From owner-freebsd-isp Thu Nov 28 19:35:57 2002 Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4597E37B401 for ; Thu, 28 Nov 2002 19:35:54 -0800 (PST) Received: from mx1.purplecat.net (mx1.purplecat.net [208.133.44.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98FED43E9C for ; Thu, 28 Nov 2002 19:35:53 -0800 (PST) (envelope-from peter@skyrunner.net) Received: (qmail 4585 invoked from network); 29 Nov 2002 03:35:59 -0000 Received: from unknown (HELO micron) (208.150.25.130) by mx1.skyrunner.net with SMTP; 29 Nov 2002 03:35:59 -0000 From: "Peter Brezny" To: "Jason Hunt" Cc: Subject: RE: Freebsd as vlan trunk controller. Date: Thu, 28 Nov 2002 22:35:50 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20021128195559.I82419-100000@lethargic.dyndns.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jason, I had a typo, it's a 2924m-xl Thanks for the tips however... My main problem here is that I don't really know what I'm talking about. I'm just now looking into configuring vlans with freebsd and literally know very little more than about a half hours flip through the man pages. I want a freebsd box with 2 fast Ethernet adapters to act as a router, and instead of putting several multiport cards into that box, I want one of the fast Ethernet adapters to go into a switch, which will have vlans. I want the bsd system to send the traffic to the appropriate vlan, so that if I desire, I could have the equivalent of 24 nic's in one freebsd box. I believe what I am after is something that can handle the 802.1q Any help on clearing up terminology and pointers to good hardware to use, whether or not this Cisco 2924m-xl or another Cisco 1900. I've got a lot of reading to do, i've only scraped the tip of the iceburg. Any tips would be appreciated. Peter Brezny Skyrunner.net -----Original Message----- From: Jason Hunt [mailto:leth@primus.ca] Sent: Thursday, November 28, 2002 8:23 PM To: Peter Brezny Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Freebsd as vlan trunk controller. On Thu, 28 Nov 2002, Peter Brezny wrote: > I'm looking for pointers/tips/stories on configuring freebsd for use as a > vlan trunk controller for connecting to a cisco 2624 switch. > > Any pointers to docs/how to's or personal experience is appreciated. > Are you referring to the VLAN Trunking Protocol? If so, then from what I can tell, the 2624 does not support VTP. It doesn't even seem to support actual VLAN tagging. (And, if it supports one it should support the other.) Instead, this switch just allows you to create multiple broadcast domains within itself, not actual VLANs. Also, I think you might be referring to doing a "router on a stick" configuration. That is, every VLAN can talk to a single port. This requires the NIC support either ISL (Inter-Switch Links) or 802.1Q trunking. As far as that goes, I've not looked into anything like that before. -----Original Message----- From: Jason Hunt [mailto:leth@primus.ca] Sent: Thursday, November 28, 2002 8:23 PM To: Peter Brezny Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Freebsd as vlan trunk controller. On Thu, 28 Nov 2002, Peter Brezny wrote: > I'm looking for pointers/tips/stories on configuring freebsd for use as a > vlan trunk controller for connecting to a cisco 2624 switch. > > Any pointers to docs/how to's or personal experience is appreciated. > Are you referring to the VLAN Trunking Protocol? If so, then from what I can tell, the 2624 does not support VTP. It doesn't even seem to support actual VLAN tagging. (And, if it supports one it should support the other.) Instead, this switch just allows you to create multiple broadcast domains within itself, not actual VLANs. Also, I think you might be referring to doing a "router on a stick" configuration. That is, every VLAN can talk to a single port. This requires the NIC support either ISL (Inter-Switch Links) or 802.1Q trunking. As far as that goes, I've not looked into anything like that before. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message