You are not logged in.

Pages: 1

#1 2023-10-08 14:55:33

djenis
Member
Registered: 2021-04-19
Posts: 82

[SOLVED] Docking station ethernet network interface doesn't work

Hello,

I want to connect to the internet using my docking station's ethernet interface enp4s0f4u1u1i5. However, I can only connect to the internet using either my laptop's WIFI network interfac wlan0 or my laptop's ethernet network interface eno1.

The enp4s0f4u1u1i5 interface works for a while after a reboot but then stops working. I notice that enp4s0f4u1u1i5 doesn't receive a ipv4 IP address... Maybe something is wrong with my DHCP?

Note that in the output below I have disabled my wlan0 WIFI network interface before running the commands.

This is the output from ip 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: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether b0:25:aa:3f:d5:27 brd ff:ff:ff:ff:ff:ff
    altname enp2s0
3: enp4s0f4u1u1i5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 80:6d:97:44:ad:22 brd ff:ff:ff:ff:ff:ff
    inet6 2001:9e8:acf:e300:fd2a:93ab:dfaa:d176/64 scope global dynamic noprefixroute
       valid_lft 7168sec preferred_lft 3568sec
    inet6 2001:9e8:acf:a200:e21f:29e5:6556:bd54/64 scope global deprecated dynamic noprefixroute
       valid_lft 7163sec preferred_lft 0sec
    inet6 2001:9e8:acf:a200:60b7:ed3:8315:b844/64 scope global deprecated dynamic mngtmpaddr noprefixroute
       valid_lft 7162sec preferred_lft 0sec
    inet6 2001:9e8:acf:e300:39c8:dc52:c2ab:ce3/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7167sec preferred_lft 3567sec
    inet6 fe80::fbb2:dfe2:54b4:4547/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether d6:7d:81:44:71:1e brd ff:ff:ff:ff:ff:ff permaddr 78:2b:46:28:d1:6f
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:ac:87:11:30 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

output from ip route show:

172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

Contents from /etc/resolve.config:

# Generated by NetworkManager
search fritz.box
nameserver 192.168.178.1
nameserver fd00::de15:c8ff:fe50:a05c
nameserver 2001:9e8:acf:e300:de15:c8ff:fe50:a05c
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2001:9e8:acf:a200:de15:c8ff:fe50:a05c

Last edited by djenis (2023-11-12 19:44:02)

Offline

#2 2023-10-08 15:26:32

djenis
Member
Registered: 2021-04-19
Posts: 82

Re: [SOLVED] Docking station ethernet network interface doesn't work

Contents of /etc/systemd/network/30-enp4s0f4u1u1i5.network:

[Match]
Name=enp4s0f4u1u1i5

[Network]
DHCP=ipv4

[DHCP]
RouteMetric=10

and the contents of /etc/systemd/network/20-eno1.network:

[Match]
Name=eno1

[Network]
DHCP=ipv4

[DHCP]
RouteMetric=5

Offline

#3 2023-10-08 15:30:55

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,727

Re: [SOLVED] Docking station ethernet network interface doesn't work

So you're using systemd-networkd, NetworkManager, and iwd? Do I have that right?

That's likely your problem. Pick how you want to manage you network and stick with it.

Online

#4 2023-10-08 15:36:28

djenis
Member
Registered: 2021-04-19
Posts: 82

Re: [SOLVED] Docking station ethernet network interface doesn't work

Yes you're right. I have iwd installed but disabled. You're saying that if I want to use NetworkManager I should disable systemd-networkd and delete the files in /etc/systemd/network/?

Offline

#5 2023-10-08 16:29:16

djenis
Member
Registered: 2021-04-19
Posts: 82

Re: [SOLVED] Docking station ethernet network interface doesn't work

So I disabled iwd, systemd-networkd and dhcpd. This means that NetworkManager is the only service managing my network.

Everything works fine for wlan0 and eno1.

But when I try to activate enp4s0f4u1u1i5 using `nmcli connection up "Tuxedo Hub"`

