*BSD News Article 36770


Return to BSD News archive

Xref: sserve comp.os.386bsd.questions:13735 comp.protocols.ppp:6178 comp.os.linux.help:59174
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!news.sprintlink.net!indirect.com!wes
From: wes@indirect.com (Barnacle Wes)
Newsgroups: comp.os.386bsd.questions,comp.protocols.ppp,comp.os.linux.help
Subject: Re: PPP at 115200 bps (FreeBSD or Linux?) to a Xyplex MX1620?
Followup-To: comp.os.386bsd.questions,comp.protocols.ppp,comp.os.linux.help
Date: 9 Oct 1994 23:45:37 GMT
Organization: Internet Direct, Inc.
Lines: 30
Message-ID: <379vb1$ksh@herald.indirect.com>
References: <1994Oct6.153307.1@wittenberg.edu>
NNTP-Posting-Host: bud.indirect.com
X-Newsreader: TIN [version 1.2 PL2]

Mike Andrews, Comp Ctr (mandrews@wittenberg.edu) wrote:

: I have a spare 386/40 that I've been unable to sell, and am
: considering turning it into a dedicated PPP router for my home
: network.
: Will FreeBSD (or NetBSD) run PPP at 115200 bps?  I'm under the
: impression that Linux can't go over 38400, and I have a V.34 modem
: (USR Courier).  (There IS a 16550 UART in the machine.)

Sure.  I've played with PPP hard-wired at 115K, it worked OK.  I'm
on a V.FC 28.8 modem line here, with the port speed set to 115200
just in case the modem (and I) get lucky.  ;^)


: If so, am I going to be able to cram all the binaries and a decent
: size swap onto an 80 meg drive?  (swap's going to be the problem,
: since this is a 4 meg machine.  I can upgrade if I have to, but as
: I was going to sell this machine anyway, I'd rather not.  :-)  I
: know Linux will fit.

Well, if you're going to use the machine *only* as a router, you
really don't need *all* of the binaries.  Plus, you can keep the
swap space small if you're not planning to use it multi-user, say,
8Mb swap partition or so.  I've got an old Everex Step 386/20 around
here, with an 4Mb RAM and an 80Mb MFM drive, that I am planning to
do this with.  Buy a $40 NE2000 clone, stick my V.FC 28.8 modem in
it, and call it "router."  Plus install a firewall and some monitoring
tools, just 'cause it sounds good.

	Wes Peters