Date: Mon, 24 Aug 2009 14:08:48 -0700 From: "Michael K. Smith - Adhost" <mksmith@adhost.com> To: "Graham Smith" <smith.graham23@gmail.com>, <freebsd-net@freebsd.org> Subject: RE: native vlan Message-ID: <17838240D9A5544AAA5FF95F8D52031606934019@ad-exh01.adhost.lan> In-Reply-To: <be61b3bb0908241212i7539feb2p3af06c328eddd732@mail.gmail.com> References: <be61b3bb0908241212i7539feb2p3af06c328eddd732@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 (802.1D) with switches and/or you wanted to put a management IP address on the same subnet as your switch management VLAN subnet. Regards, Mike > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- > net@freebsd.org] On Behalf Of Graham Smith > Sent: Monday, August 24, 2009 12:12 PM > To: freebsd-net@freebsd.org > Subject: native vlan >=20 > Networking folks >=20 > 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 ? >=20 > TIA, > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17838240D9A5544AAA5FF95F8D52031606934019>