Have System Requirements Increased?

[jim1985]

No, this default predates the fork even.


Cheers,
Franco

No idea why then that on 24.7.12 (and prior versions that I have used) this gateway IPv6 Configuration Type stayed set as None, but the update to 25.1 definitely switched it to DHCPv6 which then caused my problems.

It's possible that when I first joined OPNsense at version 24.1.x I may have manually set the gateway IPv6 Configuration Type to None during my initial set up, but all upgrades after that point did not set it back to DHCPv6, but the 25.1 upgrade definitely did

[franco]

Are you using PPPoE?

[jim1985]

Yes, I am

[franco]

Ok, easy then:

community/25.1/25.1:o interfaces: remove "Use IPv4 connectivity" setting as it will be set by default

We've removed the Use IPv4 connectivity setting because it was backwards for PPPoE (it should be set by default but it was unset). Removing the setting allowed us to force the new (and correct default), but it also means that your PPPoE was now looking for IPv6 connectivity.

Old bug, good progress, but also sorry for the noise.


Cheers,
Franco

[jim1985]

Ah ha. Yes that makes sense.


Will there be a way that you can stop it looking for IPv6, maybe after a short timeout, if it's not available?

[senser]

Ah ha. Yes that makes sense.


Will there be a way that you can stop it looking for IPv6, maybe after a short timeout, if it's not available?

Probably not. Then it would stop trying for legitimate ipv6 setups that have a temporary failure.

[jim1985]

Ah ha. Yes that makes sense.


Will there be a way that you can stop it looking for IPv6, maybe after a short timeout, if it's not available?

Probably not. Then it would stop trying for legitimate ipv6 setups that have a temporary failure.

Fair point.

Well I'm not too fussed, now I was able to locate the source of my problem & put it right anyway