1
Virtual private networks / Restart Wireguard after WAN Interface gets ready
« on: July 20, 2023, 12:19:19 pm »
Hi guys,
i'm having the same situation as its mentioned here: https://forum.opnsense.org/index.php?topic=18956.0
If i restart my OPNsense my WAN Interface gets only in a couple of Minutes its IP Address, this can be 1 Minute 10 Minutes . Thats a problem, because WG is not able to connect these tunnels. After the WAN Interface gets it's IP Address, the WG Interfaces are still down, until i restart WG.
Is it still not possible to do a restart after the WAN Interface gets its IP Adress?
For the Reboot thing it could be possible to do a simple crontab with an:
How do you handle this?
sash
i'm having the same situation as its mentioned here: https://forum.opnsense.org/index.php?topic=18956.0
If i restart my OPNsense my WAN Interface gets only in a couple of Minutes its IP Address, this can be 1 Minute 10 Minutes . Thats a problem, because WG is not able to connect these tunnels. After the WAN Interface gets it's IP Address, the WG Interfaces are still down, until i restart WG.
Is it still not possible to do a restart after the WAN Interface gets its IP Adress?
For the Reboot thing it could be possible to do a simple crontab with an:
Code: [Select]
@reboot sleep 600 && /usr/local/etc/rc.d/wireguard restart
How do you handle this?
sash