Hi zusammen,
ich verwende Ubuntu 24.04 LS mit der Standardoberfläche Gnome. Der Router ist eine Fritzbox 7530 AX. Seit gestern kann ich mich plötzlich mit meinem Lenovo ThinkPad L590 nicht mehr mit dem Netzwerk verbinden - nicht mit dem Router oder einem anderen Gerät. Weder mit LAN noch mit WLAN. Im Gnome-status-Menü rechts oben fehlt auch das Icon für die Netzanbindung. Alle meine anderen Geräte funktionieren problemlos.
Hier noch ein paar Systemdaten:
uname -a Linux thomas-laptop 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
lspci -nnk -d::0280 5:00.0 Network controller [0280]: Intel Corporation Wi-Fi 5(802.11ac) Wireless-AC 9x6x [Thunder Peak] [8086:2526] (rev 29) Subsystem: Intel Corporation Wireless-AC 9260 [8086:0010] Kernel driver in use: iwlwifi Kernel modules: iwlwifi
lspci -nnk -d::0200 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (6) I219-V [8086:15be] (rev 30) Subsystem: Lenovo Ethernet Connection (6) I219-V [17aa:5075] Kernel driver in use: e1000e Kernel modules: e1000e
ip link
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 98:fa:9b:f3:e8:73 brd ff:ff:ff:ff:ff:ff
3: wlp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
link/ether 7c:b2:7d:69:18:2e brd ff:ff:ff:ff:ff:ff
4: enx207bd2c7ccc3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 20:7b:d2:c7:cc:c3 brd ff:ff:ff:ff:ff:ffip addr
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 98:fa:9b:f3:e8:73 brd ff:ff:ff:ff:ff:ff
3: wlp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 7c:b2:7d:69:18:2e brd ff:ff:ff:ff:ff:ff
4: enx207bd2c7ccc3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 20:7b:d2:c7:cc:c3 brd ff:ff:ff:ff:ff:ffip -4 route und ip -6 route und ip neigh bringen kein Ergebnis
Für die Netzwerkkonfiguration wird der NetworkManager verwendet
Konfiguration des NetworkManagers:
nmcli general ; nmcli device ; nmcli connection STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN nicht verbunden kein aktiviert aktiviert missing aktiviert DEVICE TYPE STATE CONNECTION wlp5s0 wifi nicht verbunden -- enp0s31f6 ethernet nicht verwaltet -- enx207bd2c7ccc3 ethernet nicht verwaltet -- lo loopback nicht verwaltet -- p2p-dev-wlp5s0 wifi-p2p nicht verwaltet --
thomas@thomas-laptop:~$ resolvectl --no-pager
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (enp0s31f6)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (wlp5s0)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 4 (enx207bd2c7ccc3)
Current Scopes: none
Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupportedthomas@thomas-laptop:~$ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Apr 24 12:47 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
thomas@thomas-laptop:~$ cat /etc/resolv.conf # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search .
thomas@thomas-laptop:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 thomas-laptop # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters
homas@thomas-laptop:~$ sudo ss -pan 'sport = 53'
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 127.0.0.54:53 0.0.0.0:* users:(("systemd-resolve",pid=924,fd=16))
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=924,fd=14))
tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* users:(("systemd-resolve",pid=924,fd=17))
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=924,fd=15)) Danke für eure Hilfe! Thomas
