Update 24.1.10 kills Orange FR ISP connection

Started by Sisyphe, July 11, 2024, 05:07:49 PM

Previous topic - Next topic
After updating to 24.1.10 and rebooting the system, my connection to Orange FR ISP stopped working. It seems there is no traffic on the WAN interface.

It was working fine till 24.1.8 at least (24.1.9 as well but I did not reboot after the update).

Rollback to 24.1.5 (my last snapshot) restored the connection.

Any suggestion on where to look?


July 11, 2024, 05:31:35 PM #2 Last Edit: July 11, 2024, 05:40:33 PM by Sisyphe
I get an IPv4, but Orange FR ISP does not work if there is no valid IPv6 set if I remember well.

EDIT: I'm not getting an IPv6 from DHCP on 24.1.10.

Can you lock the dhcp6c package while you are on 24.1.5 and try to upgrade again? We need to make sure we find the right component first.


Cheers,
Franco

ok, how can I do that?

EDIT: found it, upgrade in progress

Locked dhcp6c to 20230530, but same issue after upgrade.


July 11, 2024, 06:50:27 PM #7 Last Edit: July 11, 2024, 06:53:20 PM by Sisyphe
It worked!

Note: IPv6 connection for my Wireguard VPN does not come up automatically after reboot, I have to restart the Wireguard service (tested twice).

Not sure what's the matter with Orange here. I've traced the origin of the other rule, we widened the scope of it and removed a faulty one. It tests and runs fine for IPv6 in general. Probably back to packet captures with one of you fine folks. We had a lot of fun with Orange over the years already. ;)


Cheers,
Franco

What IPv6 router address is Orange using?

# grep . /tmp/*_routerv6

fe80::ba0:bab.

Any clue on why the Wireguard IPv6 VPN does not come up automatically at reboot? Can it be related?

No clue. I'm more interested in finding out why Orange doesn't adhere to sending from fe80::/10 when in fact they appear to do it (at least the router would indicate this). The only change I can see offending is when the server decides it has a different address, but due to ND you can't viably escape fe80::/10 anyway. I'm missing some context here.

No other report so far from Orange FR users. A bit curious, because normally they are very quick to help get it solved. Just as a data point.


Cheers,
Franco

I'll issue a hotfix in a bit for https://github.com/opnsense/core/commit/0217a1a95b1 so please let me know if 24.1.10_1 will solve this for you as well.


Cheers,
Franco

Same issue after installing 24.1.10_1, unfortunately.

Thanks