[SOLVED] Host can't ping guest VMs, or guest VMs can't ping Host, both have Internet access

robotdog

New Member
Dec 23, 2021
5
0
1
53
Hi all,

I have a 7.1 host with working VMs and CTs. Also have pfSense in VM.
The hardware has multiple NICs 1 onboard realtek, and a 4 port Intel.

My proxmox host can ping gateway/internet/8.8.8.8 with no problem.
I can also ping all of the other physical interfaces AND I can ping the WAN interface of the pfSense VM.

I had this problem a couple of days a go [link to thread] which fixed the overall problem.

It was working great, but I rebooted the box to make sure everything is working properly.

I am not sure why the host can't ping anything on the 192.168.50.xx network (aside from the 192.168.50.3 interface)

Thanks for helping this noob.

note: pfsense is setup (and working) WAN:192.168.1.71, LAN 192.168.50.4) pve host cannot ping the 192.168.50.4 but can ping the WAN IP.



This is the host routing (default is 192.168.1.254) VMs and host can reach
root@proxmox-01:~# root@proxmox-01:~# ip -c r default via 192.168.1.254 dev vmbr1 proto kernel onlink 192.168.1.0/24 dev vmbr1 proto kernel scope link src 192.168.1.72 192.168.50.0/24 dev vmbr0 proto kernel scope link src 192.168.50.3 linkdown 192.168.50.0/24 dev vmbr2 proto kernel scope link src 192.168.50.5 192.168.60.0/24 dev vmbr4 proto kernel scope link src 192.168.60.1 linkdown


Interfaces: Only two interfaces are connected - enp15s0 and enp16s0.
2: enp15s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000 link/ether 24:5e:be:7a:bb:38 brd ff:ff:ff:ff:ff:ff 3: enp16s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr2 state UP group default qlen 1000 link/ether 24:5e:be:7a:bb:37 brd ff:ff:ff:ff:ff:ff 4: enp18s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr3 state DOWN group default qlen 1000 link/ether 24:5e:be:7a:bb:36 brd ff:ff:ff:ff:ff:ff 5: enp19s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr4 state DOWN group default qlen 1000 link/ether 24:5e:be:7a:bb:35 brd ff:ff:ff:ff:ff:ff 6: enp12s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vmbr0 state DOWN group default qlen 1000 link/ether 1c:1b:0d:97:a9:b6 brd ff:ff:ff:ff:ff:ff 7: vmbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 1c:1b:0d:97:a9:b6 brd ff:ff:ff:ff:ff:ff inet 192.168.50.3/24 scope global vmbr0 valid_lft forever preferred_lft forever 8: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 24:5e:be:7a:bb:38 brd ff:ff:ff:ff:ff:ff inet 192.168.1.72/24 scope global vmbr1 valid_lft forever preferred_lft forever inet6 fe80::265e:beff:fe7a:bb38/64 scope link valid_lft forever preferred_lft forever 9: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 24:5e:be:7a:bb:37 brd ff:ff:ff:ff:ff:ff inet 192.168.50.5/24 scope global vmbr2 valid_lft forever preferred_lft forever inet6 fe80::265e:beff:fe7a:bb37/64 scope link valid_lft forever preferred_lft forever 10: vmbr4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 24:5e:be:7a:bb:35 brd ff:ff:ff:ff:ff:ff inet 192.168.60.1/24 scope global vmbr4 valid_lft forever preferred_lft forever 11: vmbr3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 24:5e:be:7a:bb:36 brd ff:ff:ff:ff:ff:ff


/etc/network/interfaces: on the PVE host
auto lo iface lo inet loopback iface enp12s0 inet manual iface enp15s0 inet manual iface enp16s0 inet manual iface enp18s0 inet manual iface enp19s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.50.3/24 bridge-ports enp12s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #Management Interface auto vmbr1 iface vmbr1 inet static address 192.168.1.72/24 gateway 192.168.1.254 bridge-ports enp15s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #WAN - ATT fiber auto vmbr2 iface vmbr2 inet static address 192.168.50.5/24 bridge-ports enp16s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #LAN - fastlane bridge-vlan-aware yes bridge-vids 2-4094 auto vmbr3 iface vmbr3 inet dhcp bridge-ports enp18s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 auto vmbr4 iface vmbr4 inet static address 192.168.60.1/24 bridge-ports enp19s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094
 

Dunuin

Famous Member
Jun 30, 2020
6,734
1,567
149
Germany
This shouldn't be there...
Code:
        bridge-vlan-aware yes
        bridge-vids 2-4094
...between vmbr2 and vmbr3.

And a host shouldn't have two IPs on the same subnet. This may cause routing problems. So either use a 192.168.50.X/24 IP on vmbr0 or vmbr2 but not on both.
 
Last edited:

vesalius

Active Member
Aug 19, 2020
160
43
28
Yeah from what you above enp12s0/vmbr0 is neither physically nor virtually connected to anything. So pick an IP you want to use in the 192.168.50.0/24 subnet for Proxmox management and leave that on vmbr2, either 192.168.50.3/24 or 192.168.50.5/24 would be fine.

As it stands now vmbr0 is currently superfluous and doing nothing for you. You can just remove the IP from vmbr0 or delete that bridge altogether.
 

robotdog

New Member
Dec 23, 2021
5
0
1
53
Thanks again. Cleaned up the interfaces file and now everything acts like it should. Guess I had some 'cruft' left over from playing/testing. Maybe the lesson should be ... keep my nose out of things where it might get cut off. ;-)

Really do appreciate the help, on my screwups.
 

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 your own in 60 seconds.

Buy now!