upgrade 5 to 6 now some interfaces don't come up

[Thomas Stone]

Hello:

I upgraded from latest v5 to v6 today (16th July 2020). It went well except networking. It is certainly possible that in the past I have done bad things to my /etc/network/interfaces file that is causing it. Another possible issue is I installed Cinnamon deskop on the machine (after v6 update) which had its own network manager -- I disabled it however.

Currently, on boot I get about a 5 minute hang at raising network interface. systemctl status networkingshows:

Jul 16 16:42:32 pvea ifup[2318]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
Jul 16 16:42:31 pvea systemd[1]: Starting Raise network interfaces...
Jul 16 16:47:32 pvea systemd[1]: networking.service: Start operation timed out. Terminating.
Jul 16 16:47:32 pvea systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jul 16 16:47:32 pvea ifup[2318]: Got signal Terminated, terminating...
Jul 16 16:47:32 pvea ifup[2318]: ifup: failed to bring up vmbr0
Jul 16 16:47:32 pvea systemd[1]: networking.service: Failed with result 'timeout'.
Jul 16 16:47:32 pvea systemd[1]: Failed to start Raise network interfaces.

When the boot completes I actually do have vmbr0 working, but not the other one I need, vmbr2. Interestingly, if I then just issue ifup vmbr2 it comes up fine. Proxmox gui shows Autostart Yes for vmbr0 and vmbr2.

Here's /etc/network/interfaces:

auto lo
iface lo inet loopback

iface enp42s0 inet manual

iface enp45s0 inet manual

iface enp47s0f0 inet manual
        mtu 9000

iface enp47s0f1 inet manual
        mtu 9000

auto vmbr0
iface vmbr0 inet static
        address 10.0.1.2/24
        gateway 10.0.1.1
        bridge-ports enp42s0
        bridge-stp off
        bridge-fd 0
#Main Lan Bridge

iface vmbr1 inet static
        address 172.16.14.2/24
        bridge-ports enp45s0
        bridge-stp off
        bridge-fd 0
#10GAquantia

auto vmbr2
iface vmbr2 inet static
        address 172.16.16.2/24
        bridge-ports enp47s0f0
        bridge-stp off
        bridge-fd 0
        mtu 9000
#SFPTop

iface vmbr3 inet static
        address 172.16.15.2/24
        bridge-ports enp47s0f1
        bridge-stp off
        bridge-fd 0
        mtu 9000
#SFPBottom

Thanks for any suggestions.

 

[Stoiko Ivanov]

maybe the interfaces changed their name (sadly the predictable network names sometimes are not predictable

check the output of `ip link` - are the names the ones you have in /etc/network/interfaces?

 

[Thomas Stone]

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: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:82:52:ad brd ff:ff:ff:ff:ff:ff
3: enp47s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq master vmbr2 state UP mode DEFAULT group default qlen 1000
    link/ether 00:1b:21:bd:96:10 brd ff:ff:ff:ff:ff:ff
4: enp45s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:82:52:af brd ff:ff:ff:ff:ff:ff
5: enp47s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:1b:21:bd:96:12 brd ff:ff:ff:ff:ff:ff
6: wlp39s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 68:ec:c5:bf:1a:fd brd ff:ff:ff:ff:ff:ff
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:82:52:ad brd ff:ff:ff:ff:ff:ff
8: veth111i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:a0:23:0d:f7:b9 brd ff:ff:ff:ff:ff:ff link-netnsid 0
9: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether aa:7c:72:9f:97:33 brd ff:ff:ff:ff:ff:ff
10: veth105i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:87:5e:a7:25:d0 brd ff:ff:ff:ff:ff:ff link-netnsid 1
11: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 00:1b:21:bd:96:10 brd ff:ff:ff:ff:ff:ff

so, yes and no. not sure what veth1xxxx ones are!

 

[Stoiko Ivanov]

hm - I think that vmbr3 is not up because there is no 'auto vmbr3' line.

what's the output of `ifup -a`?


as for the veth interfaces - these are the virtual ones for guests

 

[Thomas Stone]

H/W path                Device     Class          Description
=============================================================
/0/100/1.3/0.2/3/0/1/0  wlp39s0    network        Dual Band Wireless-AC 3168NGW [Stone Peak]
/0/100/1.3/0.2/3/0/5/0  enp42s0    network        I211 Gigabit Network Connection
/0/100/1.3/0.2/9/0      enp45s0    network        AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion]
/0/100/3.2/0            enp47s0f0  network        82599ES 10-Gigabit SFI/SFP+ Network Connection
/0/100/3.2/0.1          enp47s0f1  network        82599ES 10-Gigabit SFI/SFP+ Network Connection
/1                      tap100i0   network        Ethernet interface
/2                      vmbr0      network        Ethernet interface
/3                      veth111i0  network        Ethernet interface
/4                      veth105i0  network        Ethernet interface
/5                      vmbr2      network        Ethernet interface

 

[Thomas Stone]

# ifup -a

Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
RTNETLINK answers: File exists
ifup: failed to bring up vmbr0

And yet, vmbr0 is working.

I only want vmbr0 and vmbr2 to be up on boot. Thanks for your help.

 

[Thomas Stone]

I guess the veth* ones are the vmbr ones that are not in auto, no relevant to the problem I guess.

 

[spirit]

I guess the veth* ones are the vmbr ones that are not in auto, no relevant to the problem I guess.

veth interfaces are containers interfaces, created by proxmox when ct start.
tap interfaces are vm interfaces, , created by proxmox when vm start.

 

[Thomas Stone]

Thanks Spirit.

I guess something changed or was cleaned up because I rebooted today and the interfaces came up correctly with no long hangs!