Network connected but can't ping gateway / external ips or domains

Springs

New Member
Jun 30, 2023
4
0
1
Hi all,

I have a 3 node cluster setup at home with 2 nodes installed with 2.5Gb network cards. Since these have been installed proxmox itself can't ping the gateway or ping / resolve external domains / ip addresses

DNS resolution works fine. I can resolve external domains like google.com / proxmox.com fine on the box
I can ping all internal addresses apart from the gateway

If i switch the bridge back to the onboard 1Gb connection it works fine.

The card is using a Realtek RTL8125B chip and i've followed what instructions i can to install the relevant drivers on one of the nodes to test

Is anyone else using this type of network chip?

I've attached some outputs from the machine in question
 

Attachments

  • proxmox_issue.PNG
    proxmox_issue.PNG
    54 KB · Views: 17
100% packet loss when pinging google.com and proxmox.com is not what I would define as "DNS resolution works fine".......

From the PVE host what is the result of:
# dig google.com
# dig proxmox.com
 
Last edited:
Hi all,

I have a 3 node cluster setup at home with 2 nodes installed with 2.5Gb network cards. Since these have been installed proxmox itself can't ping the gateway or ping / resolve external domains / ip addresses

DNS resolution works fine. I can resolve external domains like google.com / proxmox.com fine on the box
I can ping all internal addresses apart from the gateway

If i switch the bridge back to the onboard 1Gb connection it works fine.

The card is using a Realtek RTL8125B chip and i've followed what instructions i can to install the relevant drivers on one of the nodes to test

Is anyone else using this type of network chip?

I've attached some outputs from the machine in question
Please share your output of :

# pveversion -v
# cat /etc/network/interfaces
 
I've attached all as requested
 

Attachments

  • dig_google.png
    dig_google.png
    88.1 KB · Views: 26
  • dig_proxmox.png
    dig_proxmox.png
    88.7 KB · Views: 27
  • interfaces.png
    interfaces.png
    104.4 KB · Views: 29
  • pve_version.txt
    1.4 KB · Views: 7
I would remove "dns-nameservers" in your /etc/network/interfaces file.
And add a valid DNS server in "/etc/resolv.conf".
I notice two DNS servers in your screenshots, 192.168.1.99 and 192.168.1.101. Is that correct?
 
I would remove "dns-nameservers" in your /etc/network/interfaces file.
And add a valid DNS server in "/etc/resolv.conf".
I notice two DNS servers in your screenshots, 192.168.1.99 and 192.168.1.101. Is that correct?
the dns-nameservers was added in recently while trying to troubleshoot this issue after a lot of going through the forums etc. to confirm the issue was present before this were added.

and yes both 99 and 101 are both DNS servers and are also in the resolv.conf
 
the dns-nameservers was added in recently while trying to troubleshoot this issue after a lot of going through the forums etc. to confirm the issue was present before this were added.

and yes both 99 and 101 are both DNS servers and are also in the resolv.conf
Again, remove the line dns-nameservers in /etc/network/interfaces.

Your /etc/resolv.conf can look something like this (max 3 DNS servers):

search whateverdomainyouhave
nameserver 192.168.1.99
nameserver 192.168.1.101
nameserver 9.9.9.9
 
i've managed to figure out and "fix" the issue. Not sure why or how it's doing it.

But i've managed to work out that the IP address is causing the issue.

I build another node using a spare machine with the same network card and that worked fine with a random ip address as well as a different network port on a different switch. Moved one of the nodes over to the same switch and still the same.

in the end i ended up reinstalling proxmox on one of the effected nodes and that still didn't fix anything. then i moved the ip from what it was to a different one and everything worked as expected. moved it back to what it should be and it stopped again.

Not sure why that particular IP is causing it. I've set it to a new IP address and re-joined it to the cluser. But now need to move the rest of my cluster over to the new IP range..
 
i've managed to figure out and "fix" the issue. Not sure why or how it's doing it.

But i've managed to work out that the IP address is causing the issue.

I build another node using a spare machine with the same network card and that worked fine with a random ip address as well as a different network port on a different switch. Moved one of the nodes over to the same switch and still the same.

in the end i ended up reinstalling proxmox on one of the effected nodes and that still didn't fix anything. then i moved the ip from what it was to a different one and everything worked as expected. moved it back to what it should be and it stopped again.

Not sure why that particular IP is causing it. I've set it to a new IP address and re-joined it to the cluser. But now need to move the rest of my cluster over to the new IP range..
Same issue as you. Changing the IP resolved the issue. I didn't try to go back to the old one. Thanks.
 

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!