vmbr0 interface not created after boot

B

Bionicao

Active Member
Aug 2, 2018
2
1
43
26
Added a new network card and after a reboot, vmbr0 is not being created. I'm getting errors during boot and ifreload -a. The network interface names look correct.

What else I should change?

/etc/network/interfaces
Code: 
auto lo
iface lo inet loopback

iface enp0s31f6 inet manual

iface enp11s0f0 inet manual

iface enp11s0f1 inet manual

auto enp10s0
iface enp10s0 inet static
        address 192.168.1.103/24
        gateway 192.168.1.1

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.101/24
        bridge_ports enp0s31f6
        bridge_stp off
        bridge_fd 0

ip a
Code: 
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: enp10s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d0:50:99:db:c6:c3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.103/24 scope global enp10s0
       valid_lft forever preferred_lft forever
    inet6 fd46:9f62:6e77:84f0:d250:99ff:fedb:c6c3/64 scope global dynamic mngtmpaddr
       valid_lft 1789sec preferred_lft 1789sec
    inet6 fe80::d250:99ff:fedb:c6c3/64 scope link
       valid_lft forever preferred_lft forever
3: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d0:50:99:db:c6:c4 brd ff:ff:ff:ff:ff:ff
4: enp11s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:21:bb:23:e4 brd ff:ff:ff:ff:ff:ff
5: enp11s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:21:bb:23:e6 brd ff:ff:ff:ff:ff:ff

ifreload -a
Code: 
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 325, in run_iface_list
    cls.run_iface_graph(ifupdownobj, ifacename, ops, parent,
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 315, in run_iface_graph
    cls.run_iface_list_ops(ifupdownobj, ifaceobjs, ops)
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 188, in run_iface_list_ops
    cls.run_iface_op(ifupdownobj, ifaceobj, op,
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 150, in run_iface_op
    ifupdownobj.log_error('%s: %s %s' % (ifacename, op, str(e)))
  File "/usr/share/ifupdown2/ifupdown/ifupdownmain.py", line 226, in log_error
    raise Exception(str)
error: lo : lo: up cmd '/etc/network/if-up.d/vzifup-post' failed: returned 127
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 325, in run_iface_list
    cls.run_iface_graph(ifupdownobj, ifacename, ops, parent,
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 315, in run_iface_graph
    cls.run_iface_list_ops(ifupdownobj, ifaceobjs, ops)
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 188, in run_iface_list_ops
    cls.run_iface_op(ifupdownobj, ifaceobj, op,
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 150, in run_iface_op
    ifupdownobj.log_error('%s: %s %s' % (ifacename, op, str(e)))
  File "/usr/share/ifupdown2/ifupdown/ifupdownmain.py", line 226, in log_error
    raise Exception(str)
error: enp10s0 : enp10s0: up cmd '/etc/network/if-up.d/vzifup-post' failed: returned 127
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 325, in run_iface_list
    cls.run_iface_graph(ifupdownobj, ifacename, ops, parent,
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 302, in run_iface_graph
    cls.run_iface_list(ifupdownobj, dlist, ops,
  File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 337, in run_iface_list
    raise Exception('%s : (%s)' %(ifacename, str(e)))
error: vmbr0 : enp0s31f6 : (enp0s31f6: up cmd '/etc/network/if-up.d/vzifup-post' failed: returned 127)

journalctl -b |grep networking
Code: 
Jun 07 19:10:04 pve systemd[1]: Starting networking.service - Network initialization...
Jun 07 19:10:04 pve networking[1110]: networking: Configuring network interfaces
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 325, in run_iface_list
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_graph(ifupdownobj, ifacename, ops, parent,
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 315, in run_iface_graph
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_list_ops(ifupdownobj, ifaceobjs, ops)
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 188, in run_iface_list_ops
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_op(ifupdownobj, ifaceobj, op,
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 150, in run_iface_op
Jun 07 19:10:05 pve networking[1162]:     ifupdownobj.log_error('%s: %s %s' % (ifacename, op, str(e)))
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/ifupdownmain.py", line 226, in log_error
Jun 07 19:10:05 pve networking[1162]:     raise Exception(str)
Jun 07 19:10:05 pve networking[1162]: error: lo : lo: up cmd '/etc/network/if-up.d/vzifup-post' failed: returned 127
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 325, in run_iface_list
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_graph(ifupdownobj, ifacename, ops, parent,
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 315, in run_iface_graph
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_list_ops(ifupdownobj, ifaceobjs, ops)
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 188, in run_iface_list_ops
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_op(ifupdownobj, ifaceobj, op,
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 150, in run_iface_op
Jun 07 19:10:05 pve networking[1162]:     ifupdownobj.log_error('%s: %s %s' % (ifacename, op, str(e)))
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/ifupdownmain.py", line 226, in log_error
Jun 07 19:10:05 pve networking[1162]:     raise Exception(str)
Jun 07 19:10:05 pve networking[1162]: error: enp10s0 : enp10s0: up cmd '/etc/network/if-up.d/vzifup-post' failed: returned 127
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 325, in run_iface_list
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_graph(ifupdownobj, ifacename, ops, parent,
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 302, in run_iface_graph
Jun 07 19:10:05 pve networking[1162]:     cls.run_iface_list(ifupdownobj, dlist, ops,
Jun 07 19:10:05 pve networking[1162]:   File "/usr/share/ifupdown2/ifupdown/scheduler.py", line 337, in run_iface_list
Jun 07 19:10:05 pve networking[1162]:     raise Exception('%s : (%s)' %(ifacename, str(e)))
Jun 07 19:10:05 pve networking[1162]: error: vmbr0 : enp0s31f6 : (enp0s31f6: up cmd '/etc/network/if-up.d/vzifup-post' failed: returned 127)
Jun 07 19:10:05 pve networking[1162]: warning: vmbr0: interface not recognized - please check interface configuration
Jun 07 19:10:05 pve systemd[1]: Finished networking.service - Network initialization.
 
Last edited:
Please share
Bash: 
ifreload -av
cat /etc/network/if-up.d/vzifup-post
pveversion -v
I don't have such a /etc/network/if-up.d/vzifup-post file.
 
The vzifup-post file was the issue. I removed it and it's working now. No idea why it was there. Must be a leftover from an older proxmox version.

Thank you!

cat /etc/network/if-up.d/vzifup-post
Code: 
#!/bin/sh

[ "$ADDRFAM" = "inet" -o "$ADDRFAM" = "inet6" ] || exit 0

exec /usr/sbin/vzifup-post "$IFACE"
 
  • Like
Reactions: Impact
Bionicao said:
iface enp10s0
inet static address 192.168.1.103/24
gateway 192.168.1.1 auto
vmbr0 iface vmbr0
inet static address 192.168.1.101/24
Click to expand...
You have two hardware NICs in the same network.

Outgoing packets will always use the one with the gateway, afaik.

Incoming packets may use both. Earlier or later you will might encounter "strange" malfunctions you can not explain and which are difficult to debug. (Incoming on vmbr0 but the reply outgoing on enp10s0 - which may lead to "acceptance problems" on the receiving side.)

Personally I work hard to avoid this potentially problematic setup. One host == one address in each IP-network.
 
Last edited:
You must log in or register to reply here.
Top Bottom