Dialup troubleshooting

Hello all,

It seems that many are having difficulty connecting and staying
connected using a modem. It appears as though there are two seperate
problems.

  1. As far as connecting is concerned, it looks like pppd isn’t
    authenticating properly. The pppd shipped with RtP should support both
    PAP and CHAP. The online docs appear to be out of date in this regard.
    When in doubt, refer to the docs distributed with the release.

  2. The second phenomenon is the connection breaking prematurely.

Some people have complained that the dialer keeps trying to dial even
when they close it. This is the autoconnect feature: when any
application tries to connect to a site, the resolver will execute a
script which in turns lauches dialer. Whats happening here is after you
close dialer, someone - say voyager, attempts to reconnect to a site,
and has it launch again. You can turn this off by checking the
‘disable autoconnect’ option.

If possible we’d like a few people having problems to run dialer -v
and dialer -d (for debug). It will print out the spawn options to stderr
when you connect. It will also launch pppd in debug mode which will have
it print more verbosely in the terminal window. Please post the terminal
output, and the stderr output. (plz post to this thread)

How do I post the output if I can’t connect, you ask? If you have a
linux or windows partition, you can copy the output there, reboot and post
it from the other os.

ex:

phdialer -v > /tmp/phdialer.out

phdialer -d >> /tmp/phdialer.out

{ try to connect, copy contents from terminal, exit }

ped /tmp/phdialer.out

{ paste }

cp /tmp/phdialer.out /fs/hd1-dos/phdialer.out

Note: check the output for any sensitive info before you post it
(username, phonenum).


Shaun Sauve
QNX Software Systems

Hello, thanks for your help, here what you ask for:

