New to Prox and my guests cant reach physical network

flinte

Member
Jun 1, 2018
16
0
21
41
Hi I am brand new to Proxmox, switching from ESXi free for my homelab. So far I really like it but I cant seem to get my networking straight. Proxmox is running on a machine that came with 2x built in NICs and I popped in a 4x port Intel NIC I had laying around. I have it all installed, the hypervisor OS has full access to the internet and the physical network, I can apt-get update and ping everything but any guest OS I install cant reach DHCP or any machines on my physical network.

I got this configuration for the bond0 and bridge directly from the help documentation.

Code:
root@proxmox:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto enp2s0f0
iface enp2s0f0 inet manual

auto enp2s0f1
iface enp2s0f1 inet manual

iface enp2s0f2 inet manual

iface enp2s0f3 inet manual

iface eno1 inet manual

iface enp7s0 inet manual

auto bond0
iface bond0 inet manual
    slaves eno1 enp2s0f0 enp2s0f1 enp2s0f2 enp2s0f3 enp7s0
    bond_miimon 100
    bond_mode 802.3ad
    bond_xmit_hash_policy layer2+3

auto vmbr0
iface vmbr0 inet static
    address  192.168.1.15
    netmask  255.255.255.0
    gateway  192.168.1.1
    bridge_ports bond0
    bridge_stp off
    bridge_fd 0
#Production

root@proxmox:~#
 
Last edited:
So are you connecting the guest network to vmbr0? If DHCP is not working, what happens if you set a static IP with correct parameters for your network?

It might be something to do with having all of your network ports bonded, I'm not 100% sure it would work across different hardware. I'd look to getting it working on one of the four nic ports and then bond just those 4 if that's what you want to do. Might be good practice to dedicate a port to host management anyway.
 
Last edited:
When I give the guest a static IP I am still unable to communicate with any other devices. No pingy pingy!

I have altered my networking as you advised and still not luck. I added an additional bond interface with a 192.168.10.15 address, now I can ping this address but I am unable to ssh or do anything meaningful to it. Also it wouldnt allow me to list my router as the gateway (192.168.1.1) since vmbr0 already using it.

Code:
root@proxmox:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto enp2s0f0
iface enp2s0f0 inet manual

auto enp2s0f1
iface enp2s0f1 inet manual

auto enp2s0f2
iface enp2s0f2 inet manual

auto enp2s0f3
iface enp2s0f3 inet manual

auto eno1
iface eno1 inet manual

auto enp7s0
iface enp7s0 inet manual

auto bond0
iface bond0 inet manual
    slaves enp2s0f0 enp2s0f1 enp2s0f2 enp2s0f3
    bond_miimon 100
    bond_mode 802.3ad
    bond_xmit_hash_policy layer2+3

auto bond1
iface bond1 inet static
    address 192.168.10.15
    netmask    255.255.255.0
    slaves    eno1 enp7s0
    bond_miimon 100
    bond_mode 802.3ad
    bond_xmit_hash_policy layer2+3

auto vmbr0
iface vmbr0 inet static
    address  192.168.1.15
    netmask  255.255.255.0
    gateway  192.168.1.1
    bridge_ports bond0
    bridge_stp off
    bridge_fd 0
#Production
 
well you won't be able to reach the internet from 192.168.10.x as the subnet mask makes it a different network from 192.168.1.x which is were your gateway lives.
 
well you won't be able to reach the internet from 192.168.10.x as the subnet mask makes it a different network from 192.168.1.x which is were your gateway lives.


Shouldnt be.

192.168.10.15 subnetmask is 255.255.255.0. Still a class C and /24 network.
 
Subnet 192.168.10.0, mask bits 24, host address range 192.168.10.1 - 192.168.10.254, broadcast address 192.168.10.255

Subnet 192.168.1.0, mask bits 24, host address range 192.168.1.1 - 192.168.1.254, broadcast address 192.168.1.255

They are two entirely seperate networks
 
I have redone this a million times. I have done static addresses and DHCP on the guests. No matter what I am unable to reach the 192.168.x.x network from the guests. As you can see I have tried several different combinations for NICs and bridges. changing the guests to access vmbr0 or vmbr1 seems to make no difference.


iface lo inet loopback

auto enp2s0f0
iface enp2s0f0 inet manual

auto enp2s0f1
iface enp2s0f1 inet manual

auto enp2s0f2
iface enp2s0f2 inet manual

auto enp2s0f3
iface enp2s0f3 inet manual

auto eno1
iface eno1 inet manual

auto enp7s0
iface enp7s0 inet manual

auto bond0
iface bond0 inet manual
slaves enp2s0f0 enp2s0f1
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer3+4

auto bond1
iface bond1 inet static
address 192.168.1.6
netmask 255.255.255.0
slaves eno1 enp7s0
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3

