Network is unreachable

marcelw60

New Member
Jun 19, 2023
13
0
1
Hi,
I had a working proxmox server running and after a reboot the machine is unreachable on the network.
From the server (logged on locally) I can not ping the router or any other machine on the network.
The last line Dmesg showed : Nic Link is up 1000Mbps Full duplex

I am not sure how to proceed from this point

The interface file :
auto lo
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address 10.0.0.30/24
gateway 10.0.0.1
bridge-ports eno1
bridge-stop off
bridge-fd 0

any help or hint is helpful
 
This is the ip a outcome

root@pve-hp2: etc/network# ip a
1: 10: «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 Ift forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid Ift forever preferred_lft forever
2: enol: <BROADCAST, MULTICAST,UP ,LOWER UP > mtu 1500 gdisc pfifo_fast state UP group default qlen 1000
link/ether 98:e7:4f:bc:f8:cc brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
ineto fdaa:5228:7772:0:9ae7:f4ff: febc: f8cc/64 scope global dynamic mngtmpaddr
valid Ift forever preferred_lft forever
inet6 fe80::9ae7:f4ff:febe:f8cc/64 scope link
valid_lft forever preferred_Ift forever

There might still be some 'small'' typo's
 
Last edited:
Below the outcome

root@pve-hp2:/etc/networking cat /etc/hosts
127.0.0.1 localhost. localdomain localhost
10.0.0.30 pve-hp2.local pve-hp2

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@pve-hp2:/etc/network#
 
vmbr0 is not visible in the ip a output.

Make sure you have it in the right format:
Code:
auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
    address 10.0.0.30/24
    gateway 10.0.0.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

Linux is sensitive to spaces and tab stops.

Then restart networking:
Code:
systemctl restart networking

Hopefully you now see vmbr0 in the ip a output.

If not try to bring it up manually with:
Code:
ip link set vmbr0 up

If you encounter any errors, please post them here :)
 
I checked the interfaces file; I didn't see any issues there.
restarted the network
ip a didn't show vmbr0
Unfortunately bringing vmbr0 up manually gave the error [Cannot find device "vmbr0"]
 
dmesg | grep vmbr0. --> Didnt show any message/output

Jornalctl -u networking give following output



- Boot 199591914a845a180b63645bBB9734 -
Dec 09 15:36:57 pve-hp2 systemd[1]: Starting networking-service - Network initialization...
Dec 09 15:36:57 pve-hp2 systemd[1]: Finished networking service - Network initialization.
Dec 10 10:04:26 pve-hp2 systemd[1]: Stopping networking service - Network initialization...
Dec 10 10:04:26 pve-hp2 systemd[1]: networking service: Deactivated successfully.
Dec 10 10:04:26 pve-hp2 systemd[1]: Stopped networking.service - Network initialization.
Dec 10 10:04:26 pve-hp2 systemd[1]: Starting networking service - Network initialization...
Dec 10 10:04:26 pve-hp2 systemd[1]: Finished networking service - Network initialization.
Dec 10 10:07:50 pve-hp2 systemd[1]: Stopping networking service - Network initialization...
Dec 10 10:07:50 pve-hp2 systemd[1]: networking service: Deactivated successfully.
Dec 10 10:07:50 pve-hp2 systemd[1]: Stopped networking service - Network initialization.
Dec 10 10:07:50 pve-hp2 systemd[1]: Starting networking service - Network initialization...
Dec 10 10:07:50 pve-hp2 systemd[1]: Finished networking service - Network initialization.
 
Did you install Proxmox on top of an existing Debian or via ISO?

It looks like the bridge-utils aren't loaded or Installed.

Try to set eno1 as your Interface to at least get Network back:
Code:
auto eno1
iface eno1 inet static
        address 10.0.0.30/24
        gateway 10.0.0.1

And if you get network access try to update and install bridge-utils
Code:
apt update
apt install bridge-utils
 
I used the proxmox installer to install proxmox on a bare HP prodesk

I changed the interface file as stated above , but that didn't bring the network back up unfortunately

So, apt update did not work
 
Last edited:
I changed the interface file as stated above , but that didn't bring the network back up unfortunately
You removed the vmbr0 and restartet the Network with:
Code:
systemctl restart networking

Have you checked the wiring of the network cable? Maybe the cable is damaged or not correctly seated.
- Edit: Never mind, it was UP before, so it shouldn't be the issue...

I'm unfortunately at the end of my Knowledge, maybe it's something way different?
I'll ask my coworkers if they have a better approach. :)
 
Last edited:
Don‘t know if this is just a font issue, but in your interfaces file, the interface‘s name is „eno1“, while the dump of „ip a show“ contains „enol“ (lower L instead of digit 1).

However, among all of the Linux Interface name variants i am aware of, „enol“ is the most unlikely.
 
Don‘t know if this is just a font issue, but in your interfaces file, the interface‘s name is „eno1“, while the dump of „ip a show“ contains „enol“ (lower L instead of digit 1).

However, among all of the Linux Interface name variants i am aware of, „enol“ is the most unlikely.
thanks for checking- this was a typo at my side
 
Give it another try. Make sure that your file /etc/network/interfaces looks exactly as proposed by @smueller in comment #6, including indendation (it's a single tab, but spaces should work, too).

Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
    address 10.0.0.30/24
    gateway 10.0.0.1       
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0


Make sure (once again), that the network interface's name is "eno1" by running ip link show type "" . That sould return only two lines, including "eno1"

Next, run systemctl restart networking, that should bring up the vmbr0 device and you should be able to reach other devices on the same network from the PVE host.

Btw: What PVE version are you using? Did you update recently? Did you change the host's hardware? Did you apply changes to your overall network configuration?
 
Next, run systemctl restart networking, that should bring up the vmbr0 device and you should be able to reach other devices on the same network from the PVE host.
unfortunately rcvd same message "network is un reachable". I tried to ping the router [openwrt] @ 10.0.0.1. same result
 
Give it another try. Make sure that your file /etc/network/interfaces looks exactly as proposed by @smueller in comment #6, including indendation (it's a single tab, but spaces should work, too).
Did that again , There are Tabs in the interfaces file; but no success

Output ip a - no vmbr0

1: lo: «LOOPBACK, UP, LOWER UP> mtu 65536 gdisc noqueue state UNKNOWN group detault gen 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 Ift forever preferred ift forever inet6 ::1/128 scope host noprefixroute
valid ift forever preferred Ift forever
2: eno1: «BROADCAST, MULTICAST, UP ,LOWER UP> mtu 1500 qdisc pfifo_fast state UP group default glen 1000
link/ether 98:7:F4:bc:f8:cc brd ff:ff:ff:ff:ff:ff
altname enpos31f6
inet fdaa:528:7772:0:9ae?:f4ff:febc:f8cc/64 scope global dynamic mngtmpaddre
valid ift forever preferred_lft forever inetb feBU::9ae7:141f:febc:fBcc/64 scope link
valid ift forever preferred_lft forever


I am not 100% sure but I think HP2 server is using proxmox 8.2
 
Last edited:

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!