Unable to get DHCPv6 working on LAN side

[col360]

I seem to have made it worked!
WAN confighttps://i.imgur.com/R2S8qt4.png
https://i.imgur.com/9CAHSf8.png
LAN Config https://i.imgur.com/jy2mZrh.png

Also under Firewall->Settings->AdvancedUntick "Allow IPv6" & Click SaveThen Tick "Allow IPv6" & Click Save

Also Under WAN Firewall rules I've added below rule. Not sure if this matters.https://i.imgur.com/Q8FcA6p.png

The LAN interface and devices behind the OPNSense are getting their IPv6 IPs now.

[GDixon]

thats why i told you to ignore any LL while configuring. I also always show a LL for the IPv6 gateway and for the lan I get the proper addressing shown.
It takes a few moments and most often shuting everything down at least once then botting in order.

1) dsl/cable/whatever modem
2) OPNsense box
3) whatever else is left on the lan.

for example my gateway shows LL

Code: [Select]

Gateways
Name RTT RTTd Loss Status
SPECTRUM_DHCP
90.59.64.1 7.2 ms 0.7 ms 0.0 % Online
SPECTRUM_DHCP6
fe80::2a3:d1ff:feed:7c19%em1 33.1 ms 1.7 ms 0.0 % Online
My two biggest hurdles to get it working was i had multiple gateways so I deleted all but 2 which helped.
And like you I paid far to much attention to what what was assigned at the gateway and didn't just check when I seen a LL.  Something isn't right in OPNsense I imagine maybe?

It all works



Congratulations you can count yourself as one of the few there to have it working.

[col360]

For those wonder what GDickson mean by "LL" = link local IPV6 Address.
Looking into it more may have something to do with my ISP giving out the link local IP. However doesn't quite explain why Windows direct was getting a proper IPv6 when connected directly to the bridged modem.

[bartjsmit]

It's quite normal to have a link local address for the next IPv6 router hop. My ISP works like that. The assigned range is on your side of the PPPoE link, the router only needs to know where it lives.

Bart...

[GDixon]

For those wonder what GDickson mean by "LL" = link local IPV6 Address.
Looking into it more may have something to do with my ISP giving out the link local IP. However doesn't quite explain why Windows direct was getting a proper IPv6 when connected directly to the bridged modem.

Same for me, I can get a other than LL address on windows and opensuse tumbleweed connected directly to the cable modem (cable modem has no routing is just a bridged modem) also using a linksys router, belkin router, d-link router and a have no idea was laying around no name cheapy don't even know where I got it or why router.

Seems the same behavior for a DSL modem also regarding just a LL address.

That was why it made it so damn confusing when on OPNsense we see just a LL on the gateway and instead of consistently testing anyhow we figure it won't or don't work and configure once again.

OPNsense is the only appliance / firewall-router I see this behavior with the gateway having a LL address.

When I ignored what was in the gateway and started to test each configuration was when it all came together WITHOUT throwing money at it hmmmmm.

[col360]

Interesting observation there. The linklocal address throw me off for quite some time as I did not bother testing the clients hosts thinking it didn't work!
For some reason today I found IPV6 has stopped working on the OPNsese box and DHCP6 service also stopped. I gave it a reboot and things seems to come back on correctly. Don't know if its issue with OPNSense or not. No time to look into at the moment.

[franco]

DHCPv6 service derived from interface tracking will stop if your LAN has no IPv6 address where it could broadcast from. It would point to a defunct tracking setup or defunct IPv6 WAN setup.


Cheers,
Franco