pfSense

Marcos M wrote in #note-1:

I'm not able to reproduce this. I set up pfSense upstream with Kea DHCPv6 Server and managed RA. Then I verified that the downstream pfSense CE 2.7.2 client received leases as expected. After upgrading the client to 2.8.0, the address was still leased and on the interface. I then cleared the lease upstream and toggled the client's IPv6 config (set to None, save/apply, set to DHCP6, save/apply). The client - pfSense CE 2.8.0 - was still able to get a lease.

It is the upstream pfSense box that was upgraded from 2.7.2 to 2.8.0. The downstream clients are Windows 11 machines and Apple iPhones. It is the Windows 11 boxes and iPhones that do not get a DHCPv6 lease.

Probably worth mentioning that pfSense runs as a VM on Proxmox using virtio interfaces.

I mixed up my comment with notes from another test, apologies. I'll remove it and clarify here:

1. pfSense 2.7.2 VM with DHCPv6 Server and managed RA leasing to a pfSense+ 25.03 VM and Windows 11 VM.
   The 25.03 VM's WAN is configured for DHCP6.
2. Upgrade 2.7.2 VM to 2.8.0.
3. The 25.03 VM still has a working lease. I toggled the 25.03 WAN config between None/DHCP6 to force the requests; the 25.03 VM picked up the lease again.
4. Tested with a Windows 11 client as well - it also received a lease form the pfSense CE 2.8.0 DHCPv6 Server.

Thanks. I'll run some packet captures and have a closer look at what is going on.

It'd be best to continue the discussion on the forum for now - please open a thread there:
https://forum.netgate.com/category/93/ce-2-8-0-development-snapshots

Below is a link you can use to share the full PCAPs as well as the System and DHCP logs so we can get a better idea about what may be happening:
https://nc.netgate.com/nextcloud/s/dte9FdAQSEHdyFY

Thanks. Have uploaded the full pcaps and logs. Will continue on the forum.