Feste IP Adresse funktioniert nicht richtig in LEAP 15.2

imhotep · October 13, 2020, 7:20pm

Hallo Leute,

nachdem ich LEAP 15.2 installiert habe, funktioniert die feste IP Adresse nicht mehr richtig. Das heißt, manche Verbindungen funktionieren, andere nicht.

Fehlerfall mit fester IP.
Hallo Leute,

nachdem ich LEAP 15.2 installiert habe, funktioniert die feste IP Adresse nicht mehr richtig. Das heißt, manche Verbindungen funktionieren, andere nicht.

Fehlerfall mit fester IP:

imhotep:~ # wicked show all    
lo              up
      link:     #1, state up
      type:     loopback
      config:   compat:suse:/etc/sysconfig/network/ifcfg-lo
      leases:   ipv4 static granted
      leases:   ipv6 static granted
      addr:     ipv4 127.0.0.1/8 [static]
      addr:     ipv6 ::1/128 [static]

eth0            device-unconfigured
      link:     #2, state down, mtu 1500
      type:     ethernet, hwaddr 00:13:3b:0f:40:73

eth1            up
      link:     #3, state up, mtu 1500
      type:     ethernet, hwaddr 10:7b:44:19:59:96
      config:   compat:suse:/etc/sysconfig/network/ifcfg-eth1
      leases:   ipv4 static granted
      addr:     ipv4 192.168.2.20/24 [static]
      addr:     ipv6 2003:c6:6720:fc92:7437:eda5:65a3:a387/64
      addr:     ipv6 2003:c6:6720:fc92:127b:44ff:fe19:5996/64
imhotep:~ # ping www.spiegel.de
connect: Network is unreachable
imhotep:~ # ping www.amazon.de
connect: Network is unreachable
imhotep:~ # ping www.heise.de
PING www.heise.de(www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85)) 56 data bytes
64 bytes from www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85): icmp_seq=1 ttl=57 time=10.2 ms
64 bytes from www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85): icmp_seq=2 ttl=57 time=10.4 ms
64 bytes from www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85): icmp_seq=3 ttl=57 time=10.8 ms
^C
--- www.heise.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 10.294/10.517/10.847/0.238 ms

Mit DHCP funktioniert es.

imhotep:~ # wicked show all
lo              up
      link:     #1, state up
      type:     loopback
      config:   compat:suse:/etc/sysconfig/network/ifcfg-lo
      leases:   ipv4 static granted
      leases:   ipv6 static granted
      addr:     ipv4 127.0.0.1/8 [static]
      addr:     ipv6 ::1/128 [static]

eth0            device-unconfigured
      link:     #2, state down, mtu 1500
      type:     ethernet, hwaddr 00:13:3b:0f:40:73

eth1            up
      link:     #3, state up, mtu 1500
      type:     ethernet, hwaddr 10:7b:44:19:59:96
      config:   compat:suse:/etc/sysconfig/network/ifcfg-eth1
      leases:   ipv4 static granted, ipv4 dhcp granted
      leases:   ipv6 dhcp granted
      addr:     ipv4 192.168.2.20/24 [static]
      addr:     ipv4 192.168.2.116/24 [dhcp]
      addr:     ipv6 2003:c6:6720:fc92:7437:eda5:65a3:a387/64
      addr:     ipv6 2003:c6:6720:fc92:127b:44ff:fe19:5996/64
      route:    ipv4 default via 192.168.2.10 proto dhcp
      route:    ipv6 default via fe80::1 metric 1024 proto ra
imhotep:~ # ping [www.heise.de](http://www.heise.de)
PING [www.heise.de(www.heise.de](http://www.heise.de(www.heise.de) (2a02:2e0:3fe:1001:7777:772e:2:85)) 56 data bytes
64 bytes from [www.heise.de](http://www.heise.de) (2a02:2e0:3fe:1001:7777:772e:2:85): icmp_seq=1 ttl=57 time=11.0 ms
64 bytes from [www.heise.de](http://www.heise.de) (2a02:2e0:3fe:1001:7777:772e:2:85): icmp_seq=2 ttl=57 time=10.0 ms
^C
--- [www.heise.de](http://www.heise.de) ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 10.076/10.551/11.027/0.486 ms
imhotep:~ # ping [www.amazon.de](http://www.amazon.de)
PING e15317.e22.akamaiedge.net (23.211.1.36) 56(84) bytes of data.
64 bytes from a23-211-1-36.deploy.static.akamaitechnologies.com (23.211.1.36): icmp_seq=1 ttl=60 time=8.39 ms
64 bytes from a23-211-1-36.deploy.static.akamaitechnologies.com (23.211.1.36): icmp_seq=2 ttl=60 time=8.16 ms
^C
--- e15317.e22.akamaiedge.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 8.167/8.280/8.394/0.145 ms
imhotep:~ # ping [www.spiegel.de](http://www.spiegel.de)
PING aacfb9d106f4.link11.de (128.65.210.180) 56(84) bytes of data.
64 bytes from 128.65.210.180 (128.65.210.180): icmp_seq=1 ttl=56 time=11.5 ms
64 bytes from 128.65.210.180 (128.65.210.180): icmp_seq=2 ttl=56 time=11.5 ms
64 bytes from 128.65.210.180 (128.65.210.180): icmp_seq=3 ttl=56 time=11.6 ms
^C
--- aacfb9d106f4.link11.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 11.528/11.600/11.679/0.061 ms

Kann mir jemand sagen, was an der Konfiguration falsch ist? Oder mir einen Tipp geben, wie ich das debuggen kann?

Viele Grüße

Karsten

Sauerland · October 13, 2020, 9:04pm

Hast du den DNS in Yast—Netzwerk eingerichtet?
Poste:

ls -al /etc/resolv.conf

cat /etc/resolv.conf

Poste auch mal:

nslookup www.heise.de

nslookup www.spiegel.de

imhotep · October 14, 2020, 5:23pm

In Yast ist das auf dem Reiter Hostname/DNS konfiguriert. Es sind alle drei Nameserver eingetragen. Allerdings alle dieselbe Adresse.

ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 26 Oct 11 15:35 /etc/resolv.conf -> /run/netconfig/resolv.conf

Inhalt der resolv.conf

### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
nameserver 192.168.2.10

imhotep:~ # nslookup www.heise.de
Server:         192.168.2.10
Address:        192.168.2.10#53

Non-authoritative answer:
Name:   www.heise.de
Address: 193.99.144.85
Name:   www.heise.de
Address: 2a02:2e0:3fe:1001:7777:772e:2:85

imhotep:~ # nslookup www.spiegel.de
Server:         192.168.2.10
Address:        192.168.2.10#53

Non-authoritative answer:
www.spiegel.de  canonical name = aacfb9d106f4.link11.de.
Name:   aacfb9d106f4.link11.de
Address: 128.65.210.185
Name:   aacfb9d106f4.link11.de
Address: 128.65.210.182
Name:   aacfb9d106f4.link11.de
Address: 128.65.210.183
Name:   aacfb9d106f4.link11.de
Address: 128.65.210.184
Name:   aacfb9d106f4.link11.de
Address: 128.65.210.180
Name:   aacfb9d106f4.link11.de
Address: 128.65.210.181