IPv6 track interface setting - doesn't show correct prefix range
-
So I have a /60 from my ISP via Prefix Delegation… LAN interface works great and everything with IPv6 (Track Interface, WAN, Prefix 0).
I've added a USB 3.0 Gigabit Ethernet interface (ASIX 88719-based, ue0/OPT1) and want to use that as a guest network. I set it up with IPv4 just fine, but when I set IPv6 to Track Interface, it shows a possible prefix range of 0 to 0. Knowing that I have more than that available, I enter any other valid value (1-f, since my LAN is using 0) and save/apply. When the settings page reloads, it now properly shows a range of 0 to f.
Another issue… it will actually let me select prefix 0, even though it is already in use by the LAN connection. It doesn't seem to actually do anything as far as the addressing goes (the LAN retains that prefix), but I should receive some kind of error that the prefix selected is already in use or something, rather than being prompted to Apply Changes.
Possibly related, but might not be... With the prefix set to any valid value 1-f, the OPT1 interface never shows a valid public IPv6 address, just a link-local IPv6 address.
EDIT to add: After a reboot, the OPT1/ue0 interface comes up with an IPv6 address in that prefix. It would be nice to prevent a reboot here.
-
Sounds like this bug:
https://redmine.pfsense.org/issues/3790But that was fixed a few months ago. Are you on a current 2.2 snapshot?
-
Yep, I'm on a current build. At the time I posted, it might've been a day old. But I can still reproduce that now on the build I'm running (dated Sun Nov 30 03:42:03 CST 2014). If I were to add a third interface to my box, the first trip to the config would show me 0-0 being valid prefixes, but it would actually allow me to enter something other than 0.
But if I were to enter 0 (which is already in use), it would just prompt to apply changes, rather than notify me that prefix 0 is already in use on another interface.
Screenshots…
ipv6-track1.png - new interface, when I first select Track Interface, "between 0 and 0" is what appears.
ipv6-track2.png - when I enter another value and it reloads to apply changes, it shows "between 0 and f".
-
So two issues here…
-
wrong values being displayed (I have a /60, so 0-f should be possible, but 0-0 display initially until the page is reloaded)
-
entering a prefix value already in use on another interface doesn't produce an error
-
-
Drop those onto the redmine ticket linked above as notes, one of us can reopen that ticket since it appears the fix isn't quite right.
-
Drop those onto the redmine ticket linked above as notes, one of us can reopen that ticket since it appears the fix isn't quite right.
Done!
