Track interface / Identity association - IPv6 prefix ID already in use

[Aerowinder]

Greetings,

After updating to 26.1, I was switching my IPv6 interfaces over to the new Identity association option. I am met with an error - You specified an IPv6 prefix ID that is already in use.

No worries, I thought. I'll just change it to an unused one, save, change it back, save again. Changing to an unused prefix ID allows me to save, but I'm unable to change back to my previous (now unused prefix ID - still "in use"). Even after a reboot, still can't revert it - still "in use" (it's not).

I pulled a backup and modified+restored the config file to fix it. It's perfectly happy with the old setting now.

It may be useful to know I'm on AT&T, using a bypass method. AT&T's IPv6 is kind of a joke, you have to script the PDs. I'm not sure if that's relevant here, but I can make that script available upon request.

[franco]

Hi,

I'm not entirely sure what config you use and what the scripting looks like but I'm working on better PD selection, see

https://github.com/opnsense/core/commit/52018a0260

Patch does not readily apply at the moment but once 26.1 comes out I want to make another round of testing.

If you can privately dump the output of "pluginctl -g interfaces" for your config that produces the error I can try to see if that is expected given the constraints or if there is a new bug with the validation.

That being said in the new patch you can (optionally) select different PDs for each interface.  The author of the ticket https://github.com/opnsense/core/issues/7647 also uses AT&T.


Cheers,
Franco

[Aerowinder]

franco,

I have sent via PM the interface dump and my AT&T PD script (it's the same as posted in the GitHub issue linked). I bypass the AT&T device altogether, so I have access to all PDs (16), but only use a handful.

This does very much seem like a validation error. I can go into the interface settings and change something unrelated to IPv6, and I still get the error saying the PD is already in use. I know that it's in use - it's supposed to be.

[franco]

Sorry, I can't find your PM in my inbox.

> This does very much seem like a validation error.

It is, but I'm wondering if this is new since 25.7.11 or if it was there before. I tried to keep the state of 25.7.x compatible with 26.1 although there's clearly a refactor there that could have caused it but it uses the same code as before.

If you have a custom dhcp6c.conf also by some means the validation error doesn't even effect your setup since it only tries to validate what goes into dhcp6c.conf to avoid a syntax error.

But again I may have missed something and I'd really appreciate the interface dump so it can be fixed before 26.1 is out. You can also send via mail to franco AT opnsense DOT org


Thanks,
Franco