*BSD News Article 94663


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.Hawaii.Edu!news.caldera.com!enews.sgi.com!news-feed.inet.tele.dk!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!rill.news.pipex.net!pipex!hole.news.pipex.net!pipex!news.utell.co.uk!usenet
From: brian@shift.utell.net (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: PPP connection keeps hanging up
Date: 29 Apr 1997 09:35:24 GMT
Organization: Awfulhak Ltd.
Lines: 49
Message-ID: <5k4fcs$h54@ui-gate.utell.co.uk>
References: <3363E93E.17F0@socs.uts.edu.au> <5k2h5e$382@matrix.eden.com>
Reply-To: brian@awfulhak.org, brian@utell.co.uk
NNTP-Posting-Host: shift.utell.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:39909

In article <5k2h5e$382@matrix.eden.com>,
	jrowland@news.eden.com (John Rowland) writes:
> In article <3363E93E.17F0@socs.uts.edu.au>,
> Martin Gisch  <m.g@bigfoot.com> wrote:
>>
>>I'm trying to start a dialup PPP session to my ISP under 2.2.1 but it
>>only ever lasts about 5 mins at most.
>>
>>The only config stuff I've set up is the address and host settings in
>>/stand/sysinstall (network interfaces or something).
>>
>>After adding a default route to my providers host: 
>>	add * * 203.10.110.52
>>
>>Everything works fine...for a few minutes, then it abruptly hangs up.
>>
>>Is this a common problem, or is there some way to diagnose what the
>>problem may be? I'm fairly new to FreeBSD, so I don't know too much
>>about it yet.
>>
>>Thanks if anyone can help.
>>
>>Regards,
>>		Martin Gisch.
> 
> 
> I had this problem, where my ISP changed hardware and my dedicated
> ppp connection would hang up after three minutes.  I could see in the
> log that it had hung up because of too many lost packets or something.
> Durring the three minutes everything worked OK.  I fixed it by adding
> these lines to my config file:
> 
> disable lqr
> deny lqr
> 
> I don't really know what these mean, but I was desparate, and it
> fixed the problem so why complain?

lqr stands for line quality request.  It's a "are you still there"
protocol that is known not to work from the client side (but does
work from the server side).

> -John
> jrowland@bluecollar.com

-- 
Brian <brian@awfulhak.org> <brian@freebsd.org>
      <http://www.awfulhak.org>
Don't _EVER_ lose your sense of humour !