Networking requires restart after boot

[mtoconnor3]

Hello all,

I've lurked for a while, and benefited from the wisdom in these forums many times, but now I have hit a wall that I can't get past.

Problem Description:
After a fresh install of PVE6.2 my node's networking doesn't start unless I manually log into it and run /etc/init.d/networking restart a few times before the NIC comes up. Once I get networking online, I can ping 8.8.8.8, and access the web GUI at the node's ip address no problem. I also have no problem with apt get upgrade, but only after networking is restarted.

Given that I don't restart this machine often, this didn't bother me too much, but I also encounter networking issues when building VMs. A brand new Win10 VM installed on this node cannot get to the web with either the E1000 or VirtIO devices selected, even when I can ping 8.8.8.8 from the host. I suspect I've screwed something up in my configuration, but it looks similar to what I see from other users.

Hardware:
Ryzen 5 3600
32GB DDR4 3200
Asus Strix b550F WiFi (BIOS version 0243 x64)
1TB Samsung 960 EVO NVME System disk
1x MSI 2070 Super (using this adapter for ML)
1x MSI 1050TI (using this adapter for display)

/etc/network/interfaces:

auto lo
iface lo inet loopback

iface enp57s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.8.162
        netmask 255.255.255.0
        gateway 192.168.8.1
        bridge_ports enp57s0
        bridge_stp off
        bridge_fd 0

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: enp57s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether d4:5d:64:d5:7e:1f brd ff:ff:ff:ff:ff:ff
3: wlp56s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether b8:9a:2a:74:62:7e brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether d4:5d:64:d5:7e:1f brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.162/24 brd 192.168.8.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::d65d:64ff:fed5:7e1f/64 scope link 
       valid_lft forever preferred_lft forever

I have found a lot of threads about problems similar to mine, but none of the solutions I've found so far have worked for my situation. Here are a few of the places I have looked:

https://forum.proxmox.com/threads/restarting-network-everytime-after-reboot.27862/
https://forum.proxmox.com/threads/no-network-after-reboot.41865/
https://forum.proxmox.com/threads/no-network-connection-after-install.24663/

This all arose when I decided to upgrade my MB to AMD's new 550 chipset, and I'm beginning to think there's something funky going on with the built-in NIC. Any advice would be greatly appreciated as I've run out of ideas.

Cheers,
Mike

 

[wolfgang]

Hi,

try to enable the vlan awareness on the bridge.
What kernel module does this nic use?

The way(SysVinit) you restart the network is deprecated and will be removed next Debian version use systemd instead.

systemctl restart networking.service

 

[spirit]

I think to debug, the first thing to do, is to check if network is working on the same lan or not. (try to ping between 2 hosts in 192.168.8.0/24).

if it working fine, then , try to ping your gateway. if it's not working, it could be a problem with your gateway (maybe arp problem or something like that)