Proxmox can't ping Gateway

[newguy]

I'm going to try this as I assume I post something incorrectly the first time.

I recently purchased a Dell R720 rack server. I loaded proxmox and started moving some of my VM's to the new machine. I tried to check for updates for proxmox and could not reach the update server. Through some newbie trouble shooting I found that I can’t ping my gateway or the internet from the proxmox shell, but I can from the VM. After searching and trying to do what trouble shooting I can, I got frustrated and loaded xcp-ng. I could not ping the gateway or the internet (specifically 1.1.1.1) from the shell. When I look in my Omada network controller, I see the VM registered, but not the host machine. I've tried to set the server up with DHCP then change the address to static and no luck. It will be in there long enough to assign a static IP and in a short period of time, it's gone. My second NIC is assigned a DHCP address and it doesn't show up either. I've reached the end of my trouble shooting skills and I don't have much hair left to pull out.

 

[Moayad]

Hello,

Can you please post the network configuration (cat /etc/network/interfaces) and the output of (ip a)?

 

[newguy]

root@pve1:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eno1 inet manual

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

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual
root@pve1:~# 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,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 44:a8:42:39:f3:3e 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 44:a8:42:39:f3:3f 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 44:a8:42:39:f3:40 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 44:a8:42:39:f3:41 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 44:a8:42:39:f3:3e brd ff:ff:ff:ff:ff:ff
inet 192.168.86.5/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::46a8:42ff:fe39:f33e/64 scope link
valid_lft forever preferred_lft forever

 

[Moayad]

Thank you for the output!

What does the output of `ifreload -a` say? Does the gateway IP on the VMs is the same as on the PVE node?

 

[newguy]

Is ifreload -a the full command? I had nothing return.

I have only one vmbr0 Linux Bridge and I am not sure how to check to see if the same gateway is used.

 

[Moayad]

Is ifreload -a the full command? I had nothing return.

If not returns anything, that means everything is ok.

I have only one vmbr0 Linux Bridge and I am not sure how to check to see if the same gateway is used.

Checking by issuing the ip r command in the PVE shell and comparing with one VM if the VM have the same gateway IP.

 

[newguy]

I have another proxmox machine running on a PC and have checked the network settings against it. This is the first actual server I've worked with and I'm sure their is some differences that I don't know about or understand.

 

[newguy]

root@pve1:~# ip r
default via 192.168.86.1 dev vmbr0 proto kernel onlink
192.168.86.0/24 dev vmbr0 proto kernel scope link src 192.168.86.5
root@pve1:~#

josh@ubuntu:~$ ip r
default via 192.168.86.1 dev ens18 proto dhcp src 192.168.86.60 metric 100
192.168.86.0/24 dev ens18 proto kernel scope link src 192.168.86.60
192.168.86.1 dev ens18 proto dhcp scope link src 192.168.86.60 metric 100

 

[newguy]

Also when I look in my router's client log, I see the VM registered and idrac, but not the proxmox host.

 

[Moayad]

Also when I look in my router's client log, I see the VM registered and idrac, but not the proxmox host.

Can you test plugging the Ethernet cable into another port?

 

[newguy]

I tried plugging into a different port on the switch and strait to the router. I cant ping the router from the proxmox host. I have not tried changing the bridge to a different NIC.

 

[newguy]

I changed the bridge port on vmbr0 from eno1 to eno2 and I get the same result.

root@pve1:~# ping 192.168.86.1
PING 192.168.86.1 (192.168.86.1) 56(84) bytes of data.
^C
--- 192.168.86.1 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5104ms

 

[newguy]

I just tried booting a live version of Mint. I can ping the gateway and browse the internet from that.

 

[newguy]

root@pve1:~# traceroute google.com 443

traceroute to google.com (64.233.185.139), 30 hops max, 443 byte packets

1 192.168.86.1 (192.168.86.1) 0.791 ms 0.738 ms 0.704 ms

2 * * *

3 * * *

4 * * *

5 * * *

6 * * *

7 * * *

8 * * *

9 * * *

Same thing all the way to 30

Does that first hop mean that it is making it to the router or it knows that is where it should try to go?

 

[thommo17]

I don't know what to say but I was having the same issues as you on my R730 after I realised I haven't updated in a while.
Could ping everything on my network fine except for my gateway and then out to the internet.

Tried a few things from other forums and then found this.

I'm not sure why it started working but I followed this thread along to check my reults against yours with ifreload -a then ip r and then finally a traceroute and the traceroute worked which I wasn't expecting.

So I don't know what happened but I'm guessing the ifreload -a fixed my issue so thanks!

I hope it doesn't come back again though

 

[nidomiro]

I had the same problem, that I reached the node and the node reached everything inside my network but the Gateway.
My solution was to give the node a new IP (was a fresh install) as the IP was already taken by a VPN service of my FritzBox.