Moin, On Mon, 25 Feb 2019, 14:29:06 +0100, Carlos E. R. wrote:
On 25/02/2019 10.45, Stefan Vater wrote:
Hi,
after a large zypper dup last week on Monday, my internet connection refuses to work concerning proper name resolution. This is a problem with wicked and NetworkManager. The problem is that I cannot access websites with my browser, and any program which relies on name resolution cannot get anything from the internet.
nslookup works however
Also, /etc/resolv.conf is updated correctly and I have also tried "netconfig - f update" without success (although it updates /var/run/netconfig/resolv.conf and with this the symlink).
I'm not familiar with this idea of having resolv.conf as a symlink to /var/run - is that a tmpfs or static?
ip addr gives me: 2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 88:b1:11:ff:f7:6c brd ff:ff:ff:ff:ff:ff inet 192.168.0.6/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0 valid_lft 600509sec preferred_lft 600509sec inet6 fe80::28b1:35d2:e28f:4e6/64 scope link noprefixroute valid_lft forever preferred_lft forever
and ip route: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 20600 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.6 metric 600
Well, the obvious thing to try is
ping 192.168.0.1 ping 8.8.8.8 ping google.com
and see where it fails.
another thing is, do you have a *default route*? I have now seen NM failing to set a default route several times, which is why I decided to ignore NM here; good thing is, my systems here all have a LAN connection, so running with systemd-networkd.service is OK for me (never saw the issue with the default route missing since then). NM (for me) really is only left for pure W-LAN connections (knowing how to deal with a potentially missing default route :) ). HTH, cheers. l8er manfred