From owner-freebsd-net@FreeBSD.ORG Mon Aug 24 21:34:58 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC413106568B for ; Mon, 24 Aug 2009 21:34:58 +0000 (UTC) (envelope-from repcsike@gmail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 41A168FC0A for ; Mon, 24 Aug 2009 21:34:58 +0000 (UTC) Received: by ewy5 with SMTP id 5so1332167ewy.36 for ; Mon, 24 Aug 2009 14:34:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=hnxhZJTeF7ttFboTbSwDZO7otVpKLGze3kGyRpzn1XQ=; b=pKVy0mfVEHVHXfLnAW+/7B0pRLP0I9vDr31wsJRJuAJ38ZphPplHWR3brttWzk+QNy OYGXn46QgA+mBUjO8ySJPEa28N1/i0w40U1VP1PO61+yITaa8vmmx+qZA661apWaEFtA QvVSMOFpimpU0KRrdUnXplLRxuBS6pMs8j68k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Z9n6HAGmTUGcM5IOH85TjOvvdHFDd1bfOgJipFLuFuW0u7CJ05MB40t4vZ1RSklgpf BLnVyRUKVvhNEpXL7KCY+4gf7p3U7cxii6HYc8xNrZbPPoE1+FN7+6GMlhi362rfZDdm UoRQs6YbsJ1gQjhL8ORxC0ydXwWsoLNPxEJ04= MIME-Version: 1.0 Received: by 10.211.200.20 with SMTP id c20mr2611963ebq.15.1251149697352; Mon, 24 Aug 2009 14:34:57 -0700 (PDT) In-Reply-To: <17838240D9A5544AAA5FF95F8D52031606934019@ad-exh01.adhost.lan> References: <17838240D9A5544AAA5FF95F8D52031606934019@ad-exh01.adhost.lan> Date: Mon, 24 Aug 2009 23:34:57 +0200 Message-ID: From: =?ISO-8859-1?B?QmFs4XpzIE3hdOlmZnk=?= To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: native vlan X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 21:34:58 -0000 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 the native vlan's number is 1 by the way not 0, as far as I know. Hope this helps! Regards, Repcsi. 2009/8/24 Michael K. Smith - Adhost > 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 > > > > 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 ? > > > > 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" > _______________________________________________ > 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" >