bridge reporting as up and ip in arp table but cannot ping gateway - Resolved

zevrant

New Member
Jul 17, 2023
4
0
1
Having issue with one of my machines, the ethernet is connected, bridge is reporting up, and i can even see the ip address assigned to the bridge in the Arp table on the router, however i cannot ping the gateway from this machine.

Network Config:
Code:
auto lo
iface lo inet loopback

iface eno3 inet manual

iface eno1 inet manual

iface eno2 inet manual

iface eno4 inet manual

auto vmbr0
iface vmbr0 inet static
        address 172.16.1.3/24
        gateway 172.16.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
results of ip addr:

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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 0C:C4:7A:59:E1:37 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 0C:C4:7A:59:E1:38 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 0C:C4:7A:59:E1:3a 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 0C:C4:7A:59:E1:35 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f1
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0C:C4:7A:59:E1:37 brd ff:ff:ff:ff:ff:ff
    inet 172.16.1.16/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::868f:69ff:fee9:b2d6/64 scope link
       valid_lft forever preferred_lft forever

Routes
Code:
default via 172.16.1.1 dev vmbr0 proto kernel onlink
172.16.1.0/24 dev vmbr0 proto kernel scope link src 172.16.1.16

I attempted to ping from the gateway as well and cannot communicate with it.
Not sure if helpful but it can hit itself via the static ip address


Note that this was working, up until a few hours ago
 

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!