hello!
We use a CCR2116 with ROS 7.15.3 and we accentrate there a bunch of VLAN from a carrier.
We use the VLAN in the old way, attached to the interfaces.
We have SFPPLUS3:
vlan tag 8000 (outer)
then we have VLAN 10 (inner), 11, 12 ,13 and so on, inner VLANS.
We then create a bridge and we bridge together only the inner VLANS 10,11,12,13 etc.
We also use the horizon setting to isolate them.
It works.
I would like to ask if exist a working bridge configuration (new way, the single bridge configuration) to have the inner VLANs all togheter but using the switch chip. to have them all hardware offloaded.
We user a /24 ip addressing cover all the vlan bridged together.
i hope in the near future we can do Hardware accelerated vlan filtering of QinQ with NNI and UNI interfaces on the same bridge, and of course also been able to integrate it in a L3 Hw offload setup
Hello.
I have read it but I really dont know how to do it.
tomorrow I will export my current configuration and please can you suggest me doing it in the new way ?
I am not able to make a working test. I really dont understand the way to do it.
Then we have the ip on the provider port to 100.64.0.254/24 (for example) and we use the bridge as virtual interface.
I know that it is not the best way to do it so I ask your suggestions
So, can you specify, you receive tagged 802.1Q traffic from sfpplus2 right? This would be trunk port with customer tags.
Then you apply additional tag and then push traffic to sfpplus1 with Q-in-Q?
Maybe a network diagram of desired setup would help more, if I got you wrong.
A VLAN (the first list of vlans in the configuration) attached to the interfaces.
then I add a second VLAN (inner vlan) , attached to the first vlan (attached to the interfaces)
then i bridge together only the inner vlans!
According to your description, here’s what I think
/interface bridge
add name=bridge vlan-filtering=yes ether-type=0x88a8
/interface bridge port
add interface=sfpplus2 bridge=bridge pvid=100 tag-stacking=yes
add interface=sfpplus1 bridge=bridge
/interface bridge vlan
add bridge=bridge tagged=sfpplus1 untagged=sfpplus2 vlan-ids=100
#all bridge config with ether-type=0x88a8 only care about the service tags, not the ones coming from sfpplus2
/interface vlan
add name=outer_100 interface=bridge vlan-id=100 use-service-tag=yes #this is your outer vlan
#not sure tho if this should be on a bridge or on the outer vlan as both examples exist, but think in this config the latter one is appropriate
add name=inner_4000 interface=bridge vlan-id=4000
add name=inner_4001 interface=outer_100 vlan-id=4001
So here you receive 40xx vlans (which are inner) from sfp2, then you append outer tag 100 and this traffic passes to sfp1 with two tags
hello
unfortunately it doesnt work, I tried but doesnt work.
I will try to explicate here again, because the setup is very simple on the paper but not so simple on the reality.
My objective is to migrate the old-style vlans on the interface, on the new configuration on a single bridge. I currently use the single bridge configuration everywhere but NOT where I have qnq since I am not able to have it working.
I receive from the provider port a QNQ
Outer VLAN and INNER vlan.
I configure the outer VLAN on the phisical port, and the inner VLAN on the VLAN I have just created on the port (the configuration is in the post above).
Then I create a bridge where I put inside all the INNER vlans. I assign a 100.64.0.254/24 and I can communicate with all the inner vlan.
I would like to understand if it is even possibile to to the same configuration but on the single bridge way so I can also use the l3-hw routing in the near future.
