From owner-freebsd-questions Mon Feb 16 23:25:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24165 for freebsd-questions-outgoing; Mon, 16 Feb 1998 23:25:32 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from luke.cpl.net ([209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24159 for ; Mon, 16 Feb 1998 23:25:30 -0800 (PST) (envelope-from shawn@luke.cpl.net) Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.8/8.6.12) with SMTP id XAA14439; Mon, 16 Feb 1998 23:23:10 -0800 (PST) Date: Mon, 16 Feb 1998 23:23:10 -0800 (PST) From: Shawn Ramsey To: Doug White cc: Gary Dunn , freebsd-questions Subject: Re: FreeBSD as router, terminal server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > DigiBoards and several others. > > > What kind of interface is available for the Internet side of the box, > > the place where a router usually sits? > > That depends on what the ISP ordered and who they're connected to. This > is often why you need a router (or bridge) -- to adapt the incoming line > to whatever your internal network is using (probably Ethernet of > somesort). You can turn your FreeBSD box into a router with a card to interface with a DSU. I think this is what the poster was looking for. We use a 4 port ETInc card, and they work great. So far at least..we only have 2 1.54 feeds on it at the moment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message