> Date: Thu, 10 May 2012 09:21:02 -0700 > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: [ovs-dev] Problem with fake bridges > > [adding the list back, please don't drop it again] > > On Thu, May 10, 2012 at 06:17:33PM +0200, Daniele Milani wrote: > > > Date: Thu, 10 May 2012 09:07:29 -0700 > > > From: [email protected] > > > To: [email protected] > > > CC: [email protected]; [email protected]; > > > [email protected] > > > Subject: Re: [ovs-dev] Problem with fake bridges > > > > > > On Thu, May 10, 2012 at 05:25:51PM +0200, Daniele Milani wrote: > > > > I have the following situation: > > > > -I created two fake bridges on the same real bridge (br1 with tag=1 and > > > > br2 with tag=2); > > > > -I created two virtual machines (vm1 and vm2); > > > > -I attached the VM1 interface (vnet1) to br1, and the VM2 interface > > > > (vnet2) to br2; > > > > -I set br1 as default route of VM1 and br2 as default route of VM2; > > > > -if I run "$ ovs-vsctl show " I see that vnet1 tag is 1 and vnet2 is 2. > > > > > > > > The problem is that, if I ping VM1 from VM2, or VM2 from VM1, the > > > > ping succeed. > > > > > > What does "ovs-vsctl show" display? > > > > This is the output I obtain: > > > > Bridge realbridge > > Port "br2" > > tag: 2 > > Interface "br2" > > type: internal > > Port "vnet2" > > tag: 2 > > Interface "vnet2" > > Port "vnet1" > > tag: 1 > > Interface "vnet1" > > Port realbridge > > Interface realbridge > > type: internal > > Port "br1" > > tag: 1 > > Interface "br1" > > type: internal > > I agree that vnet1 and vnet2 should not be able to reach each other. > > Run "ovs-dpctl show" and show us the output. Then start a "ping" > between them, with little other traffic, and while it's going run > "ovs-dpctl dump-flows realbridge". Also it'd be helpful to see the > output of "route -n" and "ifconfig". > > Thanks, > > Ben. This is the output I obtain: ovs-dpctl show lookups: hit:32 missed:27 lost:0 flows: 4 port 0: br2 (internal) port 1: alpha-nic (internal) port 2: beta-nic (internal) port 3: vnet0 port 4: vnet1 ovs-dpctl dump-flows br2 no output VM1 route -n 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 ifconfig eth0 Link encap:Ethernet HWaddr 52:94:00:02:C7:1E inet addr:192.168.1.206 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2011 (1.9 KiB) TX bytes:2412 (2.3 KiB) Interrupt:11 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) VM2 route -n Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 ifconfig eth0 Link encap:Ethernet HWaddr 52:94:00:09:F7:1E inet addr:192.168.2.166 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1466 (1.4 KiB) TX bytes:2034 (1.9 KiB) Interrupt:11 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Daniele
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