[ ># phdialer -v > /tmp/phdialer.out ]
phdialer v0.9. [Compiled Sep 8 2000 14:08:56]

  • dialup path: /root/.ph/dialups

[ ># phdialer -d >> /tmp/phdialer.out ]
Opening device ‘/dev/ser1’
Initializing modem
ATZ

ok
ATM0

ok
AT&F

ok
Dialing 0141743500…
ATDT0141743500

connect 44000/arq
Link Established
Negotiating PPP connection
pppd[565282-1]: pppd 2.3.5 started by root, uid 0
pppd Started
pppd[565282-1]: Using interface ppp0
pppd[565282-1]: Connect: ppp0 <–> /dev/ser1
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: sent [LCP ConfReq id=0x1 <magic 0xfe81369c>
]
pppd[565282-1]: LCP: timeout sending Config-Requests
pppd[565282-1]: Connection terminated.
Connection Terminated
PPPD connection closed

So…whats wrong with my config ?

Best regards

Jeff PALOS

Shaun Sauve wrote:

If possible we’d like a few people having problems to run dialer -v
and dialer -d (for debug). It will print out the spawn options to stderr
when you connect. It will also launch pppd in debug mode which will have
it print more verbosely in the terminal window. Please post the terminal
output, and the stderr output. (plz post to this thread)

Ok, this is what happens:


phdialer v0.9. [Compiled Sep 8 2000 14:08:56]

  • dialup path: /root/.ph/dialups
    PHDIALER spawn: pppd /dev/ser2 115200 debug defaultroute +resconf
    require-ns noipdefault nodetach
    +stderrlog +stdinsecret name ***** nameserver 194.20.24.2 nameserver
    194.20.24.1

Sep 29 09:46:58 nto pppd[647203-1]: pppd 2.3.5 started by root, uid 0
Sep 29 09:46:58 nto pppd[647203-1]: Using interface ppp0
Sep 29 09:46:58 nto pppd[647203-1]: Connect: ppp0 <–> /dev/ser2
Sep 29 09:46:58 nto pppd[647203-1]: sent [LCP ConfReq id=0x1 <magic
0xe07bd15a> ]
Sep 29 09:47:07 nto last message repeated 3 times
Sep 29 09:47:08 nto pppd[647203-1]: Hangup (SIGHUP)
Sep 29 09:47:08 nto pppd[647203-1]: sent [LCP TermReq id=0x2 “User
request”]
Sep 29 09:47:11 nto pppd[647203-1]: sent [LCP TermReq id=0x3 “User
request”]
Sep 29 09:47:14 nto pppd[647203-1]: Connection terminated.
Sep 29 09:47:14 nto pppd[647203-1]: Exit.

And another thing: phdialer says “connect 57600” isnpaite of the fact
that I set 115200…

I hope this is useful.

Regards,
Fabio Alemagna

I initially had the same problem, then I inadvertently set the line speed to
56000 as shown on the phdialer and it worked and connect well with my ISP.
However, I don’t know whether the linespeed is actually the modem speed or
the serial controller speed as it should be something like 115200 as from my
Linuc set up experience as that would allow for higher line rate with data
compression through a 56K modem. It seems that the setting on phdialer is a
bit non-standard such as 56000, 128000, 128000 etc. These are non-standard
linespeed.
I suspect either dev/ser1 is setup differently sompared to Linux and hence
the parameter passed to pppd is non-standard or there is some bug in the
/dev/ser1 driver.
Give it a try and it might work.

“Fabio Alemagna” <falemagn@studenti.unina.it> wrote in message
news:39D44CA3.73AB1729@studenti.unina.it

Shaun Sauve wrote:
If possible we’d like a few people having problems to run dialer -v
and dialer -d (for debug). It will print out the spawn options to stderr
when you connect. It will also launch pppd in debug mode which will have
it print more verbosely in the terminal window. Please post the terminal
output, and the stderr output. (plz post to this thread)

Ok, this is what happens:


phdialer v0.9. [Compiled Sep 8 2000 14:08:56]

  • dialup path: /root/.ph/dialups
    PHDIALER spawn: pppd /dev/ser2 115200 debug defaultroute +resconf
    require-ns noipdefault nodetach
    +stderrlog +stdinsecret name ***** nameserver 194.20.24.2 nameserver
    194.20.24.1

Sep 29 09:46:58 nto pppd[647203-1]: pppd 2.3.5 started by root, uid 0
Sep 29 09:46:58 nto pppd[647203-1]: Using interface ppp0
Sep 29 09:46:58 nto pppd[647203-1]: Connect: ppp0 <–> /dev/ser2
Sep 29 09:46:58 nto pppd[647203-1]: sent [LCP ConfReq id=0x1 <magic
0xe07bd15a> ]
Sep 29 09:47:07 nto last message repeated 3 times
Sep 29 09:47:08 nto pppd[647203-1]: Hangup (SIGHUP)
Sep 29 09:47:08 nto pppd[647203-1]: sent [LCP TermReq id=0x2 “User
request”]
Sep 29 09:47:11 nto pppd[647203-1]: sent [LCP TermReq id=0x3 “User
request”]
Sep 29 09:47:14 nto pppd[647203-1]: Connection terminated.
Sep 29 09:47:14 nto pppd[647203-1]: Exit.

And another thing: phdialer says “connect 57600” isnpaite of the fact
that I set 115200…

I hope this is useful.

Regards,
Fabio Alemagna

Op 28 Sep 2000 16:25:06 GMT, schreef Shaun Sauve <ssauve@qnx.com>:

If possible we’d like a few people having problems to run dialer -v
and dialer -d (for debug). It will print out the spawn options to stderr
when you connect. It will also launch pppd in debug mode which will have
it print more verbosely in the terminal window. Please post the terminal
output, and the stderr output. (plz post to this thread)

Here’s mine,

phdialer v0.9. [Compiled Sep 8 2000 14:08:56]

  • dialup path: /root/.ph/dialups

PHDIALER spawn: pppd /dev/ser2 56000 debug defaultroute +resconf
require-ns noip
default nodetach +stderrlog +stdinsecret name xtuigx idle 7200
nameserver 194.10
9.6.66 nameserver 194.109.9.99

Opening device ‘/dev/ser2’
Initializing modem
ATZ


ok
ATM1

ok
Dialing 0xxx550xxx…
ATDT0xxx550xxx


connect 57600
Link Established
Negotiating PPP connection
pppd[770079-1]: pppd 2.3.5 started by root, uid 0
pppd Started
pppd[770079-1]: Using interface ppp0
pppd[770079-1]: Connect: ppp0 <–> /dev/ser2
pppd[770079-1]: sent [LCP ConfReq id=0x1 <magic 0x633648c>
]
pppd[770079-1]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <magic
0x16fb5c57> ]
pppd[770079-1]: sent [LCP ConfAck id=0x1 <asyncmap 0x0> <magic
0x16fb5c57> ]
pppd[770079-1]: sent [LCP ConfReq id=0x1 <magic 0x633648c>
]
pppd[770079-1]: rcvd [LCP ConfAck id=0x1 <magic 0x633648c>
]
pppd[770079-1]: sent [PAP AuthReq id=0x1 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x1 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0x2 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0x2]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x2 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0x3 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0x3]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x3 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0x4 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0x4]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x4 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0x5 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0x5]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x5 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0x6 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0x6]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x6 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0x7 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x7 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: rcvd [PAP AuthAck id=0x7]
pppd[770079-1]: sent [PAP AuthReq id=0x8 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0x8]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x8 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0x9 user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0x9]
pppd[770079-1]: rcvd [IPCP ConfReq id=0x9 <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: sent [PAP AuthReq id=0xa user=“xtuigx”
password=“passw”]
pppd[770079-1]: rcvd [PAP AuthAck id=0xa]
pppd[770079-1]: rcvd [IPCP ConfReq id=0xa <compress VJ 0f 00> <addr
194.109.6.1>]
pppd[770079-1]: No response to PAP authenticate-requests
pppd[770079-1]: sent [LCP TermReq id=0x2 “Authentication failed”]
authentication failed
pppd[770079-1]: sent [LCP TermReq id=0x3 “Authentication failed”]
pppd[770079-1]: Connection terminated.
PPPD connection closed

/** PhEDIT attribute block
0:3246:default:-3:-3:0
** PhEDIT attribute block ends (-0000096)**/

Hope this helps. I’ve never run Linux on my system so I keep having
the nagging feeling there something i’m forgetting. But because there
is a connection being made and even telnet worked for a minute,(I got
the standard message from my ISP), I am at a loss here,

Amro

\

Killsigg The Hysterian says:

This is a Ferengi tagline. Pay before you read it.

We haven’t been able to reproduce this here. In the meantime try to clear
the ‘line speed’ dialup field in phlip.

We’re trying to get hold of a account on a system that demonstrates the
authentication problem. If anyone can send information regarding an ISP
or freenet that reproduces it, please contact me.


Shaun Sauve
QNX Software Systems

ssauve@qnx.com (Shaun Sauve) wrote in <8qvrd2$9he$2@inn.qnx.com>:

Hello all,

It seems that many are having difficulty connecting and staying
connected using a modem. It appears as though there are two seperate
problems.

  1. As far as connecting is concerned, it looks like pppd isn’t
    authenticating properly. The pppd shipped with RtP should support both
    PAP and CHAP. The online docs appear to be out of date in this regard.
    When in doubt, refer to the docs distributed with the release.

  2. The second phenomenon is the connection breaking prematurely.

Some people have complained that the dialer keeps trying to dial even
when they close it. This is the autoconnect feature: when any
application tries to connect to a site, the resolver will execute a
script which in turns lauches dialer. Whats happening here is after you
close dialer, someone - say voyager, attempts to reconnect to a site,
and has it launch again. You can turn this off by checking the
‘disable autoconnect’ option.

If possible we’d like a few people having problems to run dialer -v
and dialer -d (for debug). It will print out the spawn options to stderr
when you connect. It will also launch pppd in debug mode which will have
it print more verbosely in the terminal window. YOOOO
Thats a problem, espacially when the terminal window is totally blank.