Date: Tue, 25 Aug 2009 08:23:55 -0400 From: Steve Bertrand <steve@ibctech.ca> To: =?ISO-8859-1?Q?Bal=E1zs_M=E1t=E9ffy?= <repcsike@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: native vlan Message-ID: <4A93D7DB.3050500@ibctech.ca> In-Reply-To: <c4b701070908241434o82a540aga16022630df1c94@mail.gmail.com> References: <be61b3bb0908241212i7539feb2p3af06c328eddd732@mail.gmail.com> <17838240D9A5544AAA5FF95F8D52031606934019@ad-exh01.adhost.lan> <c4b701070908241434o82a540aga16022630df1c94@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Balzs Mtffy 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. If
I have a host (or switch etc) that is incapable of 802.1q that I want
configured into a non-native VLAN (vlan 500 for example), then I would
configure the port the host is connected to as a vlan 500 access port.
The device connected to that port would then be part of vlan 500.
> 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 the native
> vlan's number is 1 by the way not 0, as far as I know.
Yes, in Cisco-land, VLAN 1 is the default, native VLAN. Most people will
disable vlan 1, and configure native to be an arbitrary number.
Also, there are cases where the native vlan warnings are acceptable,
such as when you need to bridge your network via layer-2 to an outside
network that you don't control, and both parties are using separate
native vlans.
Steve
[-- Attachment #2 --]
0 *H
01 0 + 0 *H
00CK9AbxIUw0
*H
0b1 0 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
090507231610Z
100507231610Z0B1 0 UThawte Freemail Member1 0 *H
steve@ibctech.ca0"0
*H
0
DZ杙<2IⵀfrsE6 q?0.>
S@Œ!V?A\Q
r-aZ
Ōf/0{OYQhɏߴ
F_\Q0BF=<_.a*3ep eY |t ݼcvlҷ+@p iQA{2E9 WN4[Z`h6VM/zPbd(G C ^K6XV4j<t -0+0U 0steve@ibctech.ca0 U 0 0
*H
æ|85aQz-*3HG .s*Fw*`HvFw; 9ytƘn0taC/:WC+LÙ{Oq 1 n00CK9AbxIUw0
*H
0b1 0 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
090507231610Z
100507231610Z0B1 0 UThawte Freemail Member1 0 *H
steve@ibctech.ca0"0
*H
0
DZ杙<2IⵀfrsE6 q?0.>
S@Œ!V?A\Q
r-aZ
Ōf/0{OYQhɏߴ
F_\Q0BF=<_.a*3ep eY |t ݼcvlҷ+@p iQA{2E9 WN4[Z`h6VM/zPbd(G C ^K6XV4j<t -0+0U 0steve@ibctech.ca0 U 0 0
*H
æ|85aQz-*3HG .s*Fw*`HvFw; 9ytƘn0taC/:WC+LÙ{Oq 1 n0?0
0
*H
01 0 UZA10U Western Cape10U Cape Town10U
Thawte Consulting1(0&U Certification Services Division1$0"UThawte Personal Freemail CA1+0) *H
personal-freemail@thawte.com0
030717000000Z
130716235959Z0b1 0 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA00
*H
0 Ħ<UsUNʙZ hup [v :aQP
0cZ,p+Z?qV˯< 6$*+w=+>@dקe*TH<a@ dr` 00U 0 0CU <0:08642http://crl.thawte.com/ThawtePersonalFreemailCA.crl0 U 0)U "0 0 10UPrivateLabel2-1380
*H
HP .
fgCL!6 -6/ P p<ab:~ t%Pb'qW%ݩ9 Oe_N4[5MwV!x!5$ F]_eO1d0`0v0b1 0 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAK9AbxIUw0 + 0 *H
1 *H
0 *H
1
090825122355Z0# *H
1Fh'\X 4G0R *H
1E0C0
*H
0*H
0
*H
@0+0
*H
(0 +71x0v0b1 0 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAK9AbxIUw0 *H
1xv0b1 0 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAK9AbxIUw0
*H
.KHwV"捙_ Iq=CutoݤK9C~-D e,K<ϲc#moѢѡV'sl.aP.`+м]k eE,]Cň'NFݏvkl1`WUbg 3F-t
<^1[ J+s>21x9lAh%IIơ X5(LEӄΰpW{JZ'gdVrX.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A93D7DB.3050500>