auto vmbr0
iface vmbr0 inet static
address 192.168.1.15
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports bond0
bridge_stp off
bridge_fd 0
#Production

auto vmbr1
iface vmbr1 inet static
address 192.168.1.35
netmask 255.255.255.0
bridge_ports enp2s0f2 enp2s0f3
bridge_stp off
bridge_fd 0


From another host I can ping these IPs just fine of course.

ping 192.168.1.35
PING 192.168.1.35 (192.168.1.35) 56(84) bytes of data.
64 bytes from 192.168.1.35: icmp_seq=1 ttl=64 time=0.198 ms
64 bytes from 192.168.1.35: icmp_seq=2 ttl=64 time=0.332 ms
64 bytes from 192.168.1.35: icmp_seq=3 ttl=64 time=0.312 ms
^C
--- 192.168.1.35 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2046ms
rtt min/avg/max/mdev = 0.198/0.280/0.332/0.062 ms
amlucent@devlab:~$ ping 192.168.1.15
PING 192.168.1.15 (192.168.1.15) 56(84) bytes of data.
64 bytes from 192.168.1.15: icmp_seq=1 ttl=64 time=0.286 ms
64 bytes from 192.168.1.15: icmp_seq=2 ttl=64 time=0.318 ms
64 bytes from 192.168.1.15: icmp_seq=3 ttl=64 time=0.399 ms
^C
--- 192.168.1.15 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2026ms
rtt min/avg/max/mdev = 0.286/0.334/0.399/0.049 ms
amlucent@devlab:~$ ping 192.168.1.6
PING 192.168.1.6 (192.168.1.6) 56(84) bytes of data.
64 bytes from 192.168.1.6: icmp_seq=1 ttl=64 time=0.493 ms
64 bytes from 192.168.1.6: icmp_seq=2 ttl=64 time=0.264 ms
64 bytes from 192.168.1.6: icmp_seq=3 ttl=64 time=0.312 ms
^C
--- 192.168.1.6 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2040ms
rtt min/avg/max/mdev = 0.264/0.356/0.493/0.099 ms

The problem has to be with the guest configuration right?
 
Try adding this to your network definition

Code:
#subnets
up ip route add 192.168.10.0/24 dev vmbr0
 
Ok I have been fooling with this all night and I made some progress. My guest can now receive a DHCP address on boot with the following settings but still cant reach any devices on my physical network or the internet.

auto lo
iface lo inet loopback

auto enp2s0f0
iface enp2s0f0 inet manual

auto enp2s0f1
iface enp2s0f1 inet manual

auto enp2s0f2
iface enp2s0f2 inet manual

auto enp2s0f3
iface enp2s0f3 inet manual

auto eno1
iface eno1 inet manual

auto enp7s0
iface enp7s0 inet manual

auto bond0
iface bond0 inet manual
slaves enp2s0f0 enp2s0f1 enp2s0f2 enp2s0f3
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3

auto bond1
iface bond1 inet static
address 192.168.1.6
netmask 255.255.255.0
slaves eno1 enp7s0
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3

auto vmbr0
iface vmbr0 inet static
address 192.168.1.15
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports bond0
bridge_stp off
bridge_fd 0
#Production

#subnets
up ip route add 192.168.1.0/24 dev vmbr0


pdlBM3g.png
 
root@proxmox01:/etc/network# cat /proc/net/bonding/bond0

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2+3 (2)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 00:0a:f7:83:c4:a4
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 4
Actor Key: 9
Partner Key: 1001
Partner Mac Address: 20:e5:2a:63:fa:7f

Slave Interface: enp2s0f0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0a:f7:83:c4:a4
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:0a:f7:83:c4:a4
port key: 9
port priority: 255
port number: 1
port state: 61
details partner lacp pdu:
system priority: 1
system mac address: 20:e5:2a:63:fa:7f
oper key: 1001
port priority: 1
port number: 9
port state: 61

Slave Interface: enp2s0f1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0a:f7:83:c4:a5
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:0a:f7:83:c4:a4
port key: 9
port priority: 255
port number: 2
port state: 61
details partner lacp pdu:
system priority: 1
system mac address: 20:e5:2a:63:fa:7f
oper key: 1001
port priority: 1
port number: 10
port state: 61

Slave Interface: enp2s0f2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0a:f7:83:c4:a6
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:0a:f7:83:c4:a4
port key: 9
port priority: 255
port number: 3
port state: 61
details partner lacp pdu:
system priority: 1
system mac address: 20:e5:2a:63:fa:7f
oper key: 1001
port priority: 1
port number: 11
port state: 61

Slave Interface: enp2s0f3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0a:f7:83:c4:a7
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:0a:f7:83:c4:a4
port key: 9
port priority: 255
port number: 4
port state: 61
details partner lacp pdu:
system priority: 1
system mac address: 20:e5:2a:63:fa:7f
oper key: 1001
port priority: 1
port number: 12
port state: 61
 

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!