OpenVZ Forum


Home » Mailing lists » Users » Problems with bridging across multiple containers.
Problems with bridging across multiple containers. [message #28581] Mon, 24 March 2008 16:18
feighery is currently offline  feighery
Messages: 1
Registered: March 2008
Junior Member
From: openvz.org
I am having a problem with openvz and bridging across multiple containers.
Any help or insight would be greatly appreciated.  
 
> uname -a
Linux blu12 2.6.18-ovz028stab053.5my.kernel.v5-enterprise #4 SMP Mon Mar 17
14:06:14 EDT 2008 i686 athlon i386 GNU/Linux

My architecture can be boiled down to the following. I have three separate
containers.
 
veid 101 has 1 Ethernet interface
 eth1 - 10.100.1.1
 
veid 102 has 2 Ethernet interfaces
 eth1 - 10.100.1.2
 eth2 - 10.100.1.3
 in addition I create a bridge 'test1' on 102 to bridge eth1 and eth2
together.
 
veid 103 has 1 Ethernet interface
 eth1 - 10.100.1.21
 
Given this scenario I should be able to ping from 10.100.1.1 to 10.100.1.21
and container 102 should simply bridge all frames on eth1 and eth2.  However
I cannot even get the arp request from 10.100.1.1 to 10.100.1.21.
 
on veid 101:  I can see the arp request leave the eth1 interface via tcpdump
on the Host:   I can see the arp request received on the veth101.1 interface
via tcpdump
on the Host:   I can see the arp request leave the veth102.1 interface via
tcpdump
on veid 102:   I can see the arp request received on the eth1 interface via
tcpdump
on veid 102:   I can see the arp request on the test1 bridged interface via
tcpdump
on veid 102:   I can see the arp request leave the eth2 interface via
tcpdump
on the Host:   I DO NOT see the arp request on the veth102.2 interface via
tcpdump
 
In addition. on veid 102, 'ifconfig eth2' does not show the receive or xmit
count increasing.  Is there some type of low layer filtering occurring?  If
so how can it be disabled.?
 
Many thanks
 
Best regards
    Pat Feighery
Previous Topic: ARP problems when HN and VE are on different subnets (and interfaces)
Next Topic: Problem with TCP window too large for TCPRCVBUF still present
Goto Forum:
  


Current Time: Thu Oct 17 17:35:50 GMT 2019