On 25/02/2019 14.34, Stefan Vater wrote:

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.

I suppose the thing is that /etc is considered a directory for configuration, not for variables. Ok, so name resolution fails. The next thing is: cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" cat /etc/host.conf | egrep -v "^[[:space:]]*$|^#" Ah, side note. I have /usr/local/bin/english: #!/bin/sh LANG=en_US.UTF-8 \ LC_ALL=en_US.UTF-8 \ DICTIONARY=english \ KDE_LANG=en_US.UTF-8 \ exec "$@" And then I do: ingles ping google.com to get the error messages in English so that we can all read them ;-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Oh sorry, in the meantime I changed from wireless to wired network connection. But not much difference with wireless: linux:/home/user # cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" search localdomain nameserver 192.168.0.1 nameserver fe80::1%wlp2s0 Stefan Am Montag, 25. Februar 2019, 14:55:42 CET schrieb Stefan Vater:

Hi Carlos,

Here is the output:

linux:/home/user # cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" search localdomain nameserver 192.168.0.1 nameserver fe80::1%enp0s31f6

linux:/home/user # cat /etc/host.conf | egrep -v "^[[:space:]]*$|^#" order hosts, bind multi on

Somehow your script for getting English messages does not work for me...

Stefan

Am Montag, 25. Februar 2019, 14:43:51 CET schrieb Carlos E. R.:

...

Ok, so name resolution fails.

The next thing is:

cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" cat /etc/host.conf | egrep -v "^[[:space:]]*$|^#"

Ah, side note. I have /usr/local/bin/english:

#!/bin/sh LANG=en_US.UTF-8 \

LC_ALL=en_US.UTF-8 \ DICTIONARY=english \ KDE_LANG=en_US.UTF-8 \ exec "$@"

And then I do:

ingles ping google.com

to get the error messages in English so that we can all read them

-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

On 25/02/2019 14.55, Stefan Vater wrote:

Hi Carlos,

Here is the output:

linux:/home/user # cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" search localdomain nameserver 192.168.0.1 nameserver fe80::1%enp0s31f6

First thing to check is that 192.168.0.1 resolves. Try: host -v google.com 192.168.0.1 I have my doubts about that IPv6 nameserver. Test it. I don't know the IPv6 address of my router, so I try against a local machine, and after opening the firewall, it works (before, I got timeout): cer@Telcontar:~> host google.es fe80::4ecc:6aff:fe61:50a1%eth0 ;; connection timed out; no servers could be reached cer@Telcontar:~> Message in the firewall:

<0.4> 2019-02-25T16:07:58.738832+01:00 Isengard kernel - - - [4900477.127385] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=4c:cc:6a:61:50:a1:00:21:85:16:2d:0b:86:dd SRC=fe80:0000:0000:0000:0221:85ff:fe16:2d0b DST=fe80:0000:0000:0000:4ecc:6aff:fe61:50a1 LEN=75 TC=0 HOPLIMIT=64 FLOWLBL=401697 PROTO=UDP SPT=57025 DPT=53 LEN=35

So I do know it is reaching the correct machine. Now: cer@Telcontar:~> host google.es fe80::4ecc:6aff:fe61:50a1%eth0 Using domain server: Name: fe80::4ecc:6aff:fe61:50a1%eth0 Address: fe80::4ecc:6aff:fe61:50a1%2#53 Aliases: google.es has address 216.58.201.131 google.es has IPv6 address 2a00:1450:4003:80a::2003 google.es mail is handled by 30 alt2.aspmx.l.google.com. google.es mail is handled by 20 alt1.aspmx.l.google.com. google.es mail is handled by 50 alt4.aspmx.l.google.com. google.es mail is handled by 40 alt3.aspmx.l.google.com. google.es mail is handled by 10 aspmx.l.google.com. cer@Telcontar:~>

linux:/home/user # cat /etc/host.conf | egrep -v "^[[:space:]]*$|^#" order hosts, bind multi on

It is correct.

