Router Advertisement Daemon Error After Upgrade

[RailNetRider]

Good day everyone.

After upgrading to OPNsense 22.7, I noticed that the Router Advertisement Daemon (radvd) is failing with the following error:

"/usr/local/sbin/pluginctl: The command '/usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog' returned exit code '1', the output was '/var/etc/radvd.conf:3 error: syntax error'"

/var/etc/radvd.conf

Code Select Expand

# Automatically generated, do not edit
# Skipping unsupported unknown interface lan

After this, I went to my LAN interface and simply clicked Apply, which resulted in the following error:

"The following input errors were detected:
The DHCPv6 Server is active on this interface and it can be used only with a static IPv6 configuration. Please disable the DHCPv6 Server service on this interface first, then change the interface configuration."

My LAN IPv6 Configuration Type is set to "Track Interface".

ISC DHCPv4, ISC DHCPv6, and Kea DHCPv6 are all disabled on the LAN interface.
I only use Kea DHCPv4.

Is this a problem with the new OPNsense update or is the problem on my side?

[franco]

https://github.com/opnsense/changelog/blob/105c1afe3cef13a34a4897e328ea6d95a0323d4d/community/25.7/25.7#L44

If so, unset Track interface in your IPv6 LAN configuration.


Cheers,
Franco

[cap10morgan]

https://github.com/opnsense/changelog/blob/105c1afe3cef13a34a4897e328ea6d95a0323d4d/community/25.7/25.7#L44

If so, unset Track interface in your IPv6 LAN configuration.


Cheers,
Franco

What's the migration path from this? Is there a new way to automate setting LAN IPv6 ranges based on the prefix delegated to the WAN interface?

[Monviech (Cedrik)]

Isn't your WAN set to DHCPv6? With that you can use Track Interface on LAN.

[cap10morgan]

Isn't your WAN set to DHCPv6? With that you can use Track Interface on LAN.

In my case it's a 6rd tunnel. But I'm still not clear on what is changing (and what I need to do to migrate) with 25.7 w/r/t setting LAN interfaces to "track interface" for their IPv6 ranges.

[franco]

Well, 6RD wasn't part of this change and should be the same, but I can take a closer look tomorrow.


Cheers,
Franco

[RailNetRider]

The issue was on my side. I enabled the 'Track Interface' option when first setting up the router without fully understanding its purpose or functionality. After taking the time to research and read about how 'Track Interface' works, I now recognize that the problem stemmed from my own misconfiguration. Thank you for the replies.

[franco]

Well, you and me both. 6rd and 6to4 are both eligible for tracking but I've hardwired it to only dhcp6.

# opnsense-patch https://github.com/opnsense/core/commit/25d2d6bb4a


Cheers,
Franco

[humanthrope]

I ran into this issue as well. Applied the patch and tracking my 6rd connection works once again.

However, after (re)booting opnsense, my LAN clients can't get out over ipv6 until radvd is restarted (even though it appears to have started at boot time).