I’ve just installed Leap 15,1 and my networking isn’t working. I can connect to my Internet server without difficulty, but I don’t seem to be able to get any name resolution. nslookup google hangs for a minute and then gives me the message conection timed out; no servers could be reached. If I go to Network Settings in Yast, I get a message telling me that the network is being handled by Network Manager. In Yast, I’m told that the Network Setup Method is Network Manager Service. Under “configuring Network Connections”, I’m told that "To open the network configuration dialog in GNOME, open the settings menu via the status menu and click the Network entry. " But I can’t find the settings menu that this is referring to.
So how can I get network name resolution working? I’ve gotten the impression that this stuff is changing a lot from one release to the next.
Conclusion: don’t hesitate to use nmcli. It’s easy and helpful. Showing your links, addresses and routes helps a lot:
erlangen:~ # ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether d0:50:99:9a:e1:50 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 84:16:f9:3f:0c:01 brd ff:ff:ff:ff:ff:ff
erlangen:~ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d0:50:99:9a:e1:50 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 84:16:f9:3f:0c:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.3/24 brd 192.168.178.255 scope global wlp3s0
valid_lft forever preferred_lft forever
inet6 2001:a62:308xxxxxxxxxxxx/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 6890sec preferred_lft 3290sec
inet6 fe80::8616:xxxxxxxxxxxxx/64 scope link
valid_lft forever preferred_lft forever
erlangen:~ # ip r
default via 192.168.178.1 dev wlp3s0 proto static
192.168.178.0/24 dev wlp3s0 proto kernel scope link src 192.168.178.3
erlangen:~ #
This is the standard way of working when having problems getting to the internet. I advised step 5 because you say that is where your problem is, but maybe you should start at the begin so that we all can see what is working and what not.
You check from bottom to top:
Is the NIC up with an IP address?
ip addr
Can you connect to another system on your LAN?
ping -c1 <IP-address of your router>
(I hope you know that address)
Do you have a default route to the Internet?
ip route
Can you connect to a system on the internet?
ping -c1 195.135.221.161
Can you resolve host/domain names?
ping -c1 forums.opensuse.org
Take care. As soon a one step fails, that must be resolved first. It is useless to go to the next step before it is resolved.
So start with 1. and do not hesitate to post the output here to get help on the interpretation.
Unfortunately, since I can only use the Net via a second laptop (sitting next to the one giving me trouble), I can’t post any long outputs. I’m following this thread using the second laptop.
Does not look in good shape to me, unless you did a specific local config (but following advice by Henk @hcvv is a good starting point).
If needed, the following should adjust /etc/resolv.conf (again, unless you have special local needs):