Hi list, I'm trying to configure a untagged native VLAN on a trunk interface in a sensible way on an EX switch running JUNOS 10.1R1.8.
If I do: family ethernet-switching { port-mode trunk; vlan { members all; } native-vlan-id 2; } ...the egress packets from VLAN 2 will be tagged. If I instead do: family ethernet-switching { port-mode trunk; vlan { members 3-4094; } native-vlan-id 2; } ...the commit fails with the first undefined VLAN ID: error: No vlan matches tag 4 for interface ge-0/0/46.0 error: configuration check-out failed What works is to add all configured VLANs (except 2) to the members statement. However that with a several hundred configured VLANs that configuration statement gets really nasty-looking. And it'd be easy to forget to add a newly configured VLAN there, too, so I'd rather avoid doing it that way if at all possible. Any suggestions on how to do it better would be greatly appreciated! Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com/ Tel: +47 21 54 41 27 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp