16
23.1 Legacy Series / Re: 23.1.7_1 broke my Firewall
« on: May 16, 2023, 08:14:53 am »@Gareth
> ROUTING: refusing to set inet6 gateway on addressless wan
> ROUTING: refusing to set inet6 gateway on addressless wan
It looks like the newly added log message didn't trigger on the reload here, not sure why or otherwise it would have said "wan(xxx)" to point to the device it's been using.
Looking further and hearing about PPPoE I think you don't have "Use IPv4 connectivity" set for your WAN IPv6 configuration? That's why it wants to use igb2 instead of pppoeX and here we can se igb2 does not have an address indeed.
If, however, the option is set then at least we know where to look further.
Cheers,
Franco
PS: Which WAN IPv6 mode are you using?
Hi Franco,
I ran the procedure a couple of times to make sure it wasn't me, but output was the same on both occasions, so just posted.
In terms of "Use IPv4 connectivity" it is set and my IPv6 mode is set to static because my ISP does not support PPPoEv6 or DHCPv6, few pictures attached showing further info.
I've kept the static IPv6 for the WAN interface and the gateways in the same /64 range so it's basically:
WAN Interface: face:face:face:face::254/64
WAN Gateway: face:face:face:face::50/64
As I recall, when I configured this a pretty long time back now, this was the only way that worked for me and I can see both before the upgrade to 23.1.7_3 and after that the face:face:face:face::254 gateway is being automatically selected, it's just that this gateway refuses to come up after the upgrade, but strangely dpinger shows it as green even though it's offline, I have attached a picture of this also.
The internal clients are given IPv6 addresses using a manually configured radvd since there is no interface to track here.
Thanks for the help
Gareth