Somehow your script for getting English messages does not work for me...

Did you flag it executable? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Hi, thanks for the discussion! Here is what I get: linux:/home/user # dig +trace mit.edu ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.2 <<>> +trace mit.edu ;; global options: +cmd . 198198 IN NS c.root-servers.net. . 198198 IN NS d.root-servers.net. . 198198 IN NS e.root-servers.net. . 198198 IN NS f.root-servers.net. . 198198 IN NS g.root-servers.net. . 198198 IN NS h.root-servers.net. . 198198 IN NS i.root-servers.net. . 198198 IN NS j.root-servers.net. . 198198 IN NS a.root-servers.net. . 198198 IN NS k.root-servers.net. . 198198 IN NS l.root-servers.net. . 198198 IN NS m.root-servers.net. . 198198 IN NS b.root-servers.net. couldn't get address for 'c.root-servers.net': not found couldn't get address for 'd.root-servers.net': not found couldn't get address for 'e.root-servers.net': not found couldn't get address for 'f.root-servers.net': not found couldn't get address for 'g.root-servers.net': not found couldn't get address for 'h.root-servers.net': not found couldn't get address for 'i.root-servers.net': not found couldn't get address for 'j.root-servers.net': not found couldn't get address for 'a.root-servers.net': not found couldn't get address for 'k.root-servers.net': not found couldn't get address for 'l.root-servers.net': not found couldn't get address for 'm.root-servers.net': not found couldn't get address for 'b.root-servers.net': not found dig: couldn't get address for 'c.root-servers.net': no more linux:/home/user # dig -6 +trace mit.edu ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.2 <<>> -6 +trace mit.edu ;; global options: +cmd . 198121 IN NS b.root-servers.net. . 198121 IN NS c.root-servers.net. . 198121 IN NS d.root-servers.net. . 198121 IN NS e.root-servers.net. . 198121 IN NS f.root-servers.net. . 198121 IN NS g.root-servers.net. . 198121 IN NS h.root-servers.net. . 198121 IN NS i.root-servers.net. . 198121 IN NS j.root-servers.net. . 198121 IN NS a.root-servers.net. . 198121 IN NS k.root-servers.net. . 198121 IN NS l.root-servers.net. . 198121 IN NS m.root-servers.net. couldn't get address for 'b.root-servers.net': not found couldn't get address for 'c.root-servers.net': not found couldn't get address for 'd.root-servers.net': not found couldn't get address for 'e.root-servers.net': not found couldn't get address for 'f.root-servers.net': not found couldn't get address for 'g.root-servers.net': not found couldn't get address for 'h.root-servers.net': not found couldn't get address for 'i.root-servers.net': not found couldn't get address for 'j.root-servers.net': not found couldn't get address for 'a.root-servers.net': not found couldn't get address for 'k.root-servers.net': not found couldn't get address for 'l.root-servers.net': not found couldn't get address for 'm.root-servers.net': not found dig: couldn't get address for 'b.root-servers.net': no more So this seems to be negative? Stefan Am Montag, 25. Februar 2019, 16:53:04 CET schrieb Bengt Gördén:

On 2019-02-25 16:18, Carlos E. R. wrote:

...

host -v google.com 192.168.0.1

This is probably good if you want an answer like "ping". But you can also try +trace with "dig" if the problem is more complex than just your own caching DNS server. It does a similar job as traceroute but for DNS.

dig +trace mit.edu

For v6 try: dig -6 +trace mit.edu

