You are not logged in.

#1 2020-01-24 12:39:21

schnafte
Member
Registered: 2020-01-24
Posts: 1

[Solved] Migration to new hardware: network interfaces are unmanaged

Migration to new hardware: network interfaces are unmanaged


Hello,

I hope you can help me with my problem. I had an installation of Arch on my Lenovo X1 Carbon (3rd Gen.).
Because of performance issues I wanted to switch to a Fujitsu office PC. I used dd, gzip and netcat to sync both hard drives. Then I mounted the partitions accordingly, ran "mkinitcpio -p linux", then genfstab and at the end grub-install (with some adjustments in the config files). Reboot and nearly everything worked again with the exception of the network.

I used NetworkManager. Now after restart, it is like this:

ip a

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 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 4c:52:62:27:65:d9 brd ff:ff:ff:ff:ff:ff
    inet6 fd3e:3ed5:ea15:0:4e52:62ff:fe27:65d9/64 scope global dynamic mngtmpaddr 
       valid_lft forever preferred_lft forever
    inet6 fe80::4e52:62ff:fe27:65d9/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:e3:38:dc:4b 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
4: br-3770b2778780: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:04:3d:90:f3 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-3770b2778780
       valid_lft forever preferred_lft forever
nmcli

br-3770b2778780: connected to br-3770b2778780
        "br-3770b2778780"
        bridge, 02:42:04:3D:90:F3, sw, mtu 1500
        inet4 172.18.0.1/16
        route4 172.18.0.0/16

docker0: connected to docker0
        "docker0"
        bridge, 02:42:E3:38:DC:4B, sw, mtu 1500
        inet4 172.17.0.1/16
        route4 172.17.0.0/16

eth0: unmanaged
        "Intel Ethernet"
        ethernet (e1000e), 4C:52:62:27:65:D9, 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.
sudo nmcli device set eth0 managed yes
...
Jan 24 13:32:30 fujitsu NetworkManager[6132]: <info>  [1579869150.3431] audit: op="device-managed" arg="managed" pid=6200 uid=0 result="success"
sudo journalctl -u NetworkManager.service

-- Reboot --
Jan 24 13:31:56 fujitsu systemd[1]: Starting Network Manager...
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.6325] NetworkManager (version 1.22.4-1) is starting... (for the first time)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.6326] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Jan 24 13:31:56 fujitsu systemd[1]: Started Network Manager.
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.6344] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.6396] manager[0x55684e38a190]: monitoring kernel firmware directory '/lib/firmware'.
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8741] hostname: hostname: using hostnamed
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8741] hostname: hostname changed from (none) to "fujitsu"
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8749] dns-mgr[0x55684e345240]: init: dns=default,systemd-resolved rc-manager=symlink
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8794] manager[0x55684e38a190]: rfkill: Wi-Fi hardware radio set enabled
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8795] manager[0x55684e38a190]: rfkill: WWAN hardware radio set enabled
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8832] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-wwan.so)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8845] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-wifi.so)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8917] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-team.so)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8924] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-ovs.so)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8930] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-adsl.so)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8946] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-bluetooth.so)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8949] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8950] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8951] manager: Networking is enabled by state file
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8956] dhcp-init: Using DHCP client 'internal'
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8963] settings: Loaded settings plugin: keyfile (internal)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8973] device (lo): carrier: link connected
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8976] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.8983] manager: (br-3770b2778780): new Bridge device (/org/freedesktop/NetworkManager/Devices/2)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9004] device (br-3770b2778780): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-s>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9011] device (br-3770b2778780): state change: unavailable -> disconnected (reason 'connection-assumed', sys-ifac>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9018] device (br-3770b2778780): Activation: starting connection 'br-3770b2778780' (ed131138-b911-4500-96e9-87549>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9022] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9040] device (docker0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'e>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9047] device (docker0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state:>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9053] device (docker0): Activation: starting connection 'docker0' (f8c633c2-c8c5-4765-b12b-2087f795190b)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9056] device (eth0): carrier: link connected
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9059] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9105] ovsdb: Could not connect: No such file or directory
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9116] device (br-3770b2778780): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9120] device (br-3770b2778780): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9124] device (docker0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9128] device (docker0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9135] device (br-3770b2778780): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9137] device (br-3770b2778780): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9144] device (docker0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9146] device (docker0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9155] device (br-3770b2778780): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9156] device (br-3770b2778780): state change: secondaries -> activated (reason 'none', sys-iface-state: 'externa>
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9160] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9166] device (br-3770b2778780): Activation: successful, device activated.
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9171] device (docker0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9173] device (docker0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Jan 24 13:31:56 fujitsu NetworkManager[6132]: <info>  [1579869116.9182] device (docker0): Activation: successful, device activated.
sudo lshw -c network

  *-network                 
       description: Ethernet interface
       product: Ethernet Connection (2) I219-LM
       vendor: Intel Corporation
       physical id: 1f.6
       bus info: pci@0000:00:1f.6
       logical name: eth0
       version: 00
       serial: 4c:52:62:27:65:d9
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.8-4 ip=192.168.1.151 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:135 memory:ef100000-ef11ffff
  *-network:0
       description: Ethernet interface
       physical id: 2
       logical name: docker0
       serial: 02:42:e3:38:dc:4b
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes
  *-network:1
       description: Ethernet interface
       physical id: 3
       logical name: br-3770b2778780
       serial: 02:42:04:3d:90:f3
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.18.0.1 link=no multicast=yes

I can not use the Networkmanager nor systemd-networkd to configure my network devices. On the other hand, configuring it manually with "ip" works and dhcpd, too.
What confuses me, too, is the name of the network interface. I thought network interfaces will have "more appropriate" names.

Let me know if you need more information to help me.

Thank you in advance!


Edit:

Problem solved.

Solution: Updated via "pacman -Syu" (there was a new linux package) and regnerated (another time) the linux image for booting. Reboot. Network is not unmanaged anymore and the device is now shown as "enp0s31f6" again.

Last edited by schnafte (2020-01-24 13:32:45)

Offline

Board footer

Powered by FluxBB