OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • English Forums »
  • 24.1 Legacy Series »
  • config changes apply only after service disable/enable
« previous next »
  • Print
Pages: [1]

Author Topic: config changes apply only after service disable/enable  (Read 302 times)

cj_duke

  • Newbie
  • *
  • Posts: 6
  • Karma: 1
    • View Profile
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?
« Last Edit: May 08, 2024, 04:04:03 pm by cj_duke »
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • English Forums »
  • 24.1 Legacy Series »
  • config changes apply only after service disable/enable
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2