I wrote:
>
> Hi Stephen,
>
> Today, I looked into a similar problem with my brother-in-law's machine... he
> just moved his office out of the house and into a real office.
>
> Looking into the problem (before I saw this thread), it appears the problem is
> due to a timer popping early. Looking at the log of a successful connection, a
> 10 second timer gets set for initial modem handshaking, then a longer timer (75
> seconds in his case: /etc/ppp/ppp.chatscript) for the actual login... In the
> failing attempts, the chatscript timer is not getting set, causing the initial
> 10 second timer to pop and kill the connection before it completes.
>
> I'll look into this some more later; but thought it might be useful to post this
> now...
>
> Pierre
Finally got the answer on this one... turns out when he moved, he plugged the
modem into the wrong port and forgot to mention it until I quizzed him about the
problem. So, the 10 second timer was the correct one to pop...
To those whose connections fail, does the sighup occur when a timer expires
(check your log's timestamps)...? I suspect so.
Pierre
> Stephen Bosch wrote:
> >
> > So, Doc...
> >
> > have you confirmed that it is the ISP that is causing the problem?
> >
> > I hope I don't have to switch ISPs... there has to be a way of figuring out
> > what they may have changed...
> >
> > And again -- *why* does it work when you dial with kppp? I think the answer
> > resides elsewhere...
> >
> > -Stephen-
> >
> > ----- Original Message -----
> > From: D. R. Evans <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 30, 2000 5:43 PM
> > Subject: Re: [expert] pppd dying unexpectedly
> >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > On 28 Aug 00, at 20:05, Anton Graham wrote:
> > >
> > > > Submitted 28-Aug-00 by Stephen Bosch:
> > > >
> > > > > And again -- that SIGHUP is damn peculiar -- who is sending it?
> > > >
> > > > I suspect that that is modem generated. Every modem i have ever owned
> > > > generates a SIGHUP when the other end hangs up on it.
> > > >
> > >
> > > That makes sense. If the ISP doesn't like the PPP handshaking for whatever
> > > reason (maybe USWest figures I'm running Linux so it should shut me up)
> > > then it probably causes the line to go down, thus causing the SIGHUP.
> > >
> > > Doc Evans
> > >
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: PGP 6.0.2 -- QDPGP 2.60
> > > Comment: Key obtainable from servers: ID 0x362912B8
> > >
> > > iQA/AwUBOa2cGWnXrLw2KRK4EQKVaACfZHtExZWFQdoDOH6R1h+srOl6Eh4AoKif
> > > heaA7ftO1SgLFQwyi0Q9z62F
> > > =C6LE
> > > -----END PGP SIGNATURE-----
> > >
> > > ----------------------------------------------------------
> > > D.R. Evans N7DR / G4AMJ [EMAIL PROTECTED]
> > >
> > > The last of the Chronicles of the Three Lands, "Phendric",
> > > has been published:
> > > http://www.sff.net/people/N7DR/drevans.htp
> > > ----------------------------------------------------------
> > >
>
> --
> Linux (Up 39 days) -- Reboots are for system upgrades...
> Currently running 124 processes; CPU activity: user=1.0%, system=0.4%
> Last reboot reason: Installed new BackUPS power supply.
--
Linux (Up 40 days) -- Reboots are for system upgrades...
Currently running 124 processes; CPU activity: user=1.0%, system=0.4%
Last reboot reason: Installed new BackUPS power supply.
