Timeline for How to start a swanctl.conf configured tunnel automatically
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2023 at 22:52 | answer | added | RCHinds | timeline score: 2 | |
| S Jul 22, 2020 at 19:46 | history | suggested | user339704 | CC BY-SA 4.0 | changed the typography a bit |
| Jul 22, 2020 at 15:16 | review | Suggested edits | |||
| S Jul 22, 2020 at 19:46 | |||||
| Dec 19, 2019 at 0:26 | vote | accept | Marc Wittke | ||
| Dec 13, 2019 at 19:43 | answer | added | Marc Wittke | timeline score: 2 | |
| Dec 13, 2019 at 19:29 | history | edited | Marc Wittke | CC BY-SA 4.0 | splitted the two questions |
| Dec 13, 2019 at 18:23 | comment | added | ecdsa | That systemd service unit should automatically load the config when the daemon starts. Check the documentation on how to initiate connections automatically (keyword: start_action). | |
| Dec 13, 2019 at 17:13 | comment | added | Marc Wittke | ummmm, good question. I guess the newer charon-systemd daemon is running, I posted the status summary above. | |
| Dec 13, 2019 at 17:12 | history | edited | Marc Wittke | CC BY-SA 4.0 | more environment details |
| Dec 13, 2019 at 16:43 | comment | added | ecdsa | Do you use the charon-systemd daemon? Or the old starter/charon combintation? Which strongSwan version do you use? Also note that the NetworkManager frontend uses a completely separate IKE daemon (charon-nm) that is not configured with swantl.conf/vici. | |
| Dec 13, 2019 at 12:55 | review | First posts | |||
| Dec 13, 2019 at 13:09 | |||||
| Dec 13, 2019 at 12:54 | history | asked | Marc Wittke | CC BY-SA 4.0 |