[e-nsp] vman compatibility

[Laurent HENRY (EHESS/CRI)]

Hi and thank you.

What i want to do is enabling vman/qinq on the outside to tunnel my
internal vlans ID through my provider network with the 48si and catch it
back on another network across my provider's one the same way.

So in what i understand today, it would be necessary to validate dot1q
jumbo, adjust primary/secondary vman tags to make ethernet encapsulation
possible, and configure a suitable primary vman ID on my provider access
port, let's say on only port number 1.

By the way, other switch ports with internal classic dot1q trafic don't
have to change at all and still recognize 0x8100, changes just have to
apply to outside access port to cross another network.

As it seems,it does not seem possible that way with this i-chip then...



Le Jeu 20 novembre 2008 09:17, Mikael Abrahamsson a écrit :
> On Thu, 20 Nov 2008, Laurent HENRY (EHESS/CRI) wrote:
>
>> A "small" summit 48si.
>>
>> This means 0x9100 as the vman type and 0x8100 to keep encapsulated
>> packet
>> type ?
>
> On the i-chipset platform the "vman" is just a way to change the switches
> behaviour when it comes to "what is a vlan encapsulated packet".
>
> So changing it to 0x9100, means the switch will L2 switch 0x8100 like any
> other packet, because it'll stop recognising standard .1q frames as being
> .1q encapsulated.
>
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
> _______________________________________________
> extreme-nsp mailing list
> extreme-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/extreme-nsp
>