Here you are: linux:/home/user # ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.02 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=54.4 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=121 ms 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.95 ms --- 192.168.0.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 6ms rtt min/avg/max/mdev = 1.953/45.329/120.924/48.437 ms linux:/home/user # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=122 time=36.7 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=122 time=34.9 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=122 time=35.2 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=122 time=36.8 ms --- 8.8.8.8 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 11ms rtt min/avg/max/mdev = 34.880/35.703/36.778/0.864 ms linux:/home/user # ping google.com ping: google.com: Der Name oder der Dienst ist nicht bekannt I think there was a discussion about /etc/resolv.conf being a symlink to /var/ run/netconfig/resolv.conf in recent versions of Opensuse. Am Montag, 25. Februar 2019, 14:29:06 CET schrieb Carlos E. R.:
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.
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org