Network fails after upgrade

donhwyo

Member
Jan 14, 2023
103
14
23
Last week I ran an update from the web ui. After a few days I rebooted. When it came up I had no network. Seems there was a openvswitch update. I no longer need ovs so I apt removed it. No change. Maybe that was a bad choice? Anyway I ran systemctl status networking.
Code:
● networking.service - Network initialization
     Loaded: loaded (/lib/systemd/system/networking.service; disabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:interfaces(5)
             man:ifup(8)
             man:ifdown(8)
Don't know if that is normal or not. "systemctl start networking" starts the network according to status, but it does not work.
Code:
ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 90760  bytes 5499344 (5.2 MiB)

        RX errors 0  dropped 0  overruns 0  frame
0
        TX packets 90760  bytes 5499344 (5.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Code:
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: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f0:4d:a2:3e:71:67 brd ff:ff:ff:ff:ff:ff
    altname enp1s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f0:4d:a2:3e:71:69 brd ff:ff:ff:ff:ff:ff
    altname enp1s0f1
4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f0:4d:a2:3e:71:6b brd ff:ff:ff:ff:ff:ff
    altname enp2s0f0
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f0:4d:a2:3e:71:6d brd ff:ff:ff:ff:ff:ff
    altname enp2s0f1
Code:
cat interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual
#vmbr0

# auto enp1s0f0
# iface enp1s0fo inet manual

auto eno4
iface eno4 inet manual
#Internet    pre-up ( ifconfig eno4 mtu 9000 )Internet

auto vmbr0
iface vmbr0 inet static
    address 10.0.83.15/24
    gateway 10.0.83.1
    address f0:4d:a2:3e:71:67
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
#Default ovs_options mtu 9000defaultset mtu 9000?    post-up /sbin/ethtool -K $IFACE tx off    up /sbin/route add -net 10.0.51.0 netmask 255.255.255.0 gw 10.0.51.1    down /sbin/route del -net 10.0.51.0 netmask 255.255.255.0

auto vmbr1
iface vmbr1 inet static
    address 10.0.33.2
    gateway 10.0.33.1
    bridge-ports eno4
    bridge-stp off
    bridge-fd 0
    address f0:4d:a2:3e:71:6d
#Internet

auto vmbr2
iface vmbr2 inet manual
#pf lan
Code:
ifreload -a -d
error: Another instance of this program is already running.
info: exit status 89

Thanks
 
Last edited:
A little more info. This shows the new 6.2 kernel but it is the same with 5.15 kernels.
Code:
pveversion -v
proxmox-ve: 7.4-1 (running kernel: 6.2.11-1-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-6.2: 7.4-2
pve-kernel-5.15: 7.4-2
pve-kernel-6.2.11-1-pve: 6.2.11-1
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-1
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1
Code:
lspci |grep network
01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5709 Gigabit Ethernet (rev 20)

Any other info I should provide?
Thanks
 
Well I got network running on one interface. I updated apt and reinstalled ovs. Then set the network up in the web ui with ovs. Seems to be working.

The last thing I need to do is have the network start on boot. It does work if I "systemctl start networking". Have not found out what should be starting it at boot. Or what logs I need to look at.
 
'Thanks for the reply. That's what I get for following things on the internet. I did get networking working by setting up one interface and using the web ui.
Code:
cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual
    ovs_type OVSPort
    ovs_bridge vmbr0
    ovs_mtu 9000
#vmbr0

auto eno2
iface eno2 inet manual
    ovs_type OVSPort
    ovs_bridge vmbr0
#wireless

auto eno3
iface eno3 inet manual
    ovs_type OVSPort
    ovs_bridge vmbr0
#wireless

auto eno4
iface eno4 inet manual
    ovs_type OVSPort
    ovs_bridge vmbr1
#internet

auto vmbr0
iface vmbr0 inet static
    address 10.0.83.15/24
    gateway 10.0.83.1
    ovs_type OVSBridge
    ovs_ports eno1 eno2 eno3
    ovs_mtu 9000
#vmbr0

auto vmbr1
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_ports eno4
#internet

auto vmbr2
iface vmbr2 inet manual
    ovs_type OVSBridge
#pf

It seems to be working if I start networking with "systemctl start networking". I am now trying to figure out why it is not starting on boot. Seems Proxmox may not be using systemctl to start it? Not sure what to look for in which logs.

Code:
# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 6.2.11-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-6.2: 7.4-3
pve-kernel-5.15: 7.4-3
pve-kernel-6.2.11-2-pve: 6.2.11-2
pve-kernel-6.2.11-1-pve: 6.2.11-1
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.6
libpve-storage-perl: 7.4-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
openvswitch-switch: 2.15.0+ds1-2+deb11u4
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-1
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1
 
● networking.service - Network initialization Loaded: loaded (/lib/systemd/system/networking.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:interfaces(5) man:ifup(8) man:ifdown(8)
Your networking.service is disabled. Enable it via systemctl enable networking.service, then try if network comes up after reboot.
 
  • Like
Reactions: spirit
Thanks that worked! Not sure what turned that off?

The web interface for network setup is really nice. Would be really helpful if there was a cli version of that.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!