[j-nsp] Double-tagging on EX

[Kevin Wormington]

I have never tried this in a q-in-q application, but what if you put "native-vlan-id" on the access ports...will that add the inner tag when it goes out a trunk port?  Might be worth a shot if you haven't tried it.

Kevin

On 02/22/2012 11:44 AM, Alexander Frolkin wrote:
> On Wed, Feb 22, 2012 at 03:39:12PM +0100, Bjørn Tore wrote:
>> interfaces {
>>     ge-0/0/0 {
>>         description "upstream";
>>         mtu 9192;
>>         unit 0 {
>>             family ethernet-switching {
>>                 port-mode trunk;
>>             }
>>         }
>>     }
>>     ge-0/0/2 {
>>         description "customer";
>>         mtu 9192;
>>         unit 0 {
>>             family ethernet-switching {
>>                 port-mode access;
>>             }
>>         }
>>     }
>> }
>> vlans {
>>     my-vlan {
>>         description QinQ;
>>         vlan-id 7;
>>         interface {
>>             ge-0/0/0.0;
>>             ge-0/0/2.0;
>>         }
>>         dot1q-tunneling;
>>     }
>> }
> 
> I think this assumes that the frames arrive on ge-0/0/2 tagged.  Our
> frames come in to the switch untagged, this is the whole problem.
> 
> 
> Alex
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp