Thanks for pointing it out, somehow intuitively i thought it is an
egress property of sub interface to attach vlan tag.
with the correct config to access ports in the bridge domain fix the
egress with a vlan tag on the trunk port.
however now while receiving the tagged packet on trunk port i see
correct tag, but it somehow is not associating it to correct bridge
domain.
so i have interface host-eth10 and sub interface host-eth10.10
host-eth10 is associated to bridge domain 2 and sub interface is
associated to bridge domain 3
when VPP receives tagged packet with vlan 10 it still associates it to
bd 2 and not bd 3
if i don't associate any bd with base interface it just drops the
packet with some error.
Also somewhere we expect to use translate vlan tags to different
external tags which need not be same as the one tag for bridge domain,
please let us know if it is a supported config.
set interface l2 tag-rewrite GigabitEthernet2/0/0.10 translate 1-1
dot1q 10
Regards,
Prabhjot
----- Original Message -----
From:
"John Lo (loj)" <l...@cisco.com>
To:
"Prabhjot Singh Sethi" <prabh...@techtrueup.com>,
"vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Cc:
Sent:
Mon, 25 Sep 2017 20:38:11 +0000
Subject:
RE: [vpp-dev] Trunk ports with VPP
The access port config from the example doc is aa follows:
create vhost socket /tmp/sock2.sock server
set interface state VirtualEthernet0/0/2 up
set interface l2 bridge VirtualEthernet0/0/2 200
set interface l2 tag-rewrite VirtualEthernet0/0/2 push dot1q 200
Note the tag-rewrite config on access port to push the VLAN tag on
the packet. Did you do this on the access ports?
Regards,
John
FROM: vpp-dev-boun...@lists.fd.io
[mailto:vpp-dev-boun...@lists.fd.io] ON BEHALF OF Prabhjot Singh Sethi
SENT: Monday, September 25, 2017 2:11 PM
TO: vpp-dev@lists.fd.io
SUBJECT: [vpp-dev] Trunk ports with VPP
Hi,
i am trying to achieve trunck ports with VPP using following
documentation
https://wiki.fd.io/view/VPP/Interconnecting_vRouters_with_VPP#Create_TRUNK_ports
[1]
only difference is that i am trying this with host interfaces
connected to netns instance.
However packet egressing on this trunk port remains untagged
irrespective of which sub-interface it came from.
i am i missing something over here ?
Regards,
Prabhjot
Links:
------
[1]
https://wiki.fd.io/view/VPP/Interconnecting_vRouters_with_VPP#Create_TRUNK_ports
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