-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Hi, thanks for the help. Here again the output: linux:/home/user # host -v google.com 192.168.0.1 Trying "google.com" Using domain server: Name: 192.168.0.1 Address: 192.168.0.1#53 Aliases: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11726 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com. IN A ;; ANSWER SECTION: google.com. 98 IN A 172.217.22.110 Received 44 bytes from 192.168.0.1#53 in 26 ms Trying "google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26122 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com. IN AAAA ;; ANSWER SECTION: google.com. 184 IN AAAA 2a00:1450:4001:81d::200e Received 56 bytes from 192.168.0.1#53 in 25 ms Trying "google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2467 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com. IN MX ;; ANSWER SECTION: google.com. 327 IN MX 30 alt2.aspmx.l.google.com. google.com. 327 IN MX 20 alt1.aspmx.l.google.com. google.com. 327 IN MX 50 alt4.aspmx.l.google.com. google.com. 327 IN MX 10 aspmx.l.google.com. google.com. 327 IN MX 40 alt3.aspmx.l.google.com. Received 136 bytes from 192.168.0.1#53 in 24 ms I am not sure if this is the command I should issue, but I get an answer: linux:/home/user # host google.es fe80::1%wlp2s0 Using domain server: Name: fe80::1%wlp2s0 Address: fe80::1%2#53 Aliases: google.es has address 172.217.16.195 google.es has IPv6 address 2a00:1450:4001:817::2003 google.es mail is handled by 50 alt4.aspmx.l.google.com. google.es mail is handled by 20 alt1.aspmx.l.google.com. google.es mail is handled by 10 aspmx.l.google.com. google.es mail is handled by 30 alt2.aspmx.l.google.com. google.es mail is handled by 40 alt3.aspmx.l.google.com. So it seems that my router resolves? The script I made executable. However, the answer is still in German... Stefan Am Montag, 25. Februar 2019, 16:18:41 CET schrieb Carlos E. R.:

On 25/02/2019 14.55, Stefan Vater wrote:

...

Hi Carlos,

Here is the output:

linux:/home/user # cat /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" search localdomain nameserver 192.168.0.1 nameserver fe80::1%enp0s31f6

First thing to check is that 192.168.0.1 resolves. Try:

host -v google.com 192.168.0.1

I have my doubts about that IPv6 nameserver. Test it. I don't know the IPv6 address of my router, so I try against a local machine, and after opening the firewall, it works (before, I got timeout):

cer@Telcontar:~> host google.es fe80::4ecc:6aff:fe61:50a1%eth0 ;; connection timed out; no servers could be reached cer@Telcontar:~>

Message in the firewall:

...

<0.4> 2019-02-25T16:07:58.738832+01:00 Isengard kernel - - - [4900477.127385] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=4c:cc:6a:61:50:a1:00:21:85:16:2d:0b:86:dd SRC=fe80:0000:0000:0000:0221:85ff:fe16:2d0b DST=fe80:0000:0000:0000:4ecc:6aff:fe61:50a1 LEN=75 TC=0 HOPLIMIT=64 FLOWLBL=401697 PROTO=UDP SPT=57025 DPT=53 LEN=35 So I do know it is reaching the correct machine.

Now:

cer@Telcontar:~> host google.es fe80::4ecc:6aff:fe61:50a1%eth0 Using domain server: Name: fe80::4ecc:6aff:fe61:50a1%eth0 Address: fe80::4ecc:6aff:fe61:50a1%2#53 Aliases:

google.es has address 216.58.201.131 google.es has IPv6 address 2a00:1450:4003:80a::2003 google.es mail is handled by 30 alt2.aspmx.l.google.com. google.es mail is handled by 20 alt1.aspmx.l.google.com. google.es mail is handled by 50 alt4.aspmx.l.google.com. google.es mail is handled by 40 alt3.aspmx.l.google.com. google.es mail is handled by 10 aspmx.l.google.com. cer@Telcontar:~>

...

linux:/home/user # cat /etc/host.conf | egrep -v "^[[:space:]]*$|^#" order hosts, bind multi on

It is correct.

...

Somehow your script for getting English messages does not work for me...

Did you flag it executable?

-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

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: 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

On 25. 02. 19, 17:50, Stefan Vater wrote:

cool! That helps! Thanks a lot!

Everything seems to work again. So should I disable this service or should I reconfigure it?

I don't know. nscd is a piece of crap causing me troubles like this every now and then. I never managed to report the issue. So if you could finally report it to bugzilla, add me to CC, I would be glad :). thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org