*BSD News Article 71651


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!metro!metro!asstdc.scgt.oz.au!nsw.news.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!arclight.uoregon.edu!news.bc.net!news.mindlink.net!van-bc!news.rmii.com!usenet
From: tjacobs@vaultbbs.com (Thomas R. Jacobs, Jr.)
Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.bsd.misc
Subject: SLIP problems with FreeBSD 2.1
Date: Fri, 21 Jun 1996 04:06:58 GMT
Organization: Vault Information Services
Lines: 24
Message-ID: <4qd72c$3m8@natasha.rmii.com>
Reply-To: tjacobs@vaultbbs.com
NNTP-Posting-Host: indolin.vaultbbs.com
X-Newsreader: Forte Free Agent 1.0.82
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:21811 comp.unix.bsd.misc:1145

Some of our users are having occasional dialup problems while using
SLIP.  This problem has happened using both Windows 95 Dialup
Networking and Trumpet Winsock.  The host system is running a FreeBSD
2.1SNAP release.  What happens is this:

The user connects, logs in, and is added to the route table.
Everything looks good from the host side.  However, the user can not
access anything (IRC, WWW, etc.) and pings of the host fail.  The
route table shows that no packets are being transfered from the users
system.  This happens no matter what dialup port is accessed, and has
happened when the host was using comm ports and after the host system
was switched to a BOCA multiport.  The problem is also intermittent.
Some times it only last for a couple of hours, and one user has gone
several days with the problem, only have it start working again on its
own.

Any help or ideas on what could be causing this would be greatly
appreciated!

Thomas R. Jacobs, Jr.     | tjacobs@vaultbbs.com
VIS SysAdmin2 - Webmaster | http://www.vaultbbs.com/~tjacobs
                          | PGP Key available via finger.
Sleep \'slep\ n 1 : A completely inadequate substitute for caffeine.