Hi Joo, 1) To assign an eth1 port inside a bridge to a vlan 40 use “ovs-vsctl set port eth1 tag=40 vlan_mode=native-untagged” This way you can avoid the use of fake bridges for this purpose, this command is equivalent to “switchport access vlan 40” in the fabric world. 2) The packets that are sent out using br0 interface will be untagged, the device connected to the other side of p3 will receive it in it’s native vlan, so if you have other hosts running in this native vlan then yes you can communicate. 3) Yes, you can see all the packets in the bridge but use the -e option to also see the VLAN Tag in layer 2 frame “tcpdump -i br0 -e”
Sent from Mail for Windows 10 From: Joo Yong-Seok Sent: Wednesday, February 1, 2017 9:30 PM To: [email protected] Subject: [ovs-discuss] Regarding on VLAN Hi, Quick questions in regard of VLANs 1) Are we able to assign VLAN to local-port? (not sure whether it is really required...) If so, how? (without using "fake-bridge"). 2) If not, I have following situation. - br0(ovs-bridge) has p1, p2, p3 and p4 as a bridge port. > p1 - tag 10 > p2 - tag 20 > p3 - trunk port > local-port (br0). - with above config, am I able to communicate to other host by using the IP address on br0? 3) If I run tcpudmp -i br0, am I able to see all the packets from every port? Thanks in advance. Best regards, - yongseok
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
