IPv6 broken beyond pfSense after 2.5 upgrade
-
@jknott Just another follow up to the above. It is definitely the whole NDP/RA exchanges that are just not happening to allocate IPV6 addresses. I've confirmed this by manually configuring IPV6 on a couple of my machines (adding in the IPV6 address of the pfSense router, an IPV6 address in my address range and prefix for the machine) and then the individual machines passes the appropriate tests on sites like test-ipv6 and ipv6-test just as before my update from 2.4.5p1. I can route IPV6 between the machines and on the internet correctly. Something is just not happening to enable the "chatter" to make the address/router negotiation work, but which happened perfectly previously.
-
I don't know what would be causing that. IPv6 works fine for me with 2.5.
-
@jknott I'm at a loss at this point. Doing a packet capture of ICMP v6 packets on my LAN I can see a steady chatter of Neighbour Solicitation/Neighbour Advertisement packets being used to determine link layer addresses, but absolutely no router solicitation or router advertisement messages.
I've also tried changing the RA settings to Unmanaged and to SLAAC with no change.
As I said pfSense is operating with IPv6 and commands on clients such as "host google.com" will return IPv6 addresses as well as IPv4.
All a mystery!
-
Try reinstalling pfsense. Backup your config first, then see what happens after the reinstall, but before restoring the config.
-
@stepheng To me, after upgrading to 2.5.0, it doesn't let me use LAN with IPv6 with SLACC, if RADVD is activated. It only permits SLACC on LAN if RADVD is set to Disabled.
-
@jknott I will do that, but it will have to wait for a couple of days until I'm on my own in the house and don't have any pressing deadlines.
I know that in theory it only takes 15 minutes to do a reinstall, but you never know what may not quite work. I'll get my old Ubiquity Edgerouter out as well in case I need to use it (I think it still has a working configuration).
-
@tadao That is very interesting, but also to my limited understanding, somewhat puzzling. As I said, I'm not really as expert on IPv6 as I would like, but I'd be surprised that turning RADVD off would work (except with manually assigned clients - and that works for me in any case, but is a bit impractical for phones and mobile devices and besides the whole point of RA/DHCPv6 is to do all this stuff automagically). However, I did try it and got no joy. I have tried all of the setting in the RA tab. As @JKnott says, I think a re-install is needed in my case which I will try in a day or two when I have some quiet time on my own.
-
@stepheng SOLVED!
I didn't need to re-install pfSense.
I noticed that poking around in the command line with "ps" that although I was seeing the radvd process, the only dhcp6 process that I was seeing was the dhcp6c which was being used on my pppoe0 connection to obtain my WAN IPv6 address.
I went back to the LAN / DHCPv6 Server page and made a trivial alteration (added an NTP server) and resaved the page. This obviously caused the DHCPv6 server to kick into action again. I can now see a "/usr/local/sbin/dhcpd -6 " process running (as well as the normal dhcpd process for IPv4), and also a "/usr/local/sbin/dhcpleases6" process.
All the expected ICMPvs messages for RA, RS, NS, NA are now being seen on the LAN and all devices that previously had IPv6 addresses are getting them. "test-ipv6.com" gives me my score of 10/10 again.
I was able to return the LAN / DHCPv6 Server page back to exactly the same configuration as before without any strange behaviour happening (i.e. removed the NTP server again).
I assume that for some reason during the upgrade process the dhcpv6 process didn't get started or failed. It might be interesting to see if with my configuration it starts properly when the system is rebooted - and I might try that tomorrow as that is something that can be done in a couple of minutes without risk.
Thanks for the help from @JKnott and @tadao. I must confess that I think I need to understand more about IPv6. Now that it is working I've captured some packets in Wireshark so I can study them and hopefully further my knowledge.
-
I have a similar problem. My ISP is also Zen, and it was working perfectly in 2.4.5p1. I'm using an SG-1100.
It appears that IPv6 comes up normally, but after a few seconds the LAN interfaces lose their IPv6 addresses. This can be reproduced by disconnecting and reconnecting the WAN in Status / Interfaces.
The DHCP logs shows that dhcp6c receives a prefix, adds addresses to the LAN interfaces, then removes them:
-
https://redmine.pfsense.org/issues/11365
-
The "restarting" in the log indicates that dhcp6c is getting a sighup, but from where?
-
@yon-0 You seem to be talking about a completely different problem. Our ISP delegates a /48 to us, as is normal, and the LAN interfaces use a /64 subnet.
-
Are you trying to configure the WAN interface for a /48? Or allowing DHCPv6-PD to do it? What happens if you select a smaller prefix. For example, I get a /56 from my ISP, but can select a smaller one.
-
@jknott I'm not sure I understand you. There is no problem with the WAN interface; the router has an IPv6 connection to the outside world and can connect happily to external sites. The problem is that the LAN interfaces lose their addresses after a few seconds, apparently because dhcp6c does a restart, so clients cannot make (non-local) IPv6 connections.
-
Sorry, I wasn't quite sure what you were saying. However, what happens if you select a smaller prefix? On the WAN page, you can choose in the DHCPv6 Prefix Delegation size box. Do you have the same problem if you select a /49? /56? etc.
-
@jknott Changing it to /49 didn't seem to change anything. After changing it to /56 it didn't work at all - dhcp6c seemed to exit. Change back to /48 and it's the same as before: LANs get addresses then lose them a few seconds later.
-
After my WAN was down for some minutes IPv6 doesn't come up anymore. I'm getting my prefix and every device gets an IPv6 address but the gateway keeps pending. Of course I use a monitor IP but it's not working. Only solution is to reboot the whole pfSense. This is unacceptable and I can't believe that this major fault wasn't discovered in the BETA builds.
Any ETA for a fix? How do I downgrade back to 2.4.5_p1?
Netgate 6100 MAX
-
@johnpoz With 2.5.0 I see with Multi WAN setup that sometimes I don't get a prefix after interface down/up. DHCP log is showing "unexpected interface"
Mar 1 16:50:09 dhcp6c 22055 unexpected interface (15) Mar 1 16:50:09 dhcp6c 18058 reset a timer on pppoe0, state=SOLICIT, timeo=151, retrans=109128 Mar 1 16:50:09 dhcp6c 18058 send solicit to ff02::1:2%pppoe0 Mar 1 16:50:09 dhcp6c 18058 set IA_PD Mar 1 16:50:09 dhcp6c 18058 set IA_PD prefix Mar 1 16:50:09 dhcp6c 18058 set option request (len 4) Mar 1 16:50:09 dhcp6c 18058 set elapsed time (len 2) Mar 1 16:50:09 dhcp6c 18058 set identity association Mar 1 16:50:09 dhcp6c 18058 set client ID (len 10) Mar 1 16:50:09 dhcp6c 18058 Sending SolicitI do have to kill the dhcpd6 with "killall -9 dhcp6c" and apply interface to get it back working.
Netgate 6100 MAX
-
Still no ETA for fixing this major bug that makes IPv6 unusable?
-
Moved that other, non-related discussion to its own thread.
Most of the IPv6 work I see being done for 2.5.1 can be tracked here:
https://redmine.pfsense.org/issues/11454
Overall progress of everything being done for 2.5.1 here:
https://redmine.pfsense.org/projects/pfsense/issues?page=1&query_id=172
And here:
https://redmine.pfsense.org/projects/pfsense/issues?query_id=179
There are snapshots to try if you want to test it in your environment but it is still "In Progress."
