IPv6 forwarding died in 2.2.6 and RA issues

risotto

Upgraded to 2.2.6 and noticed a day later that IPv6 forwarding must have died. Can't route any packets across the gateway from my LAN anymore. This is a simple WAN DHCPv6 setup, with a 64 prefix requested and has the LAN interface tracking it. Clients on the LAN do seem to get an IPv6 address assigned by RA, but other than that, they cannot route across the gateway. Clients also can't ping the gateway. I found this in the Gateway logs:

Dec 23 06:49:38	radvd[18671]: resuming normal operation
Dec 23 06:49:38	radvd[18671]: sendmsg: Can't assign requested address
Dec 23 06:49:38	radvd[18671]: attempting to reread config file
Dec 23 06:49:34	radvd[18671]: sendmsg: Can't assign requested address
Dec 23 06:49:34	radvd[18269]: no auto-selected prefix on interface re2, disabling advertisements
Dec 23 06:49:34	radvd[18269]: IPv6 forwarding seems to be disabled, but continuing anyway.
Dec 23 06:49:34	radvd[18269]: IPv6 forwarding setting is: 0, should be 1
Dec 23 06:49:34	radvd[18269]: version 1.9.1 started

The routing table on the clients don't have a route set for the subnet, nor do they have a default gateway set for IPv6.

mrhanman

I'm also having IPv6 issues after upgrading to 2.2.6. I don't see any entries related to radvd in the logs, however. In fact, I can't seem to find any indication anywhere that IPv6 is doing anything at all.

My setup is similar to risotto's. Comcast is my ISP, WAN is set to DHCP6, request 60 prefix and hint, LAN is set to Track.

risotto

My main WAN is Comcast as well. Not sure whether it's specific to them though. Were there any changes in radvd in 2.2.6, or the way routing and interfaces are configured for IPv6?

cmb

No IPv6-related changes at all in 2.2.6. Probably a reboot-initiated issue of some sort. What's a traceroute6 look like? ping6 from the firewall itself work? ping6 sourced from the LAN IP?

risotto

Reboot could have triggered something, but then again I've been rebooting frequently lately, so I doubt it's just that.

I can actually trace and ping IPv6 hosts from both LAN and WAN interfaces. I suspect it's got something to do with radvd not advertising the route to my hosts properly.

cmb

Do LAN hosts get an IPv6 IP? On the same subnet as the LAN has? What does traceroute6 from LAN hosts to Internet look like?

risotto

Ok, so I've figured out that some of the issues were pebkac and some were configuration related.

One problem seems to be that Windows has a problem with setting up routes properly, if you happen to use a Hyper-V bonded wireless interface. The other was that my configuration got wedged and other clients started having full IPv6 connectivity when I went back to a configuration from about two weeks ago. I don't know exactly what tripped up radvd in those last two weeks, but I was experimenting with gateway groups and some policy based routing. It had worked with that configuration for a while, and like CMB said, a reboot may have caused something to break. Don't actually think this is 2.2.6 specific at this point either, but it was certainly a break on some less common interface settings.

Thanks everyone for your help!

mrhanman

In my case, I'm not getting IPv6 addresses on pfsense, or anywhere on my network. It was all working fine before the upgrade. I've disabled, and re-enabled all the IPv6 settings in pfsense, but no luck. I'm not sure where else to even start checking.

thvmh

Same problem here, LAN won't get any ipv6 address. Radvd gives same error over and over again. P.s. WAN works just fine. PFsene can ping and traceroute over ipv6.

Jan 2 12:17:29	radvd[14977]: IPv6 forwarding seems to be disabled, but continuing anyway.
Jan 2 12:17:29	radvd[14977]: IPv6 forwarding setting is: 0, should be 1