Hello everyone,
I recently setup my 3rd host node and have bonded (alb) pro/100 interfaces to bridge to the wan vlan, an e1000 for the "lan" bridge, and an r8168 on the "pfsync" vlan.
After setting up bonding on the e100, if I ping the (public) ip of the GUEST from my firewall/gateway, the MAC address of the HOST'S bond is assigned to the guest's IP. When this happens, the gateway cannot ping the guest IP.
If I disable bonding and use either of the 2 slaves (which confirms they are both on the correct vlan) as an individual interface bridged to wlan vlan, with no other changes to the guest or host, then everything works fine.
This is bizarre. Has anyone seen this before? Is this a bug in bridging ? e100 driver?
I am using 2.6.32 kernel that comes with proxmox.
I recently setup my 3rd host node and have bonded (alb) pro/100 interfaces to bridge to the wan vlan, an e1000 for the "lan" bridge, and an r8168 on the "pfsync" vlan.
After setting up bonding on the e100, if I ping the (public) ip of the GUEST from my firewall/gateway, the MAC address of the HOST'S bond is assigned to the guest's IP. When this happens, the gateway cannot ping the guest IP.
If I disable bonding and use either of the 2 slaves (which confirms they are both on the correct vlan) as an individual interface bridged to wlan vlan, with no other changes to the guest or host, then everything works fine.
This is bizarre. Has anyone seen this before? Is this a bug in bridging ? e100 driver?
I am using 2.6.32 kernel that comes with proxmox.
Last edited: