[j-nsp] EX native-vlan-id for transmitting untagged frames?

[Chuck Anderson]

Thanks guys.  Within 5 minutes I got a private reply explaining that 
the "members" list should not contain the native-vlan-id.  Once I 
removed it, things started working properly.

[edit interfaces ge-1/0/11]
unit 0 {
    family ethernet-switching {
        port-mode trunk;
        vlan {
            members 92;
        }
        native-vlan-id 80;
    }
}

On Thu, Jul 23, 2009 at 08:35:19AM +0200, Tomasz Szewczyk wrote:
> Some time ago I made similar configuration for our wi-fi guys. It seems  
> it is working (at least they don't bother me any more :-)
>
> show configuration vlans
> wifi-test {
>    vlan-range 3980-3985;
> }
>
> show configuration interfaces ge-0/0/6 unit 0 {
>    description "** WiFi-test **";
>    family ethernet-switching {
>        port-mode trunk;
>        vlan {
>            members wifi-test;
>        }
>        native-vlan-id 3980;
>    }
> }
>
> Some MAC's are present on this interface on native VLAN.
>
> Tomek
>
> Chuck Anderson pisze:
>> I'm trying to configure a port on an EX4200 to send tagged frames for  
>> 1 or more VLANs, and untagged frames for the "native" VLAN.  For  
>> example:
>>
>> [edit interfaces ge-1/0/11]
>> unit 0 {
>>     family ethernet-switching {
>>         port-mode trunk;
>>         vlan {
>>             members [ 80 92 ];
>>         }
>>         native-vlan-id 80;
>>     }
>> }
>>
>> In this example, I want VLAN 92 frames to be transmitted with an  
>> 802.1q tag of 92, and VLAN 80 frames to be transmitted without any tag  
>> at all.
>>
>> The documentation for "native-vlan-id" seems to suggest that the  
>> statement only affects received frames, not transmitted ones:
>>
>> "Configure the VLAN identifier to associate with untagged packets  
>> received on the interface."
>>
>> That is also my experience when testing this, although I haven't  
>> broken out the analyzer yet to see for sure.
>>
>> Does anyone know of any workarounds I can use to make this work?  I  
>> have some braindead wireless bridges that can't be managed via tagged  
>> frames, but need to transport several VLANs.
>>
>> Thanks.