Hi
I have an IPv6 connection with DHCPv6-PD from my ISP. IPv6 on WAN is configured with DHCPv6, Prefix delegation size and prefix hint enabled.
LAN is configured with Track Interface WAN and a prefix id.
With that configured, my LAN clients don't receive any prefix information in the router advertisements. After I run
/var/etc/rtsold_intX_vlanY_script.sh
manually, the clients receive prefix information and IPv6 works.
As a workaround I added the line into a shellscript in /usr/local/etc/rc.syshook.d
I run 18.1.2_2-amd64 on a APU. The issue already was in 15.7: https://forum.opnsense.org/index.php?topic=1950.msg6072#msg6072.
Is there something I can change so I don't need the workaround?
What version of opnsense are you running?
I run opnsense 18.1.2_2-amd64 with serial console.
Are you seeing a prefix on the Lan interface before you run the rtsold script?
No, I only see the IPv4 address.
Do you have directly send solicit on or off in your wan dhcp6c settings?
Directly send SOLICIT is turned off.
Have you tried with it turned on?
Thanks for the hint. With that flag enabled it grabs the IPv6 after boot without the workaround. However with this setting enabled unbound doesn't start anymore. Is this a bug?
opnsense: /status_services.php: The command '/usr/local/sbin/unbound -c '/var/unbound/unbound.conf'' returned exit code '1', the output was '[1518296527] unbound[21470:0] error: can't bind socket: Can't assign requested address for 2001:db8::xxxx [1518296527] unbound[21470:0] fatal error: could not open ports'
I configured unbound to only listen on specific interfaces (it doesn't need to listen for dns requests on the wan interface). If I set Network Interfaces in unbound to all the service starts again.
Leave unbound to listen on all, there's often issues if you don't. pf***** also suffers from the same issues. It's not going to cause problems if it's listening on all interfaces
Good to know. Thanks for your help.
You're welcome, :)
Mark it solved.