I try to configure an automatic start and stop time for the IPsec-host but the option in the connection-scheduler does not seem to have the effect, that I hoped for.
Now my goal is to “automate” the clicking of the “activate”-field at the top of the menu and hitting the “save”-button at a specific time (and deactivate it again later).
I tried it with the connection scheduler because it offers the option to “(re)start IPsec” but that does not seem to have any effect or at least not the same effect as “activating” IPsec.
I cross-checked with starting the “IPsec-service” from the terminal (/etc/init.d/Ipsec start) but that does not do the trick either.
Anyway, when I follow the log-messages, it seems like “activating” IPsec in the menu does a lot more, like loading certificats, etc. so what is the option in the connection-scheduler for?
And what commands are needed to automate “clicking activate” in the IPsec-menu?
first of all, thank you very much for your quick reply!
I did some more “testing” and made some observations.
There is no check-mark appearing or disappearing when you refresh the IPsec-menu-site after you started or stopped IPsec either from the terminal (/etc/init.d/ipsec start) or via the connection scheduler. So I thought, this led to my confusion and solved the riddle, but unfortunately, there is more.
When I start IPsec via the menu and stop it via scheduler or terminal and later start it again via scheduler or terminal, everything works great (Connection, No Connection, Connection).
BUT
When IPsec is not activated via the menu in the first place and I start it via connection scheduler or terminal, it just does not work.
I compared the log-messages (tail -f /var/log/messages) and the initiating-sequence is exactly the same. The difference is, that when I “cold-start” IPsec via terminal or scheduler, the firewall drops the incoming requests from the IPsec-client.
Maybe someone can reproduce this behavior or I misconfigured something.
