ppp times out in Linux
William Hanson
dial-up ISP under any version of Linux I tried, and now can not. It
still works under WinXP, but I want the better firewall safety of Linux.
The ISP *says* that they've changed nothing on their end, but I *know*
that nothing changed on mine.
It worked under Mandrake 7.x, 9.1, 10.1, Mandrake move, then Fedora Core
2 (which is what I'm using now on that machine), using either kppp or
wvdial. Now, none of them work; it always times out waiting for the ppp
daemon to start.
Here is the output of the ppp log file, using kppp:
Nov 19 09:56:39 monorail pppd[2828]: pppd 2.4.2 started by root, uid 0
Nov 19 09:56:39 monorail pppd[2828]: using channel 2
Nov 19 09:56:39 monorail pppd[2828]: Using interface ppp0
Nov 19 09:56:39 monorail pppd[2828]: Connect: ppp0 <--> /dev/ttyS0
Nov 19 09:56:39 monorail pppd[2828]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x7f68e1e8> <pcomp> <accomp>]
Nov 19 09:57:06 monorail last message repeated 9 times
Nov 19 09:57:09 monorail pppd[2828]: Terminating on signal 15.
Nov 19 09:57:09 monorail pppd[2828]: sent [LCP TermReq id=0x2 "User
request"]
Nov 19 09:57:12 monorail pppd[2828]: sent [LCP TermReq id=0x3 "User
request"]
Nov 19 09:57:15 monorail pppd[2828]: Connection terminated.
Nov 19 09:57:15 monorail pppd[2828]: Exit.
When I use minicom, the ISP asks for login and password, then sends
multiple lines of gibberish, then times out.
When I use wvdial from the command line, I get:
Using wvdial:
root@monorail will]# wvdial
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT375-2650
--> Waiting for carrier.
ATDT375-2650
CONNECT 26400/ARQ
--> Carrier detected. Waiting for prompt.
[1c] ` [1c] ` `||||`[1c]`[1c]|```
--> Don't know what to do! Starting pppd and hoping for the best.
--> Starting pppd at Fri Nov 18 00:44:11 2005
--> pid of pppd: 2986
--> Disconnecting at Fri Nov 18 00:44:42 2005
--> The PPP daemon has died: PPP negotiation failed (exit code = 10)
--> man pppd explains pppd error codes in more detail.
(I don't usually run as root; this is from when I'm troubleshooting.)
Any suggestions on what to try next?
----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
Moe Trin
In the Usenet newsgroup alt.os.linux, in article
<11324239...@spool6-east.superfeed.net>, William Hanson wrote:
>I have a PC that until fairly recently could hook up to the local
>dial-up ISP under any version of Linux I tried, and now can not.
Old story - what did you change? I know, I know - but I have to ask.
>The ISP *says* that they've changed nothing on their end, but I *know*
>that nothing changed on mine.
OK - one problem I can see is that you are using a poorly configured
tool.
>When I use minicom, the ISP asks for login and password, then sends
>multiple lines of gibberish, then times out.
Does it ask for that in windoze? Well, you can't see it, but I can
assure you that it's HIGHLY unlikely that they are. Virtually every
ISP in the world is configured for windoze - which doesn't look for
some old login prompt. Kill that concept.
>When I use wvdial from the command line, I get:
>--> Sending: ATZ
Do you know that ATZ is setting the modem to a known state? It's resetting
it to what-ever you set in NVRAM - what-ever that might be. See you modem
manual, and use AT&F0 or AT&F1 as appropriate. Most of these ppp helper
programs use something the author saw during a hallucinogenic trip a long
time ago.
>--> Carrier detected. Waiting for prompt.
Edit the wvdial configuration and set Stupid Mode (see the man page)
>[1c] ` [1c] ` `||||`[1c]`[1c]|```
That's not what I'd expect - either you have character set mismatch
or a serial port bit rate mismatch. I'd bet on the character set. This
should look like
~y}#.!}!}!} }8}!}$}%U}"}&} } } } }%}& ...}'}"}(}"} .~~y}
>--> The PPP daemon has died: PPP negotiation failed (exit code = 10)
Error 10 means nothing could be agreed to. Not really informative. What
happens if you try
[compton ~]$ cat /usr/local/bin/dialin
#!/bin/bash
exec /usr/sbin/pppd connect "/usr/sbin/chat -f /etc/ppp/dialscript" \
defaultroute lock noipdefault modem nodetach /dev/modem 115200 crtscts \
user whanson debug logfile /tmp/ppp.log
[compton ~]$
There must not be anything after the \ in those two lines.
[compton ~]$ cat /etc/ppp/dialscript
ABORT BUSY ABORT 'NO CARRIER' "" AT&F0 OK ATDT3752650 CONNECT \d\c
[compton ~]$
This assumes you have /etc/ppp/pap-secrets (or /etc/ppp/chap-secrets as
required by your ISP), and /etc/resolv.conf set up, and that /dev/modem
points to where your modem is hiding. Notice, this is intentionally not
using anything in /etc/ppp/options, so if you have that file at the
moment, temporarily rename it so that it's not used.
Old guy
James Carlson
> --> The PPP daemon has died: PPP negotiation failed (exit code = 10)
> --> man pppd explains pppd error codes in more detail.
10 means that pppd failed to negotiate anything with the peer.
> (I don't usually run as root; this is from when I'm troubleshooting.)
>
> Any suggestions on what to try next?
I'd get rid of kppp and wvdial and just use pppd and chat. Most ease-
of-use tools tend to make things _harder_ to use, at least in my
experience.
The most likely cause of this is a problem with the modem
initialization. I _suspect_ that the modem's bit rate on the DTE side
(the serial port) isn't locked -- though, really, that sort of problem
ought to be extremely rare on modern modems. I don't know why that
might be, but examining your modem's reference manual would be a good
start.
For what it's worth, "AT&F" (or "AT&F1" for USR modems) is a better
way to initialize the modem than "ATZ." The former uses the
known-good factory defaults, while the latter just reads from EEPROM
-- whatever might have been stored there last with "AT&W".
--
James Carlson, KISS Network <james.d...@sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
William Hanson
> Followup Set to comp.protocols.ppp
>
> In the Usenet newsgroup alt.os.linux, in article
> <11324239...@spool6-east.superfeed.net>, William Hanson wrote:
>
>
>>I have a PC that until fairly recently could hook up to the local
>>dial-up ISP under any version of Linux I tried, and now can not.
>
>
> Old story - what did you change? I know, I know - but I have to ask.
Nothing before the system stopped hooking up. Note that the hookup used
to work from live CDs such as Mandrake Move and Damned Small Linux; now
it does not. Not much I can change from a live CD load.
>
>
>>The ISP *says* that they've changed nothing on their end, but I *know*
>>that nothing changed on mine.
>
>
> OK - one problem I can see is that you are using a poorly configured
> tool.
>
Specifics? Do you mean the PC, or the ISP?
>
>>When I use minicom, the ISP asks for login and password, then sends
>>multiple lines of gibberish, then times out.
>
>
> Does it ask for that in windoze? Well, you can't see it, but I can
> assure you that it's HIGHLY unlikely that they are. Virtually every
> ISP in the world is configured for windoze - which doesn't look for
> some old login prompt. Kill that concept.
>
>
>>When I use wvdial from the command line, I get:
>
>
>>--> Sending: ATZ
>
>
> Do you know that ATZ is setting the modem to a known state? It's resetting
> it to what-ever you set in NVRAM - what-ever that might be. See you modem
> manual, and use AT&F0 or AT&F1 as appropriate. Most of these ppp helper
> programs use something the author saw during a hallucinogenic trip a long
> time ago.
>
>
>>--> Carrier detected. Waiting for prompt.
>
>
> Edit the wvdial configuration and set Stupid Mode (see the man page)
>
>
>>[1c] ` [1c] ` `||||`[1c]`[1c]|```
>
>
> That's not what I'd expect - either you have character set mismatch
> or a serial port bit rate mismatch. I'd bet on the character set. This
> should look like
>
> ~y}#.!}!}!} }8}!}$}%U}"}&} } } } }%}& ...}'}"}(}"} .~~y}
OK, that might be worth looking into. What would cause the character
set mismatch?
>
>
>>--> The PPP daemon has died: PPP negotiation failed (exit code = 10)
>
>
> Error 10 means nothing could be agreed to. Not really informative. What
> happens if you try
>
> [compton ~]$ cat /usr/local/bin/dialin
> #!/bin/bash
> exec /usr/sbin/pppd connect "/usr/sbin/chat -f /etc/ppp/dialscript" \
> defaultroute lock noipdefault modem nodetach /dev/modem 115200 crtscts \
> user whanson debug logfile /tmp/ppp.log
> [compton ~]$
>
> There must not be anything after the \ in those two lines.
>
> [compton ~]$ cat /etc/ppp/dialscript
> ABORT BUSY ABORT 'NO CARRIER' "" AT&F0 OK ATDT3752650 CONNECT \d\c
> [compton ~]$
>
> This assumes you have /etc/ppp/pap-secrets (or /etc/ppp/chap-secrets as
> required by your ISP), and /etc/resolv.conf set up, and that /dev/modem
> points to where your modem is hiding. Notice, this is intentionally not
> using anything in /etc/ppp/options, so if you have that file at the
> moment, temporarily rename it so that it's not used.
>
> Old guy
Neither of those files existed before; I created them matching your
post. Then I tried kppp and wvdial. No improvement.
This gets pretty frustrating. No one around here does linux at all (I
live in the sticks), so the only place to troubleshoot is through
newsgroups. That means going online, which is exactly the problem in
linux just now.
William Hanson
Both Moe Trin (ibup...@painkiller.example.tld) and James Carlson
(james.d...@sun.com) questioned the initialization string on the
modem, which I had never looked at in my troubleshooting. It was set to
ATZ, which just told the modem to use the defaults, and had worked
unchanged for ages.
I changed it to AT&F1, and the problem was instantly cured. All the
hours I've spent reading howtos, chasing web pages, booting and
rebooting back and forth to test theories, etc, must have been just
karmic retribution for some unknown offense.
Thanks to the two who pointed out the problem, and to all else who answered!
Moe Trin
<11326034...@spool6-east.superfeed.net>, William Hanson wrote:
>Moe Trin wrote:
>> Old story - what did you change? I know, I know - but I have to ask.
>
>Nothing before the system stopped hooking up. Note that the hookup used
>to work from live CDs such as Mandrake Move and Damned Small Linux; now
>it does not. Not much I can change from a live CD load.
Actually, you can change the hardware - in this case the contents of the
NVRAM on the modem.
>> OK - one problem I can see is that you are using a poorly configured
>> tool.
>Specifics? Do you mean the PC, or the ISP?
Both WvDial and KPPP (like most of the "helper" tools) make some really
bad assumptions about the way hardware works, and the way ISPs have their
terminal servers configured. As you discovered, the modem init strings
leave a lot to be desired (but then, even minicom and seyon come out of
the box with truly bizarre init strings). As far as the way ISPs work,
when microsoft invented the telephone (or what-ever they claimed was new
and innovative in win95), they determined that this Login: prompt thing
was really not going to work - first the DUN tool didn't have the
capabilities to deal with it, and second, the average windoze user's
head was going to explode trying to figure out what to do with a login
prompt. So they invented this new text-less method... that had been
available for three years before then, and forced the ISPs of the world
to convert their setups to that old standard. The manufacturers of
terminal servers have a mode where if the peer dialing in starts sending
ppp frames WITHOUT SENDING ANY TEXT (even so much as a carriage return),
the terminal server auto switches to running ppp. Most ISPs don't bother
disabling the text mode (because windoze never tried that), but they
also did not configure it to work either. It's only been 10 years, so
some programmers haven't heard this relevation yet. That's why I'm so
negative on the helper tools.
>OK, that might be worth looking into. What would cause the character
>set mismatch?
The character set mismatch means the way your computer display shows
those characters. Not everyone is using ASCII (or ISO-8859-1, or...)
and if your system is set to use something other than this, it would
display a different character when presented the bits 01111101.
>Neither of those files existed before; I created them matching your
>post. Then I tried kppp and wvdial. No improvement.
Yeah - they should be looked at as a command line replacement for WvDial
or KPPP. They don't have the pretty icons, but they just do the job of
connecting your computer to your ISP. They're also a bit smaller.
>This gets pretty frustrating. No one around here does linux at all (I
>live in the sticks), so the only place to troubleshoot is through
>newsgroups. That means going online, which is exactly the problem in
>linux just now.
Understood - in fact, your best Linux support is through the newsgroups.
The two nearest computer stores to me apparently have never heard of it,
never mind words like BSD, or UNIX, or even 'ppp'. I also know what you
mean about trying to get help when you can't get on line. I stopped using
windoze in 1992, and had been using *nix at home after that. In 1996, I
changed ISPs. The new one was using this text-less dialin, and I spent a
very frustrating two weeks of a vacation trying to get the stupid things
to connect. The PPP-HOWTO and ISP-HOOKUP-HOWTO of that era were exclusively
a text based login. I got no help from the ISP. Only one person I was able
to contact even knew what I was talking about when I asked about anything,
but he thought they were still using that login prompt thing. Wrong!!!
By the way, did you know that banging your head against the wall burns
250 calories per hour?
Old guy
Clifford Kite
> William Hanson <wha...@mwt.net> writes:
>> --> The PPP daemon has died: PPP negotiation failed (exit code = 10)
>> --> man pppd explains pppd error codes in more detail.
> 10 means that pppd failed to negotiate anything with the peer.
>> (I don't usually run as root; this is from when I'm troubleshooting.)
>>
>> Any suggestions on what to try next?
> I'd get rid of kppp and wvdial and just use pppd and chat. Most ease-
> of-use tools tend to make things _harder_ to use, at least in my
> experience.
Absolutely! When such frontends work everything is fine, but when
they don't work they are almost always harder to debug. Sometimes
it may not even be possible to find a configuration that works.
Below is a simple shell script using pppd with chat which should be
easily utilized and/or modified to suit your needs. It generates the
verbose chat and PPP negotiation messages, and has a high probability
of working without modification. It may well contain more options
than you need but that won't matter. But, as James Carlson pointed
out, with a USR modem you likely need to substitute AT\&F1 for AT\&F .
---Begin connection script---
#! /bin/sh
# Run pppd as root - chmod 1744 /usr/sbin/pppd, or be root and run it.
# Two command line options are required, your ISP username followed
# by the ISP dialup number. Addition pppd options may also follow the
# ISP dialup number on the script command line. An example in which
# this script is named "dialup-myisp":
# dialup-myisp bubba 314-1593 [other pppd options]
echo $1
export USERNAME=$1;shift
echo $USERNAME
echo $1
export NUMBER=$1;shift
echo $NUMBER
/usr/sbin/pppd connect '/usr/sbin/chat -vs "" ATZ OK AT\&F \
OK ATM0W1\&D1%E1s95=47 OK ATDT$NUMBER ABORT BUSY ABORT "NO DIALTONE" \
TIMEOUT 60 CONNECT \\d\\c' /dev/ttyS1 115200 crtscts modem noccp nomp \
noendpoint updetach lock noipdefault asyncmap a0000 debug \
user $USERNAME $*
---End script---
To have the chat/pppd messages sent to one log file add the line
daemon.*;local2.* /var/log/ppp.log
to /etc/syslog.conf and do "killall -HUP syslogd" so syslogd will
reread that file. Then try to make a connection and take a look
at the messages in the ppp.log file. Post the messages if you need
them translated.
--
Clifford Kite Email: "echo xvgr_yv...@ri1.arg|rot13"
/* For every credibility gap, there is a gullibility fill.
-- R. Clopton */
Unruh
>>Moe Trin wrote:
When you get online with whatever (windows?) you could try downloading and
printing out
www.theory.physics.ubc.ca/ppp-linux.html
which is a step by step guide to debugging a ppp connection. It guides you
through setting up a text/chat based ppp session. After you get that
working you can always apply what you learned to kppp or wvdial. In the
case of wvdial there is a StupidMode which you could try switching on.
(That as the old guy says, tells wvdial not to try making a login prompt.
It really means" the writers of wvdial were stupid, and this mode reveals
that-- sorry about the bitterness but I have seen too many posters having
gone to hell and back just because wvdial assumed that everyone wants to
use login mode.
>By the way, did you know that banging your head against the wall burns
>250 calories per hour?
Much more than that. After doing it for an hour, your skin and skull are so
damaged that it takes at least 10,000 calories to fix, never mind the food
you do not eat while you are in a coma.
> Old guy
William Hanson
>
> When you get online with whatever (windows?) you could try downloading and
> printing out
> www.theory.physics.ubc.ca/ppp-linux.html
> which is a step by step guide to debugging a ppp connection. It guides you
> through setting up a text/chat based ppp session. After you get that
> working you can always apply what you learned to kppp or wvdial. In the
> case of wvdial there is a StupidMode which you could try switching on.
> (That as the old guy says, tells wvdial not to try making a login prompt.
> It really means" the writers of wvdial were stupid, and this mode reveals
> that-- sorry about the bitterness but I have seen too many posters having
> gone to hell and back just because wvdial assumed that everyone wants to
> use login mode.
>
I was working through that, but getting nowhere because I was chasing
the wrong problem. At some point I had done something to reset the
modem, so it was not initializing properly. It's online now, thanks!
Unruh
>>
>>
>> When you get online with whatever (windows?) you could try downloading and
>> printing out
>> www.theory.physics.ubc.ca/ppp-linux.html
>> which is a step by step guide to debugging a ppp connection. It guides you
>> through setting up a text/chat based ppp session. After you get that
>> working you can always apply what you learned to kppp or wvdial. In the
>> case of wvdial there is a StupidMode which you could try switching on.
>> (That as the old guy says, tells wvdial not to try making a login prompt.
>> It really means" the writers of wvdial were stupid, and this mode reveals
>> that-- sorry about the bitterness but I have seen too many posters having
>> gone to hell and back just because wvdial assumed that everyone wants to
>> use login mode.
>>
>I was working through that, but getting nowhere because I was chasing
>the wrong problem. At some point I had done something to reset the
>modem, so it was not initializing properly. It's online now, thanks!
Great. Actually one of the lines in there says that you should not use ATZ
to set your modem, but use AT&F (or F1 for Sportster modems), but it is
good that you solved the problem.
Donnie
"William Hanson" <wha...@mwt.net> wrote in message
news:11324235...@spool6-east.superfeed.net...
> I have a PC that until fairly recently could hook up to the local
> dial-up ISP under any version of Linux I tried, and now can not. It
> still works under WinXP, but I want the better firewall safety of Linux.
> The ISP *says* that they've changed nothing on their end, but I *know*
> that nothing changed on mine.
>
I used to run KDE and dial from kppp. It was a lot easier and it usually
worked.
donnie.