Date: Tue, 6 May 1997 03:32:24 +0000 (GMT) From: Adam David <adam@veda.is> To: vince@mail.MCESTATE.COM (Vincent Poy) Cc: freebsd-isp@freebsd.org Subject: Re: ISP Terminal Server Remote Site Requirements Message-ID: <199705060332.DAA01485@veda.is> In-Reply-To: <Pine.BSF.3.95.970505193132.1286w-100000@mail.MCESTATE.COM> from Vincent Poy at "May 5, 97 07:33:35 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > In the meantime, I suppose a Linux box just to contain the ports and run > > the driver, forwarding raw TCP/PPP datastreams to a FreeBSD box, might > > just cut it. > > Wouldn't this create a bottleneck though? At 100Mb/s on a dedicated segment... How many ports at what load would saturate it? Dialup traffic is typically still bursty, and you can get full duplex at 100Mb/s. If I'm going to run Linux in a server context, I'd prefer it to be barebones/blackbox in as isolated an environment as possible (i.e. a port engine, nothing more). > I thought FreeBSD did support the Cyclades boards already? Y series, maximum speed 115.2kb/s each port. Z series is a possible future driver. Linux and Windows drivers already exist. > > > So FreeBSD can't do radius as a server yet? > > > > Yes. Trouble is FreeBSD does not have radius support yet in pppd (or ppp?). > > What about for a terminal server such as a Xyglogics or Livingston > that needs radius authetication from a FreeBSD host? Would that work? Of course it would work, but those terminal servers cannot be reused to run FreeBSD later. :) -- Adam David <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705060332.DAA01485>