I get the error:

Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)
Hint: use 'journalctl -xe NM_CONNECTION=8f228cb1-a69c-4514-974a-61c6ff0df8dc + NM_DEVICE=enp4s0f4u1u1i5' to get more details.

This is the output of the Hint:

Oct 08 18:20:20 tux NetworkManager[5093]: <info>  [1696782020.2298] device (enp4s0f4u1u1i5): Activation: starting connection 'Tuxedo Hub' (8f228cb1-a69c-4514-974a-61c6ff0df8dc)
Oct 08 18:20:20 tux NetworkManager[5093]: <info>  [1696782020.2301] device (enp4s0f4u1u1i5): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 08 18:20:20 tux NetworkManager[5093]: <info>  [1696782020.2304] device (enp4s0f4u1u1i5): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 08 18:20:20 tux NetworkManager[5093]: <info>  [1696782020.2307] device (enp4s0f4u1u1i5): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 08 18:20:20 tux NetworkManager[5093]: <info>  [1696782020.2312] dhcp4 (enp4s0f4u1u1i5): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:21:05 tux NetworkManager[5093]: <info>  [1696782065.0361] device (enp4s0f4u1u1i5): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 08 18:21:05 tux NetworkManager[5093]: <warn>  [1696782065.0365] device (enp4s0f4u1u1i5): Activation: failed for connection 'Tuxedo Hub'
Oct 08 18:21:05 tux NetworkManager[5093]: <info>  [1696782065.0368] device (enp4s0f4u1u1i5): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 08 18:21:05 tux NetworkManager[5093]: <info>  [1696782065.0638] dhcp4 (enp4s0f4u1u1i5): canceled DHCP transaction
Oct 08 18:21:05 tux NetworkManager[5093]: <info>  [1696782065.0639] dhcp4 (enp4s0f4u1u1i5): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:21:05 tux NetworkManager[5093]: <info>  [1696782065.0639] dhcp4 (enp4s0f4u1u1i5): state changed no lease

I googled the " failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')" problem and landed on an old threat where Seth recommends using a different dhcp client for NetworkManager: https://bbs.archlinux.org/viewtopic.php … 5#p1755185

There must be somthing else I can do, no?

Offline

#6 2023-10-08 16:56:14

djenis
Member
Registered: 2021-04-19
Posts: 82

Re: [SOLVED] Docking station ethernet network interface doesn't work

I switched to the dhclient but "Tuxedo Hub" is still not getting an ipv4 address:

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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether b0:25:aa:3f:d5:27 brd ff:ff:ff:ff:ff:ff
    altname enp2s0
    inet 192.168.178.146/24 brd 192.168.178.255 scope global dynamic noprefixroute eno1
       valid_lft 863864sec preferred_lft 863864sec
    inet6 2001:9e8:ad0:2100:2679:b943:2290:668e/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7196sec preferred_lft 3596sec
    inet6 2001:9e8:ad0:2100:c478:35a4:f157:a0ed/64 scope global dynamic noprefixroute
       valid_lft 7197sec preferred_lft 3597sec
    inet6 fe80::f7d8:8e9c:945a:643a/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp4s0f4u1u1i5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 80:6d:97:44:ad:22 brd ff:ff:ff:ff:ff:ff
    inet6 2001:9e8:ad0:2100:6da8:1dbc:405d:1147/64 scope global dynamic noprefixroute
       valid_lft 7197sec preferred_lft 3597sec
    inet6 2001:9e8:ad0:2100:3dd1:1827:6706:b37f/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7196sec preferred_lft 3596sec
    inet6 fe80::e8b2:380:db89:2444/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 78:2b:46:28:d1:6f brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.78/24 brd 192.168.178.255 scope global dynamic noprefixroute wlan0
       valid_lft 863875sec preferred_lft 863875sec
    inet6 2001:9e8:ad0:2100:322b:5e49:6a22:e070/64 scope global dynamic noprefixroute
       valid_lft 7115sec preferred_lft 3515sec
    inet6 2001:9e8:ad0:2100:16b7:ed48:f14:ff4a/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 7114sec preferred_lft 3514sec
    inet6 fe80::1f5b:48c7:596d:de87/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:f4:55:64:4e brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

