On Mon, 2009-08-24 at 12:12 -0700, Graham Smith wrote:
> requiring creation of native vlan (vlan 0) and why native vlan are
> most suitable for this scene ?
Cisco highly recommend changing the management VLAN away from VLAN1.
Here's an example, of using alternative native VLANs, ironically, on t
Balázs Mátéffy wrote:
> Hi,
>
> I would add, that if you have hosts, a hub or an unmanaged switch without
> vlan capability between two switches with vlans those devices will use the
> native vlan.
This isn't entirely accurate.
Note that the VLAN tag is applied during the ingress into the switch
Graham Smith wrote:
Networking folks
Nothing to do with freebsd per say, but can someone tell real life scenario
requiring creation of native vlan (vlan 0) and why native vlan are most
suitable for this scene ?
Assuming you're referring to what's in the 802.1q header: it's what
802.1p puts i
Hi,
I would add, that if you have hosts, a hub or an unmanaged switch without
vlan capability between two switches with vlans those devices will use the
native vlan. And another thing: you have to make the native vlan the same on
the switches or you will get native vlan error messages. In cisco th
Well, in Cisco speak, the native vlan is untagged and used for
management. So, all your customer traffic comes in tagged with various
VLAN's and your management stuff remains untagged and localized to the
switching infrastructure.
So, I guess you would do it if you wanted to speak spanning tree
(
