1
24.1 Production Series / config changes apply only after service disable/enable
« on: May 08, 2024, 03:53:15 pm »
Hello everyone,
with my opnsense instance I observe the following behaviour:
- Wireguard interface after reboot has the ipv4 address missing. I have to disable and reenable WG for the interface to bring up both ipv4 and ipv6 address.
- Changing the WG config (adding peer) does add the peer, but the peer can not connect (handshake not complete). I have to disable and reenable WG to accept the new config/peer.
- I did setup (new instance - testing environment) nginx with upstream server. Some behaviour as on running instance, the setup/config for nginx was only accepted as I disabled and reenabled the service.
Is this normal behaviour? Which point I am missing with configuring these services?
with my opnsense instance I observe the following behaviour:
- Wireguard interface after reboot has the ipv4 address missing. I have to disable and reenable WG for the interface to bring up both ipv4 and ipv6 address.
- Changing the WG config (adding peer) does add the peer, but the peer can not connect (handshake not complete). I have to disable and reenable WG to accept the new config/peer.
- I did setup (new instance - testing environment) nginx with upstream server. Some behaviour as on running instance, the setup/config for nginx was only accepted as I disabled and reenabled the service.
Is this normal behaviour? Which point I am missing with configuring these services?