"D. R. Evans" wrote:
If I kill the script-based bit, then I never get to the PAP. BOTH are
necessary, which does seem faintly ridiculous. But perhaps not without
precedent; this is, after all, USWest.
(Maybe this whole thing has something to do with the takeover, since they
are now QWest.
"Stephen F. Bosch" wrote:
"D. R. Evans" wrote:
If I kill the script-based bit, then I never get to the PAP. BOTH are
necessary, which does seem faintly ridiculous. But perhaps not without
precedent; this is, after all, USWest.
(Maybe this whole thing has something to do with the
Submitted 04-Sep-00 by D. R. Evans:
No. It accepts the script based login just fine. It then changes gears to
PAP.
Most bizaare.
(Maybe this whole thing has something to do with the takeover, since they
are now QWest.
^
That being the case, it may be time to shop for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Found it!!
The geniuses at USWest added PAP authentication after the ordinary logon
script. In other words, you have to go through the old logon sequence and
then do a PAP dance that was never necessary before.
Now why couldn't they have told me
Submitted 04-Sep-00 by D. R. Evans:
The geniuses at USWest added PAP authentication after the ordinary logon
script. In other words, you have to go through the old logon sequence and
then do a PAP dance that was never necessary before.
Now why couldn't they have told me that instead of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4 Sep 00, at 11:35, Anton Graham wrote:
One also wonders what is the point of bothering with PAP, since I've
already sent exactly the same information via the terminal script.
Because it's (apparently) throwing out the script based
Bring up a console window, type man pppd
Maybe set 'crtscts' or 'cdtrcts' or check if it is set wrong
Check the idle variable, mabe it's just timing out?
Not sure how you set up pppd to run, you may not have all the variables
set right.
Hey... this sounds like it could be it -- where are the timer settings, and why
wouldn't it be setting the timer?
-Stephen-
Pierre Fortin wrote:
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
[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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1 Sep 00, at 10:56, Pierre Fortin wrote:
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
-
- 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
: [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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Do this make you want to laugh or to cry?
I am now fairly sure that the fault is indeed with USWest/Qwest/whatever-the-dolts-
want-to-call-themselves-today. I found another entity that runs PPP (a bunsiness,
not an ISP) and I have no trouble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suppose before I give up entirely on the bozos at USWest, I should ask if
anyone else in the Denver area is reading this and uses USWest as their
ISP. If so, please e-mail me privately if you're interested in sharing your
ppp configuration.
My word...
I have been having exactly this same problem, and this is after a whole
month of trouble-free operation... why is the damn thing dropping
connections?
I know this wasn't very helpful, but I want to add my name to the chorus. I
expect to take another stab at this problem later in the
- Original Message -
From: "Stephen Bosch" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 28, 2000 11:23 AM
Subject: Re: [expert] pppd dying unexpectedly
My word...
I have been having exactly this same problem, and this is after a whole
month of trouble-free
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Aug 00, at 12:56, Hoyt wrote:
1. physical installation of modem
wrong serial port, it's a winmodem, setserial config needed, IRQ
conflicts, pnp not set up, linmodem drivers not installed
Nope. Modem works fine. I can talk to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
More info on the still-unsolved ppp problem (in the hope that a light will
flash on over someone's head!):
1. The messages in the /var/log/messages file are completely reproducable.
2. After trying to bring up the link, ifconfig says:
ppp0
Hi, Doc:
3. The command line I'm using (to get rid of One More Variable -- kppp)
looks like this:
pppd connect 'chat -v "" ATDT3034427097 CONNECT "" name: n7dr word:
password goes here' /dev/modem 115200 debug crtscts defaultroute
The above is all on one line, and seems to give exactly
Hullo:
I have been doing some research. In general, ppp problems fall into four
broad areas:
1. physical installation of modem
wrong serial port, it's a winmodem, setserial config needed, IRQ
conflicts, pnp not set up, linmodem drivers not installed
Modem works fine. It's been
On Mon, 28 Aug 2000, Stephen Bosch wrote:
Hi, Doc:
3. The command line I'm using (to get rid of One More Variable -- kppp)
looks like this:
pppd connect 'chat -v "" ATDT3034427097 CONNECT "" name: n7dr word:
password goes here' /dev/modem 115200 debug crtscts defaultroute
The
Quick question about the SIGHUP:
Only root can send signals to root processes, right? So, reboot in
single-user mode, then try pppd. See if it still gets the SIGHUP.
I mean, if there are no other programs, it *should* work, right? There
are no programs ('cept the kernel!) to give it the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29 Aug 00, at 7:50, Andrew George wrote:
Ok Obvious questions
No question is too obvious for me to fail to think of it.
In this case, however:
Did you change anything shortly before it went ga-ga?
No.
have you checked permissions on
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.
--
Anton GrahamGPG ID: 0x18F78541
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
0. Running Mandrake 7.0, with no substantive changes (no kernel builds,
etc.)
1. For months, I have had no kppp/ppp/pppd have seemed to work perfectly.
2. Several days passed when I didn't use them. (They worked fine last
Tuesday; but on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Further to the pppd problem (I swore I'd had enough for today, but of
course, I kept wanting to try One More Thing).
a. I have now installed the very lastest ppp from rpmfind; the same still
happens.
b. The failure occurs regardless of whether I
Hello All,
I am new to this list, running Linux for a couple of years now, and recently
installed LM7
Install went through okay (albeit a bit long), but I experienced problems
with connecting to the internet via kppp. This is the fault report I got:
The remote system is required to authenticate
Fredthere's a thread on this called "Kppp in Air" starting
on Jan 21st. There's a bunch of suggestions for possible
solutions in there to try out. Please let me know if any of
them work as I'm still running 6.1 on my masquerade machine
because of the same problem you're experiencing.
Alan
29 matches
Mail list logo
