01-11-2020, 10:56 AM
(01-10-2020, 07:46 PM)a0kami Wrote:(01-03-2020, 01:25 PM)rleasle Wrote: Well, that was fun. Turns out that the DHCP client took precedence over the default gateway for my home network. Once I disabled that, everything came up correctly. I guess I'm the only one here stubborn enough to use static IPs?
I'm not sure I understand how fixed but I'm having the exact same host not resolving issue over wifi.
I connect to a shitty wifi extender and I've had a friend having issues as well (he was using x86 though). :/
Anyway in the meantime I borrowed a usb-to-ethernet adapter, but may I kindly ask you could fill me in on what exactly is the issue and how to troubleshoot ?
TL;DR - It's probably a configuration issue. Check Network Manager for your wifi setup, try the 'ping' command to test DNS and routing.
It's not about the connection (unless you have the wrong wifi password or security settings), it's about how networking is configured. So DNS (name server) and default routing. Not sure how much you know about networking (not sure how much I know). If it's a DNS problem, you can get to a remote host by IP address, but not by name. When I was having my problem, I used the command
Code:
$ ping github.com
and the system would try the correct IP address. So DNS was working (the ping didn't work because of routing issues). If DNS was messed up, it would have told me "name or service not known". Even with DNS messed up, if the routing is correct, you can ping the IP directly
Code:
$ ping 192.30.255.112
You can look at or change the DNS settings from the Network Manager. It should also show up in the file /etc/resolv.conf
For the routing issue I had, I used the route command:
Code:
$ route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 302 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 302 0 0 wlan0
The above output was what it looked like when I was having my problems. That netmask value (255.255.0.0) was only allowing me to access part of the internet.
You can also check the configuration that Network Manager set up from the command line (here, I've X-ed out my actual values):
Code:
$ sudo ifconfig wan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 255.255.255.0 broadcast xx.xx.xx.255
inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20<link>
ether xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 253663 bytes 334990443 (319.4 MiB)
RX errors 0 dropped 57 overruns 0 frame 0
TX packets 135146 bytes 13434493 (12.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
If the interface doesn't say UP, you're not actually connected.
Hope something here helps.