Output from journalctl -b -u NetworkManager:

Oct 08 18:50:15 tux systemd[1]: Starting Network Manager...
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.0734] NetworkManager (version 1.44.2-1) is starting... (after a restart, boot:f0f7db75-17e6-43d8-b967-d4a8563e903a)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.0735] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.0790] manager[0x55b987c06190]: monitoring kernel firmware directory '/lib/firmware'.
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1252] hostname: hostname: using hostnamed
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1253] hostname: static hostname changed from (none) to "tux"
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1256] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1290] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1297] manager[0x55b987c06190]: rfkill: Wi-Fi hardware radio set enabled
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1297] manager[0x55b987c06190]: rfkill: WWAN hardware radio set enabled
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1323] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-adsl.so)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1346] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-wwan.so)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1352] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-ovs.so)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1360] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-bluetooth.so)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1509] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-team.so)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1515] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-wifi.so)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1519] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1520] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1520] manager: Networking is enabled by state file
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1523] settings: Loaded settings plugin: keyfile (internal)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1591] dhcp: init: Using DHCP client 'dhclient'
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1595] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1601] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1606] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1617] device (lo): Activation: starting connection 'lo' (e2211062-50cb-4e2a-adf9-56fe5429037d)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1626] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/2)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1646] device (docker0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1652] device (docker0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1660] device (docker0): Activation: starting connection 'docker0' (30aea478-a4e0-4dd2-aa2f-8e1029b81c79)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1670] device (eno1): carrier: link connected
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1677] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1683] manager: (eno1): assume: will attempt to assume matching connection 'Laptop' (2329640d-8434-4c16-bf08-3a9f2e05e27d) (indicated)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1683] device (eno1): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1695] device (eno1): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1712] device (eno1): Activation: starting connection 'Laptop' (2329640d-8434-4c16-bf08-3a9f2e05e27d)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1719] device (enp4s0f4u1u1i5): carrier: link connected
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1729] manager: (enp4s0f4u1u1i5): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1732] device (enp4s0f4u1u1i5): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1747] device (wlan0): driver supports Access Point (AP) mode
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1751] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/5)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.1752] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.4225] device (wlan0): set-hw-addr: set MAC address to 66:D0:7F:FC:B8:F3 (scanning)
Oct 08 18:50:15 tux systemd[1]: Started Network Manager.
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6342] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6433] ovsdb: disconnected from ovsdb
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6435] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6438] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6441] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6447] device (docker0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6450] device (docker0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6452] device (docker0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6454] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6457] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6496] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6502] device (docker0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6508] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6598] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6648] dhcp4 (eno1): dhclient started with pid 4635
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6655] device (enp4s0f4u1u1i5): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6671] policy: auto-activating connection 'Tuxedo Hub' (8f228cb1-a69c-4514-974a-61c6ff0df8dc)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6673] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6675] device (docker0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6684] device (enp4s0f4u1u1i5): Activation: starting connection 'Tuxedo Hub' (8f228cb1-a69c-4514-974a-61c6ff0df8dc)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6684] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6689] device (lo): Activation: successful, device activated.
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6695] device (docker0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6699] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6702] device (docker0): Activation: successful, device activated.
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6708] device (enp4s0f4u1u1i5): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6711] manager: NetworkManager state is now CONNECTING
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6713] device (enp4s0f4u1u1i5): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6729] device (enp4s0f4u1u1i5): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6737] dhcp4 (enp4s0f4u1u1i5): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.6770] dhcp4 (enp4s0f4u1u1i5): dhclient started with pid 4641
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7057] device (wlan0): supplicant interface state: internal-starting -> disconnected
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7058] Wi-Fi P2P device controlled by interface wlan0 created
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7061] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7063] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7068] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7072] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:15 tux dhclient[4635]: DHCPREQUEST for 192.168.178.152 on eno1 to 255.255.255.255 port 67
Oct 08 18:50:15 tux dhclient[4635]: DHCPNAK from 192.168.178.1
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7124] dhcp4 (eno1): state changed no lease
Oct 08 18:50:15 tux dhclient[4635]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 4
Oct 08 18:50:15 tux dhclient[4635]: DHCPOFFER of 192.168.178.146 from 192.168.178.1
Oct 08 18:50:15 tux dhclient[4635]: DHCPREQUEST for 192.168.178.146 on eno1 to 255.255.255.255 port 67
Oct 08 18:50:15 tux dhclient[4641]: DHCPDISCOVER on enp4s0f4u1u1i5 to 255.255.255.255 port 67 interval 6
Oct 08 18:50:15 tux dhclient[4635]: DHCPACK of 192.168.178.146 from 192.168.178.1
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7245] dhcp4 (eno1):   address 192.168.178.146
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7245] dhcp4 (eno1):   plen 24 (255.255.255.0)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7245] dhcp4 (eno1):   gateway 192.168.178.1
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7246] dhcp4 (eno1):   lease time 864000
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7246] dhcp4 (eno1):   nameserver '192.168.178.1'
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7246] dhcp4 (eno1):   domain name 'fritz.box'
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7246] dhcp4 (eno1): state changed new lease, address=192.168.178.146
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7248] policy: set 'Laptop' (eno1) as default for IPv4 routing and DNS
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7391] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7400] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7402] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'assume')
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7403] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7405] device (eno1): Activation: successful, device activated.
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7411] dhcp6 (eno1): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7437] dhcp6 (eno1): dhclient started with pid 4677
Oct 08 18:50:15 tux dhclient[4635]: bound to 192.168.178.146 -- renewal in 374897 seconds.
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.7449] policy: set 'Laptop' (eno1) as default for IPv6 routing and DNS
Oct 08 18:50:15 tux NetworkManager[4618]: <info>  [1696783815.8079] agent-manager: agent[2000a0d37ca69e43,:1.36/org.freedesktop.nm-applet/1000]: agent registered
Oct 08 18:50:16 tux dhclient[4677]: XMT: Info-Request on eno1, interval 930ms.
Oct 08 18:50:16 tux dhclient[4677]: RCV: Reply message on eno1 from fe80::de15:c8ff:fe50:a05c.
Oct 08 18:50:16 tux NetworkManager[4618]: <info>  [1696783816.5235] dhcp6 (eno1):   nameserver 'fd00::de15:c8ff:fe50:a05c'
Oct 08 18:50:16 tux NetworkManager[4618]: <info>  [1696783816.5235] dhcp6 (eno1):   nameserver '2001:9e8:ad0:2100:de15:c8ff:fe50:a05c'
Oct 08 18:50:16 tux NetworkManager[4618]: <info>  [1696783816.5235] dhcp6 (eno1): state changed new lease
Oct 08 18:50:16 tux NetworkManager[4618]: <info>  [1696783816.5259] dhcp6 (eno1): client pid 4677 exited with status 0
Oct 08 18:50:16 tux NetworkManager[4618]: <info>  [1696783816.5260] dhcp6 (eno1): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:16 tux NetworkManager[4618]: <info>  [1696783816.5260] dhcp6 (eno1): state changed no lease
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3610] policy: auto-activating connection 'FRITZ!Box 7530 OL' (82e8885c-4a74-45fc-a847-8ba94aec7c1d)
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3618] device (wlan0): Activation: starting connection 'FRITZ!Box 7530 OL' (82e8885c-4a74-45fc-a847-8ba94aec7c1d)
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3620] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3957] device (wlan0): set-hw-addr: reset MAC address to 78:2B:46:28:D1:6F (preserve)
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3974] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3977] device (wlan0): Activation: (wifi) access point 'FRITZ!Box 7530 OL' has security, but secrets are required.
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3978] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3979] sup-iface[04f8b367631a1d6d,2,wlan0]: wps: type pbc start...
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3992] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3995] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3998] device (wlan0): Activation: (wifi) connection 'FRITZ!Box 7530 OL' has security, and secrets exist.  No new secrets needed.
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3998] Config: added 'ssid' value 'FRITZ!Box 7530 OL'
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3998] Config: added 'scan_ssid' value '1'
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3998] Config: added 'bgscan' value 'simple:30:-65:300'
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3999] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.3999] Config: added 'psk' value '<hidden>'
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.4738] device (wlan0): supplicant interface state: disconnected -> authenticating
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.4739] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> authenticating
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.5245] device (wlan0): supplicant interface state: authenticating -> associating
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.5245] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.5467] device (wlan0): supplicant interface state: associating -> 4way_handshake
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.5467] device (p2p-dev-wlan0): supplicant management interface state: associating -> 4way_handshake
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.6286] device (wlan0): supplicant interface state: 4way_handshake -> completed
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.6286] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "FRITZ!Box 7530 OL"
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.6286] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.6292] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.6297] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:18 tux NetworkManager[4618]: <info>  [1696783818.6316] dhcp4 (wlan0): dhclient started with pid 4701
Oct 08 18:50:18 tux dhclient[4701]: DHCPREQUEST for 192.168.178.151 on wlan0 to 255.255.255.255 port 67
Oct 08 18:50:19 tux NetworkManager[4618]: <info>  [1696783819.7030] dhcp6 (enp4s0f4u1u1i5): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:19 tux NetworkManager[4618]: <info>  [1696783819.7148] dhcp6 (enp4s0f4u1u1i5): dhclient started with pid 4709
Oct 08 18:50:19 tux NetworkManager[4618]: <info>  [1696783819.8423] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:19 tux NetworkManager[4618]: <info>  [1696783819.8550] dhcp6 (wlan0): dhclient started with pid 4712
Oct 08 18:50:20 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 930ms.
Oct 08 18:50:20 tux dhclient[4712]: XMT: Info-Request on wlan0, interval 930ms.
Oct 08 18:50:20 tux dhclient[4712]: RCV: Reply message on wlan0 from fe80::de15:c8ff:fe50:a05c.
Oct 08 18:50:20 tux NetworkManager[4618]: <info>  [1696783820.6343] dhcp6 (wlan0):   nameserver 'fd00::de15:c8ff:fe50:a05c'
Oct 08 18:50:20 tux NetworkManager[4618]: <info>  [1696783820.6344] dhcp6 (wlan0):   nameserver '2001:9e8:ad0:2100:de15:c8ff:fe50:a05c'
Oct 08 18:50:20 tux NetworkManager[4618]: <info>  [1696783820.6344] dhcp6 (wlan0): state changed new lease
Oct 08 18:50:20 tux NetworkManager[4618]: <info>  [1696783820.6358] dhcp6 (wlan0): client pid 4712 exited with status 0
Oct 08 18:50:20 tux NetworkManager[4618]: <info>  [1696783820.6358] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:50:20 tux NetworkManager[4618]: <info>  [1696783820.6358] dhcp6 (wlan0): state changed no lease
Oct 08 18:50:21 tux dhclient[4641]: DHCPDISCOVER on enp4s0f4u1u1i5 to 255.255.255.255 port 67 interval 9
Oct 08 18:50:21 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 1800ms.
Oct 08 18:50:21 tux NetworkManager[4618]: <info>  [1696783821.8362] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:21 tux NetworkManager[4618]: <info>  [1696783821.8387] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:21 tux NetworkManager[4618]: <info>  [1696783821.8390] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 08 18:50:21 tux NetworkManager[4618]: <info>  [1696783821.8403] device (wlan0): Activation: successful, device activated.
Oct 08 18:50:23 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 3510ms.
Oct 08 18:50:26 tux dhclient[4701]: DHCPREQUEST for 192.168.178.151 on wlan0 to 255.255.255.255 port 67
Oct 08 18:50:26 tux dhclient[4701]: DHCPNAK from 192.168.178.1
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7080] dhcp4 (wlan0): state changed no lease
Oct 08 18:50:26 tux dhclient[4701]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Oct 08 18:50:26 tux dhclient[4701]: DHCPOFFER of 192.168.178.78 from 192.168.178.1
Oct 08 18:50:26 tux dhclient[4701]: DHCPREQUEST for 192.168.178.78 on wlan0 to 255.255.255.255 port 67
Oct 08 18:50:26 tux dhclient[4701]: DHCPACK of 192.168.178.78 from 192.168.178.1
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7305] dhcp4 (wlan0):   address 192.168.178.78
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7305] dhcp4 (wlan0):   plen 24 (255.255.255.0)
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7305] dhcp4 (wlan0):   gateway 192.168.178.1
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7306] dhcp4 (wlan0):   lease time 864000
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7306] dhcp4 (wlan0):   nameserver '192.168.178.1'
Oct 08 18:50:26 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 7250ms.
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7306] dhcp4 (wlan0):   domain name 'fritz.box'
Oct 08 18:50:26 tux NetworkManager[4618]: <info>  [1696783826.7306] dhcp4 (wlan0): state changed new lease, address=192.168.178.78
Oct 08 18:50:26 tux dhclient[4701]: bound to 192.168.178.78 -- renewal in 357963 seconds.
Oct 08 18:50:30 tux dhclient[4641]: DHCPDISCOVER on enp4s0f4u1u1i5 to 255.255.255.255 port 67 interval 10
Oct 08 18:50:33 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 14940ms.
Oct 08 18:50:40 tux dhclient[4641]: DHCPDISCOVER on enp4s0f4u1u1i5 to 255.255.255.255 port 67 interval 7
Oct 08 18:50:47 tux dhclient[4641]: DHCPDISCOVER on enp4s0f4u1u1i5 to 255.255.255.255 port 67 interval 13
Oct 08 18:50:48 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 30240ms.
Oct 08 18:51:00 tux dhclient[4641]: DHCPDISCOVER on enp4s0f4u1u1i5 to 255.255.255.255 port 67 interval 11
Oct 08 18:51:05 tux NetworkManager[4618]: <info>  [1696783865.0213] device (enp4s0f4u1u1i5): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 08 18:51:05 tux NetworkManager[4618]: <info>  [1696783865.0664] device (enp4s0f4u1u1i5): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 08 18:51:05 tux NetworkManager[4618]: <info>  [1696783865.0667] device (enp4s0f4u1u1i5): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 08 18:51:05 tux NetworkManager[4618]: <info>  [1696783865.0673] device (enp4s0f4u1u1i5): Activation: successful, device activated.
Oct 08 18:51:05 tux NetworkManager[4618]: <info>  [1696783865.0678] manager: startup complete
Oct 08 18:51:11 tux dhclient[4641]: DHCPDISCOVER on enp4s0f4u1u1i5 to 255.255.255.255 port 67 interval 5
Oct 08 18:51:16 tux dhclient[4641]: No DHCPOFFERS received.
Oct 08 18:51:16 tux dhclient[4641]: No working leases in persistent database - sleeping.
Oct 08 18:51:16 tux NetworkManager[4618]: <info>  [1696783876.5715] dhcp4 (enp4s0f4u1u1i5): activation: beginning transaction (timeout in 45 seconds)
Oct 08 18:51:16 tux NetworkManager[4618]: <info>  [1696783876.5715] dhcp4 (enp4s0f4u1u1i5): state changed no lease
Oct 08 18:51:19 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 63100ms.
Oct 08 18:52:22 tux dhclient[4709]: XMT: Info-Request on enp4s0f4u1u1i5, interval 125080ms.

Offline

#7 2023-11-12 19:43:39

djenis
Member
Registered: 2021-04-19
Posts: 82

Re: [SOLVED] Docking station ethernet network interface doesn't work

Solved, see: https://bbs.archlinux.org/viewtopic.php?id=289641

Offline

Pages: 1

Board footer

Powered by FluxBB