Gateway monitor (wireguard_ipv6) doesn't start automatically

[Kornelius777]

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug

After a reboot, my Gateway monitor (wireguard_ipv6) always needs to be started manually.
My local Wireguard Address is fd00:dead:beef:cafe::10/64
Monitor IP is set to fd00:dead:beef:cafe::1

Gateway monitor (wireguard_ipv4) starts with no issues.

Expected behavior

Start the additional Gateway Monitor (IPv6) automatically after startup.

Environment

Software version used and hardware type if relevant, e.g.:

OPNsense 24.7.11_2-amd64

[fichtner]

Hmm, can you add a tunable with net.inet6.ip6.dad_count and value 0and see if that works around it? Normally wireguard turns off DAD, but it could also be an issue on the other side…

[Kornelius777]

Indeed, this tunable made the Gateway Monitor start automatically!
Thank you!

[fichtner]

Let me check this again after the holidays, maybe this can be improved.

Cheers,
Franco

[ianmtaylor1]

I was having similar issues with a GIF interface (Hurricane Electric tunnel). The gateway monitor was not starting on boot, or would periodically crash and not restart. This tunable also fixed the issue for me.

[fichtner]

This relates to be42113 but I fear this may still be problematic for GIF, GRE, WG and others... Only VIPs are a little better...