Bug #6343
closed
Old configs have interfaces with IPv6 link local addresses in the config
0%
Description
It has been reported that ipaddrv6 tag for an interface has just "FE80" in it in some pre-2.3 configs:
https://forum.pfsense.org/index.php?topic=109688.msg621286#msg621286
https://forum.pfsense.org/index.php?topic=111080.msg621838#msg621838
and maybe in other threads?
When upgrading to 2.3 these cause problems. The tag should be empty rather than containing "FE80".
This needs to be looked into an perhaps provide upgrade code to check for this case and fix it.
I am not sure how this comes about, but I don't think it has been logged in Redmine yet. I put target version 2.3.1 so someone sees this and can change it to whatever is appropriate at this point.
Updated by Chris Buechler almost 8 years ago
- Status changed from New to Not a Bug
- Target version deleted (
2.3.1) - Affected Version deleted (
2.3)
We've never set anything other than user-defined input there. The described config wouldn't pass input validation in 2.1.x, 2.2.x nor 2.3x. Anything older than that doesn't support IPv6. Maybe going back to pre-2.1.0 release before the input validation was correctly in place that was permitted. I'm guessing that person manually edited their config, given it's 1 report and Google finds exactly 1 instance of same. More than 1 person would have encountered that otherwise.
If you see something that indicates otherwise, glad to be proven wrong, but seems there's no issue here. Trying to anticipate, detect and automatically fix broken manually-edited configs, outside of completely bunk XML and reverting to a backup, is fraught with peril.
Updated by Phillip Davis almost 8 years ago
Yep, fair enough. If tgharold in the forum can explain the history of his system so we can understand how FE80 got in his config (without it being manually edited) then this could be pursued. Otherwise leave it closed.