Re: [ovs-discuss] Flow Rules for VLAN in Open vSwitch

2014-06-25 Thread Andrew Mann
If you want inter-vlan communications, it would be more generic to define a patch-port between the two vlans modifying the vlan on the way through: what you have at the start is: vlan:100 vlan:100 | red1 | -->

Re: [ovs-discuss] Flow Rules for VLAN in Open vSwitch

2014-06-25 Thread shruti rao
Hi Andrew and Ben, Thanks for your responses. Following your suggestions, I modified the flow rules. mininet> sh ovs-ofctl dump-flows s1 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=1456.805s, table=0, n_packets=0, n_bytes=0, idle_age=1456, icmp,dl_src=00:00:00:00:00:03,dl_dst=00:00:00:00:0

Re: [ovs-discuss] Flow Rules for VLAN in Open vSwitch

2014-06-24 Thread Andrew Mann
I'm still learning OVS, but I'll take a stab: 1) Before the ping starts, an ARP request will be sent which will be broadcast. It won't match the destination MAC because the purpose of the ARP is to find out what the MAC is. Normally the VLAN would take care of broadcasting the packet out to all h

Re: [ovs-discuss] Flow Rules for VLAN in Open vSwitch

2014-06-24 Thread Ben Pfaff
On Tue, Jun 24, 2014 at 10:08:28AM -0700, shruti rao wrote: > mininet> sh ovs-ofctl dump-flows s1 > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=160.318s, table=0, n_packets=0, n_bytes=0, > idle_age=160, actions=NORMAL > mininet> sh ovs-ofctl dump-flows s2 > NXST_FLOW reply (xid=0x4): > cook

[ovs-discuss] Flow Rules for VLAN in Open vSwitch

2014-06-24 Thread shruti rao
Hi, I am new to Open vSwitch and am trying to create a VLAN with two switches (s1, s2) having 2 hosts (s1 having red1 and blue1 and s2 having red2 and blue2) each and no controller. My configuration is as mentioned below: mininet> net s1 lo: s1-eth1:red1-eth0 s1-eth2:blue1-eth0 s1-eth3:s2-eth1 s