Proxmox cannot access the internet, even can't ping 8.8.8.8

sinan

Member
Jul 31, 2021
8
3
8
44
Hello,

I have installed proxmox 6.3-2 and works great with 5 VMs (one of Pfsense). All of VMs connects the internet and proxmox web gui without any problem. But proxmox can't, even cannot ping 8.8.8.8 from proxmox shell.

Got 4 ethernet on my server, using 2 of them and configured like as attached image.

PfSense works on 16.0.0.1 as DHCP Server and Gateway
Proxmox works on 16.0.0.3

But i can't even ping from 16.0.0.1 (pfsense) to proxmox (16.0.0.3) and can't ping from the proxmox to pfsense.
Btw; i can ping all of vms from proxmox and pfsense shell.

Here is my /etc/network/interfaces;

auto lo
iface lo inet loopback

iface enp2s0f0 inet manual

iface enp2s0f1 inet manual

iface enp3s0f0 inet manual

iface enp3s0f1 inet manual

auto vmbr0
iface vmbr0 inet static
address 16.0.0.3/24
gateway 16.0.0.1
bridge-ports enp2s0f0
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet manual
bridge-ports enp2s0f1
bridge-stp off
bridge-fd 0

auto vmbr2
iface vmbr2 inet manual
bridge-ports enp3s0f0
bridge-stp off
bridge-fd 0

auto vmbr3
iface vmbr3 inet manual
bridge-ports enp3s0f1
bridge-stp off
bridge-fd 0

Need a genius or any kind of ideas for connect the proxmox to internet. Thanks in advance
Best regards
 

Attachments

  • screen1.JPG
    screen1.JPG
    42.9 KB · Views: 47
  • screen2.JPG
    screen2.JPG
    24 KB · Views: 45
Thanks for your reply;

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
28 * * *
29 * * *
30 * * *

traceroute to 16.0.0.1 (16.0.0.1), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
28 * * *
29 * * *
30 * * *
 
Okay, although that might not be directly related to your problem, please remember that you shouldn't use globally routable addresses for a private network. RFC1918 defines three IP ranges for internal use and 16.0.0.0/24 is not included.

Did you enable the firewall on vmbr0 or vmbr1?
 
  • Like
Reactions: sinan
@ph0x
Do you know what‘s it with this 16.0.0.0 range? Tried (just checking) to ping 16.0.0.1 but it gives me a network unreachable because it is dropped by my ISPs gateway/router.

BTW: Firewall would be my next guess too ;)
 
  • Like
Reactions: sinan
Okay, although that might not be directly related to your problem, please remember that you shouldn't use globally routable addresses for a private network. RFC1918 defines three IP ranges for internal use and 16.0.0.0/24 is not included.

Did you enable the firewall on vmbr0 or vmbr1?
Thanks for a different perspective, RFC1918 is quite reasonable. I will try with 192.168../24 and share the results.
Tried to enable/disable firewall on vmbr0 and vmbr1 and doesn't work
 
But keep in mind that for a firewall VM both host's and VM's firewalls in conjunction are relevant.
Rules on vmbr0 and vmbr1 regulate traffic to and from the VM's interfaces but the host's/datacenter's firewall might also interfere with communication.
 
  • Like
Reactions: sinan
I’m not using Proxmox very long so I could be wrong but there are three places where you can put firewall rules:

- Hostfirewall
- VMs firewall
- Vmbr rules

Which one did you check?

For completeness sake, could you share the output of the ping command(s)?
 
  • Like
Reactions: sinan
Solved! Problem was HP! HP owned my old gateway ip 16.0.0.1 :)
Changed LAN to 192.168../24 group and then worked.
Ps: Don't go outside the range of the RFC1918 :P
Thanks for all replies and effort to all...
 

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!