I'm not familiar with mn, but when you tag a port in OpenVswitch as an access port, it tells openvswitch that packets should _not_ be tagged on that interface. Instead, traffic is untagged, but presumed to belong to vlan 20 by the switch. So in that setup, only traffic on eth2 would be tagged. I can't figure out from the provided information whether your ping is traversing eth2 or your wireshark is capturing eth2. If it's only traversing eth1, it would be untagged.
On Tue, Jun 24, 2014 at 4:12 AM, Anurudh Tiwari <anurudh.tiw...@aricent.com> wrote: > > > Hi all, > > > > > > I am trying to implement vlan in mininet open vSwitch. I did the > following .. > > > > Open vSwitch version : 1.9 > > Kernel version : 3.8.0-19-generic > > > > 1. Create a topology using sudo mn command as, > > > > *mininet@mininet-vm:~$* sudo mn --topo=linear,2 > > *** Creating network > > *** Adding controller > > *** Adding hosts: > > h1 h2 > > *** Adding switches: > > s1 s2 > > *** Adding links: > > (h1, s1) (h2, s2) (s1, s2) > > *** Configuring hosts > > h1 h2 > > *** Starting controller > > *** Starting 2 switches > > s1 s2 > > *** Starting CLI: > > *mininet>* > > > > 2. Topology is as > > *mininet> net* > > h1 h1-eth0:s1-eth1 > > h2 h2-eth0:s2-eth1 > > s1 lo: s1-eth1:h1-eth0 s1-eth2:s2-eth2 > > s2 lo: s2-eth1:h2-eth0 s2-eth2:s1-eth2 > > c0 > > *mininet>* > > > > > > 3. I tagged s1-eth1 & s2-eth1 port as access port And s1-eth2 & > s2-eth2 as trunk port with same vlan 1d 20. > > *mininet@mininet-vm:~$* sudo ovs-vsctl set port s2-eth2 trunk=20 > vlan_mode=trunk > > *mininet@mininet-vm:~$* sudo ovs-vsctl set port s1-eth2 trunk=20 > vlan_mode=trunk > > *mininet@mininet-vm:~$* sudo ovs-vsctl set port s1-eth1 tag=20 > vlan_mode=access > > *mininet@mininet-vm:~$* sudo ovs-vsctl set port s2-eth1 tag=20 > vlan_mode=access > > > > > > > > 4. > > *mininet@mininet-vm:~$ sudo ovs-vsctl show* > > fc881c5c-41dd-4904-91e9-591c7a851011 > > Bridge "s2" > > Controller "ptcp:6635" > > Controller "tcp:127.0.0.1:6633" > > is_connected: true > > fail_mode: secure > > Port "s2-eth1" > > tag: 20 > > Interface "s2-eth1" > > Port "s2" > > Interface "s2" > > type: internal > > Port "s2-eth2" > > trunks: [20] > > Interface "s2-eth2" > > Bridge "s1" > > Controller "ptcp:6634" > > Controller "tcp:127.0.0.1:6633" > > is_connected: true > > fail_mode: secure > > Port "s1" > > Interface "s1" > > type: internal > > Port "s1-eth1" > > tag: 20 > > Interface "s1-eth1" > > Port "s1-eth2" > > trunks: [20] > > Interface "s1-eth2" > > ovs_version: "1.9.0" > > *mininet@mininet-vm:~$* > > > > *5. *Now I pinged h1 ping h2. > > *mininet>* h1 ping h2 > > PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. > > 64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=23.9 ms > > 64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.581 ms > > ^C > > --- 10.0.0.2 ping statistics --- > > 2 packets transmitted, 2 received, 0% packet loss, time 1003ms > > rtt min/av > > > > ping is working here. But vlan is not tagged in the wireshark log. > > And also tagging is not working as I tried with s1-eth1(h1) tag with vlan > 10 and s2-eth1(h2) with vlan 20 . ping works in this configuration. > > > > > > *Thanks* > > *Anurudh* > > > "DISCLAIMER: This message is proprietary to Aricent and is intended > solely for the use of the individual to whom it is addressed. It may > contain privileged or confidential information and should not be circulated > or used for any purpose other than for what it is intended. If you have > received this message in error, please notify the originator immediately. > If you are not the intended recipient, you are notified that you are > strictly prohibited from using, copying, altering, or disclosing the > contents of this message. Aricent accepts no responsibility for loss or > damage arising from the use of the information transmitted by this email > including damage from virus." > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > > -- Andrew Mann DivvyCloud Inc. www.divvycloud.com
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
