Hi
I'm running Opnsense 25.7.1_1 with DSL pppoe termination on my WAN interface.
I do receive my IPv4 using pppoe and IPv6 using DHCPv6.
I configured my LAN (multiple) interfaces with static /64 networks out of my delegated prefix.
When configuring my Service-> Router Advertisements [interface] I can't start the Service anymore.
The logs show:
/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:36 error: syntax error'
The line in the config file creating the problem seems to be RDNSS which includes the suffix %pppoe0:
interface pppoe0 {
...
...
RDNSS fe80::82ee:73ff:fee2:6622%pppoe0 {
};
...
...
};
I can manually modify and start the service from CLI. So everything is working then, but just not from the UI.
Is that a config issue on my side or is the generation fo the config file broken?
Best
Alexander
I tend to agree that the scope isn't correct, but I would extend this to the whole use of the link-local of what is likely the WAN interface which the clients can never reach from a configured LAN.
I'm not sure where that DNS server comes from? It also doesn't usually happen otherwise it would have been fixed quite a while ago.
Cheers,
Franco
> interface pppoe0 {
This is definitely wrong. Radvd cannot give out SLAAC on a WAN?
Cheers,
Franco
Franco,
not sure where I have a mistake in my setup. I think it could give out SLAAC on WAN, as there is a virtual interface pppoe (which holds the actual v6 address) and the WAN physical interface (just a thought).
But how can I troubleshoot this, and why is RA generating config for the WAN interface at all?
Happy to share more configuration if this helps, but currently I'm a bit clueless where to start.
Best
Alexander
Quote from: franco on August 19, 2025, 03:56:10 PMI tend to agree that the scope isn't correct, but I would extend this to the whole use of the link-local of what is likely the WAN interface which the clients can never reach from a configured LAN.
I'm not sure where that DNS server comes from? It also doesn't usually happen otherwise it would have been fixed quite a while ago.
Cheers,
Franco
This is the link local on the WAN interface fe80::82ee:73ff:fee2:6622/64 alongside with my global IPv6 address.
As this entry is related to recursive DNS, it might be related that I'm running unboundDNS on my FW?