IPv6 Invalid range?

AndyRH

The Nexus interface the PHP interface seem to disagree and what is a valid range for IPv6 DHCP pools. Devices are getting addresses from within the pool.

I did not find any other references to this issue, so maybe I made a mistake.

SteveITS

@AndyRH IIRC if you edit the PHP GUI page it will refuse to save now? I used to use that. Would be super handy if it followed the LAN subnet because our office Comcast router issues a different subnet every time it boots…like a Comcast update. :(

AndyRH

@SteveITS I can still save on the PHP page.
When the range changed it worked correctly, the clients got the new range. My other thread is because they could not get the internet, but that resolved on its own.

Bob.Dig

@AndyRH said in IPv6 Invalid range?:

but that resolved on its own.

That is common with dynamic IPv6 problems, after some time, the Lifetime of a to old prefix is over.

Gertjan

@AndyRH

That's the IPv6 DHCP pool setup that is cleary 'static' minded, not dynamic.
Prefixs can change at any time, hard coding a full prefix start end en pool IPv6 is plain wrong.
The GUI is aware that you use tracking, so it should allow ::1000 -> ::2000 where the prefix part is implicit.

The pfSense 'PGP' GUI does accept :

but it's still not ok.
Try setting up a "DHCPv6 Static Mappings" like

and now you wind up with

[26.07-RELEASE][root@pfSense.bhf.tld]/root: host epackferpar22
epackferpar22.brit-hotel-fumel.net has address 192.168.1.26
epackferpar22.brit-hotel-fumel.net has IPv6 address 2a01:dead:beef:7ce2::cc
epackferpar22.brit-hotel-fumel.net has IPv6 address ::cc

Check the /etc/hosts file and you'll understand what's happening.

So, with DHCPv6 Static Mappings" you have to use the dynamic prefix (the left part of the ::) as a 'static' and keep on checking, as if the prefix changes (and it will tomorrow, next week, or over two years), things will break.

AndyRH

@Gertjan I am not understanding what you mean about the DHCP pool. What should the notion be? In the old GUI it clearly states that is what I need to do, in the new one it does not state what should be done and does not accept the old. How do you suggest the DHCP range should be done?
I also do not understand why you brought up static mappings.

Gertjan

@AndyRH said in IPv6 Invalid range?:

How do you suggest the DHCP range should be done?

I'll bring my words closer to to topic.
Thanks for the reminder.

Right now, the 'old' GUI :

and this is 'ok' for me.
This wasn't always the case, as with earlier version (when IP6 was less a priority) I had to make it look like this :

and that totally doesn't make sense.
It prefix, assigned by the upstream (ISP ?) DHCPv6 server, "2a01:dead:beed:7ce2" in my example, can change at any moment. Prefix hardcoding is bad/wrong/will break the network as soon as the prefix changes.
That was corrected.
And that's where I join the topic : pfSense GUI PHP knows how to deal with the pool settings when tracking is used, ::xx ->::yy and not flagging that as a wrong IPv6 address. The prefix part is implicit here.
The pSense GUI (writers) make the same mistake in the past, it needed to be corrected.

The rest of my bla bla mentions the fact that with for pfSense GUI PHP the issues isn't solved entirely.

SteveITS

@AndyRH said in IPv6 Invalid range?:

I can still save on the PHP page.

Which page are we discussing? I get a different error than the above, at the top of the page (on /services_dhcpv6.php?if=lan, with from/to as "::d:0000" and "::d:ffff"):

...so I have to specify the full subnet, and change it every time (which is a different thread, because reasons) Possibly, it's different because on this specific router the LAN interface is a static IPv6.

Gertjan

@SteveITS said in IPv6 Invalid range?:

Which page are we discussing? I get a different error than the above, at the top of the page (on /services_dhcpv6.php?if=lan, with from/to as "::d:0000" and "::d:ffff"):

Classic pfSense GUI 26.07 :

I even took your "::d:0000" and "::d:ffff" and saved that.
Works for me.

SteveITS

@Gertjan OK so then it's likely a "feature" that they block it if it's not the configured static subnet. Annoying in my very specific case but not a big issue.