This is starting to become a rather tedious problem but for some reason I have “limited connectivity” basically once a day when I initially boot my PC and the only way I know to cure it is to reboot my router.
I cannot ping any address, including my router. At first I thought it was an issue with my PCs hostname but that doesn’t seem to be the problem. Any ideas on how to fix this?
This is only an issue with my PC as all other devices stay connected no issue. Connection is wired directly to the router if that makes a difference.
I’m just using my motherboard’s onboard ethernet which is listed as “Intel Corporation I211 Gigabit Network Connection (rev 03)”.
I’m not sure about the network address. It’s going to be hard to diagnose as it doesn’t happen with every reboot but it seems to happen every day when I first boot my PC. If I reboot now then it’ll connect normally.
To check if it’s getting an address when you see the issue, run ip addr show dev <devicename> and you should see the ethernet interface listed. If an address is assigned, you’ll see that as well.
For example, if I enter ip addr show dev enp2s0, I see:
$ ip addr show dev enp2s0
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether <hwaddr> brd ff:ff:ff:ff:ff:ff
inet x.x.x.x/24 brd x.x.x.255 scope global dynamic noprefixroute enp2s0
valid_lft 38384sec preferred_lft 38384sec
inet6 <address>/64 scope global temporary dynamic
valid_lft 1523sec preferred_lft 1523sec
inet6 <address>/64 scope global temporary deprecated dynamic
valid_lft 1523sec preferred_lft 0sec
inet6 <address>/64 scope global temporary deprecated dynamic
valid_lft 1523sec preferred_lft 0sec
inet6 <address>/64 scope global temporary deprecated dynamic
valid_lft 1523sec preferred_lft 0sec
inet6 <address>/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 1523sec preferred_lft 1523sec
inet6 <address>/64 scope link noprefixroute
valid_lft forever preferred_lft forever
With actual values where I’ve masked them, naturally.
You can just run ip addr if you’re not sure of the hardware device’s identifier, but the list might be longer (in my case, I have Docker and virtual network interfaces, so the list is quite long unless I specify the interface I’m interested in).
Depending on what the router is, I’d also probably set up to capture the DHCP address request/response using a packet capture at the router, but you have to have a router with firmware that lets you do that, so that’s going to be very dependent on what you have.
If the router logs the requests, and you can connect to it with other devices, you might see if there’s a log that shows what happens when you first start the system up in the morning as well, to see if there’s anything logged at the router.
I also run into a similar problem but less frequent although I can ping the router if NetworkManger has set the correct IP address or if I fix the IP address myself. In my view the behavior of NetworkManger is not helpful in these situations.
For now, for me, the only working solution is also to reboot the ADSL router so it could be router problem…