Hello,
I’ve witnessed a very strange bug on a freshly installed minimal Debian immediately upgraded to Sid. No GNOME nor any desktop. Only Sway, Firefox and, for our concern, network-manager. No configuration of any kind beside installing a few packages.
The installation and subsequent use happened while connected to Ethernet. It was fine for a few days until I needed to move and connect to my wifi. I was surprised to discover that some websites were not responding. At first, I thought they were down but I started to see a lot of them, even very important one.
I suddenly had an intuition and, indeed : turns out I was accessing website with IPv6 enabled but IPv4-only websites were down. I had managed to disable IPv4 (which is funny, when you think about it).
After many investigations, I can reproduce the problem every time as follow:
1) If network service is started while ethernet is plugged in (systemctl restart networking.service), then :
- Ethernet works perfectly.
- Disconnecting Ethernet enable Wifi which connects but only for IPv6 and DNS. Logs shows: "set 'wifi' (wlp0s20f3) as default for IPv6 routing and DNS" (but there’s no IPv4 !)
(note : DNS also returns IPv4 addresses. So IP are correct. There’s simply no route for IPv4)
- Reconnecting ethernet makes ethernet works normally.
But:
2) If network.service is started without ethernet being plugged in:
- Wifi works flawlessly
- Plugging ethernet disable Wifi but do not enable Ethernet (as shown by "ip route", both interfaces are down)
- Unplugging ethernet reenable Wifi.
That’s very strange and I have no idea on how to investigate this more deeply. I haven’t found anything helpful in the logs (I hate systemd which doesn’t allow me to simply grep through lot of logs to find the interesting ones)
I don’t know if it is related but I have a small bug with network-manager-applet : in the context menu of the applet, it always shows "enable networking" even when networking is enabled (it should have switched to "disable networking"). I don’t know if it is related but just telling it for the sake of completeness.
So, have you any idea on what could be the problem ? How I could investigate it to see if it is a bug or something I missed from my part ?
Thanks for reading
I’ve witnessed a very strange bug on a freshly installed minimal Debian immediately upgraded to Sid. No GNOME nor any desktop. Only Sway, Firefox and, for our concern, network-manager. No configuration of any kind beside installing a few packages.
The installation and subsequent use happened while connected to Ethernet. It was fine for a few days until I needed to move and connect to my wifi. I was surprised to discover that some websites were not responding. At first, I thought they were down but I started to see a lot of them, even very important one.
I suddenly had an intuition and, indeed : turns out I was accessing website with IPv6 enabled but IPv4-only websites were down. I had managed to disable IPv4 (which is funny, when you think about it).
After many investigations, I can reproduce the problem every time as follow:
1) If network service is started while ethernet is plugged in (systemctl restart networking.service), then :
- Ethernet works perfectly.
- Disconnecting Ethernet enable Wifi which connects but only for IPv6 and DNS. Logs shows: "set 'wifi' (wlp0s20f3) as default for IPv6 routing and DNS" (but there’s no IPv4 !)
(note : DNS also returns IPv4 addresses. So IP are correct. There’s simply no route for IPv4)
- Reconnecting ethernet makes ethernet works normally.
But:
2) If network.service is started without ethernet being plugged in:
- Wifi works flawlessly
- Plugging ethernet disable Wifi but do not enable Ethernet (as shown by "ip route", both interfaces are down)
- Unplugging ethernet reenable Wifi.
That’s very strange and I have no idea on how to investigate this more deeply. I haven’t found anything helpful in the logs (I hate systemd which doesn’t allow me to simply grep through lot of logs to find the interesting ones)
I don’t know if it is related but I have a small bug with network-manager-applet : in the context menu of the applet, it always shows "enable networking" even when networking is enabled (it should have switched to "disable networking"). I don’t know if it is related but just telling it for the sake of completeness.
So, have you any idea on what could be the problem ? How I could investigate it to see if it is a bug or something I missed from my part ?
Thanks for reading
Statistics: Posted by ploum — 2024-06-05 22:08 — Replies 0 — Views 13