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 the one Cisco product that doesn't follow that VLAN1-rule. On the Cisco Aironet AP 1200, you can run a Dot1Q VLAN trunk to map X-number of different ESSIDs-to-VLANs. You do this by setting the "bridge-group" of the Ethernet Subinterface and the Dot11Radio subinterfaces to the same VLAN that you would like to bridge. Whereas, management traffic (Monitoring, etc.) has to run on "BVI1", or Bridged Virtual Interface 1, which must transmit untagged on Ethernet0. This stipulation is set by the Bridging IOS on the AP1200. If your management VLAN is something other than VLAN1 (god forbid), you simply set the "native VLAN" on that Dot1Q trunk port on the Catalyst to some other VLAN _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
