@dblclick Another reason to support this would be DDNS. We are unable to provide a IPv6 address to services .

@matty10209 Not sure why you think that is some sort of lease? Nor what rabbit hole you went down that you think you should delete an interfaces link-local address? [image: 1684077043752-ndp.jpg] Those are the link-local address of pfsense own interfaces.. You can disable IPv6 in pfsense, this doesn't remove the under laying IPv6 support in the OS, ie link-local addresses on the interfaces..

@starcodesystems If you want to have local only addresses, you want ULA. These work pretty much the same way as RFC 1918 addresses on IPv4. Link local happens automagically on all IPv6 capable devices, but you don't want to use them in the same way as global or ULA addresses. They're more for ICMP messages, router advertisements, etc..

@gamienator-0 Regarding Windows Bug I'm livin with the imagination that pfsense should not not let the request through on that interface for the wrong subnet. ///Peter!

@jknott said in 23.01 DUID question - I can't spoof my way to a new prefix: @mfld This is the opposite problem of what some others have. That's the story of my life, brother I specialize in bizarre tickets. The reason I want a new prefix is that this one directly resolves to the actual MAC address of the CPE and the OUI on this one is very specific. I'd rather obfuscate. Just out of habit. I did uncheck that option (meaning yes absolutely release the PD on restart) but they still send the same prefix. It may need to be offline for a bit. Maybe they tie it to the pppoe credential for a period of time and a reboot is too short. I called them to ask if their policy changed and the prefixes are static now but they assured me that it's still a /64 only and it's definitely dynamic.

@johnpoz said in What If ISP can only provide a /64: The point is that you can subnet a /64. Um not according the the specification - breaking up a /64 is going to be problematic for sure.. If everyone stuck to the specifications and best practice then there would be zero need to have such conversations. To be clear, I'm not an advocate of splitting up a /64 and certainly not an advocate of anyone receiving just a /64 or worse, not being served by IPv6 at all. None of these limitations are applicable to my situation either. This is just a conversation for those stuck in the gap between what should be happening and what is actually happening when stupid strikes. ️

@robbiett Great information. I will definitely look into this, as i am still new to all this.

You might compare the content in /var/dhcpd/var/db/dhcpd6.leases when it works and when it doesn't. See if maybe there is a particular lease present when it fails to parse, or check the file size when it works vs when it doesn't.

@dobby_ Thanks, switches aren't the issue (I have several). I'm just trying to minimize electricity costs. At $0.50/kWh it adds up.

solved, wasn't a pfsense issue

@wentoo Do you get a bigger prefix than /64 from your ISP? If so, you have to split off some chunk of it for a downstream router to further split. You can use a manual configuration for the link between pfSense and the next router and not worry about using DHCPv6-PD there. As I mentioned above, you can split a /64, but not for a LAN, which must be a /64 for things to work right.

@jknott I know

@chase My wording isn't the best, glad you figured it out.

@arobase13 said in How to configure dhcp6 service?: Only Android devices, don't seem to have ipv6. Yep, as I mentioned above, some genius at Google decided Android users don't want to use DHCPv6. Use SLAAC on your LAN