Upgrading 2.4.3-p1 to 2.4.4 breaks DHCP6c?
-
Has anyone else encountered this? I’ve tried upgrading theee times, and eventually had to roll back with a snapshot every time.
I have DHCP6 configured on a WAN interface with a /56 PD that is used to assign subnets to tracked interfaces. In 2.4.3-p1 this worked without issue. As soon as the upgrade completed, all IPv6 is gone, including the WAN address. Bouncing the WAN interfaces does no good. Tried rebooting. Reconfiguring the DHCP6 settings did not help. And I’m at a loss as to what else can be done.
Is this a known issue? Does anyone have any other possible troubleshooting steps I can take? Each of these upgrade attempts requires me to schedule downtime, so I’m hoping I can squeeze in as much troubleshooting as possible tonight or Friday evening.
-
Is this bare metal? Virtual machine? What hypervisor?
What are your WAN DHCPv6 options?
-
This is Hyper-V on Server 2016.
Settings for DHCP6 on WAN are /56 PD, send prefix hint, do not wait for RA, do not release address/PD.
-
Probably https://redmine.pfsense.org/issues/8489
This appears to be isolated to Hyper-V only, but nobody has yet confirmed that. -
Interesting. So it may work if I uncheck do not wait for RA? I may have to test that tonight.
-
Sorry, posted in wrong thread after reading that reply.
Do you have any suggestions around information I should be gathering or troubleshooting steps I should be trying?
I was planning to grab a pcap tonight just to make sure the request is going out on the wire on 2.4.4 and find out if the ISP is sending anything back. It will at least confirm whether dhcp6c is running and whether the ISP is sending a response.
-
Anything we know or have asked for is on the ticket linked above. There are also a few other forum threads already going for this issue.
-
There was a thread started about this 5 months ago while 2.4.4 was still under development. https://forum.netgate.com/topic/130219/dhcpv6-client-broken-in-latest-snapshot
There was also a bug #8489 created at that time.
I really don't understand why 2.4.4 was released with this serious of a regression in it?
-
Not sure if this is related, but after updating to 2.4.4 my IPv6 has stopped working. pfSense gets an IPv6 address on the WAN and LAN side, but no clients are getting an address on the LAN.
-
@xero9 said in Upgrading 2.4.3-p1 to 2.4.4 breaks DHCP6c?:
Not sure if this is related, but after updating to 2.4.4 my IPv6 has stopped working. pfSense gets an IPv6 address on the WAN and LAN side, but no clients are getting an address on the LAN.
Probably not. In this case it's a Hyper-V issue and it never gets an address. If you haven't already, start a new thread with as much detail as possible.
