Hello! Today I started Endeavour and found that I have no internet connection over Ethernet and over wifi. The router works normally as I can use wi-fi on my phone with mobile network turned off. Last time I used my pc was on Thursday and everything was fine, I don’t remember tinkering with network in any way. What should I do to diagnose the problem? By far I tried switching to lts kernel but that got no effect.
Thanks!
Upd: ping google.com gives me “temporary error in name resolution”, while ping 8.8.8.8 gives PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
Upd2: both pings work correctly with periodic ping result lines while endeavourOS live usb is booted, so I guess something went wrong with my installation.
Resolv.conf: #Generated by NetworkManager
search Dlink
nameserver 8.8.8.8
nameserver fe80:c6e9:1aff:fe75:e8d4%enp1s0
nameserver 192.168.1.0 #NOTE: the libc resolver may not support more than 3 nameservers #the nameservers listed below may not be recognized
nameserver fe80:c6e9:1aff:fe75:e8d4%wlan
Can you tell us the model of router, is it a Cisco or D-Link router? I see both in the logs.
In the meantime, make sure you have the setttings for the router, before you start anything. Is the router preconfigured by the ISP?
If you can ping the router 192.168.0.1? if so, then access your admin section of the router and try and export your router configuration first, then try doing a hard reset of your router, usually a button recessed under the casing. Check your router’s manual.
Here is my resolv.conf just for an example. It’s simple.
[michael@eos-22 etc]$ cat resolv.conf #Generated by NetworkManager
search home
nameserver 192.168.1.1
Avoid polarizing content. We have a diverse member base spanning many geographies and cultures so please do not post content related to politics, religion or other controversial subjects.
Thanks, 8.8.8.8 is added to the list. There’s no difference as internet is not available still. I did configure two vpns, but both of them work through openconnect and you need to turn them on deliberately. Thanks for pointing on 192.168.0.1 va 192.168.1.0 inconsistency. That’s really strange.
It’s an ISP branded d-link, which is also preconfigured. 192.168.1.0 is not pingable for me. I’ll try resetting the router but I think it’s something with the OS, as my phone and live usb boot both seem to be working fine with the router.
P.S.: thanks for support.
How did you configure them? Did you make any changes to system configuration files?
If you pick a different option then you can set it to “Automatic (DHCP) addresses only” and make sure the working DNS resolver is the only one being used; otherwise the system will try to use non-working resolvers and fail.
You can use one or more of those public DNS resolvers.
If the issue is being caused by Network Manager picking up the wrong DNS resolver then this will work around that problem. The next step would be to work out why you are being provided 192.168.1.0 in the first place.
Oh, right, forgot that I could put several resolvers. So i did. Resolv.conf now shows
search Dlink
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 9 9.9 9
Note about 3 nameservers
nameserver 4.2.2.2
nameserver 192.168.0.1
nameserver fe80::c6e9:1aff:fe75:e8d4%wlan0
nameserver fe80::c6e9:1aff:fe75:e8d4%enp1s0
But there’s still no successful ping of google.com…