On Thu, Aug 25, 2022 at 10:50:01PM +0200, Michael Biebl wrote: > Output of "nmcli" as well, please.
wlp61s0: connected to sirena
"Intel 8265 / 8275"
wifi (iwlwifi), 48:F1:7F:C0:88:CF, hw, mtu 1500
ip4 default
inet4 192.168.8.100/16
route4 192.168.0.0/16
route4 0.0.0.0/0
inet6 fe80::788e:1990:4d51:7a42/64
route6 fe80::/64
docker0: connected to docker0
"docker0"
bridge, 02:42:62:06:90:BF, sw, mtu 1500
inet4 172.17.0.1/16
route4 172.17.0.0/16
inet6 fe80::ddf5:758f:ebbd:71dc/64
route6 fe80::/64
lxcbr0: connected to lxcbr0
"lxcbr0"
bridge, 00:16:3E:00:00:00, sw, mtu 1500
inet4 10.0.3.1/24
route4 10.0.3.0/24
route4 169.254.0.0/16
p2p-dev-wlp61s0: disconnected
"p2p-dev-wlp61s0"
wifi-p2p, hw
enp0s31f6: unavailable
"Intel Ethernet"
ethernet (e1000e), E8:6A:64:AB:B8:78, hw, mtu 1500
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
> Is /etc/resolv.conf a real file or a symlink pointing somewhere?
Normal file.
-rw-r--r-- 1 root root 72 Aug 26 19:15 /etc/resolv.conf
> Please also post the content of /run/NetworkManager/no-stub-resolv.conf
# Generated by NetworkManager
nameserver 192.168.8.1
(which is good for this network).
signature.asc
Description: PGP signature
