PPP problems

Will_Parsons1 · August 19, 2003, 10:18pm

I have just installed QNX 6.2.1NC and am having problems getting PPP to
work. (I had similar problems a year or so ago with 6.1.0 which I was
never able to resolve.) After creating a device for the modem and setting
up the dialer, I see the following:

==========================

Opening device ‘/dev/ser3’
Initializing modem
ATZ

ok
ATM1

ok
Dialing nnn-nnnn
ATDTnnn-nnnn

connect 45333 v42bis
Link Established
Negotiating PPP connection
pppd started
Connection terminated
PPPD connection closed

==========================

I realize this is probably not enough information to diagnose the problem,
but how do I get more information? I have on the same machine installed
Linux, FreeBSD, and Windows XP, and have no problems in the other OS’s
with the settings I used for the QNX dialer.

Also, the ISP apparently uses CHAP authentication.

Xiaodan_Tang1 · August 20, 2003, 2:28am

Starting a terminal, run dialer with -d (phdialer -d), and capture the log
output.

-xtang

Will Parsons <wbp@pcnet.com> wrote in message
news:slrnbk597v.2k5.wbp@isis.thalatta…

I have just installed QNX 6.2.1NC and am having problems getting PPP to
work. (I had similar problems a year or so ago with 6.1.0 which I was
never able to resolve.) After creating a device for the modem and setting
up the dialer, I see the following:

==========================

Opening device ‘/dev/ser3’
Initializing modem
ATZ

ok
ATM1

ok
Dialing nnn-nnnn
ATDTnnn-nnnn

connect 45333 v42bis
Link Established
Negotiating PPP connection
pppd started
Connection terminated
PPPD connection closed

==========================

I realize this is probably not enough information to diagnose the problem,
but how do I get more information? I have on the same machine installed
Linux, FreeBSD, and Windows XP, and have no problems in the other OS’s
with the settings I used for the QNX dialer.

Also, the ISP apparently uses CHAP authentication.

–
±---------------------------------------------------+
| Will Parsons |
| Modified e-mail address: > wbparsons@cshorexyz.com > |
| To reply: delete “xyz” from domain |
±---------------------------------------------------+

Will_Parsons1 · August 20, 2003, 9:27pm

Xiaodan Tang <xtang@qnx.com> wrote:

Starting a terminal, run dialer with -d (phdialer -d), and capture the log
output.

-xtang

Running phdialer -d shows:

PHDIALER spawn: /usr/sbin/pppd /dev/ser3 debug defaultroute +resconf
require-ns noipdefault logstatus nodetach receive-all logfd 2 +stdinsecret
name wbparsons

Will Parsons <> wbp@pcnet.com> > wrote in message
news:> slrnbk597v.2k5.wbp@isis.thalatta> …
I have just installed QNX 6.2.1NC and am having problems getting PPP to
work. (I had similar problems a year or so ago with 6.1.0 which I was
never able to resolve.) After creating a device for the modem and setting
up the dialer, I see the following:

==========================

Opening device ‘/dev/ser3’
Initializing modem
ATZ

ok
ATM1

ok
Dialing nnn-nnnn
ATDTnnn-nnnn

connect 45333 v42bis
Link Established
Negotiating PPP connection
Loading npm-pppmsgr.so <=== additional message with phdialer -d
pppd started
Connection terminated
PPPD connection closed

==========================

I realize this is probably not enough information to diagnose the problem,
but how do I get more information? I have on the same machine installed
Linux, FreeBSD, and Windows XP, and have no problems in the other OS’s
with the settings I used for the QNX dialer.

Also, the ISP apparently uses CHAP authentication.

Will_Parsons1 · August 20, 2003, 9:52pm

Will Parsons <wbp@pcnet.com> wrote:

Xiaodan Tang <> xtang@qnx.com> > wrote:
Starting a terminal, run dialer with -d (phdialer -d), and capture the log
output.

-xtang

Running phdialer -d shows:

PHDIALER spawn: /usr/sbin/pppd /dev/ser3 debug defaultroute +resconf
require-ns noipdefault logstatus nodetach receive-all logfd 2 +stdinsecret
name wbparsons

I figured out that “log output” means output to syslog… (Is there any
particular reason why syslogd isn’t started automatically?) Anyway, here’s
the contents of /var/log/syslog:

===========================================
Aug 20 17:45:58 localhost syslogd: restart
Aug 20 17:46:34 nto pppd[639010-1]: pppd 2.3.11 started by root, uid 0
Aug 20 17:46:34 nto pppd[639010-1]: Status print: PPPD Status: pppd Started
Aug 20 17:46:34 nto pppd[639010-1]: Using interface ppp0
Aug 20 17:46:34 nto pppd[639010-1]: Connect: ppp0 <–> /dev/ser3
Aug 20 17:46:34 nto pppd[639010-1]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xdc9b7296> ]
Aug 20 17:47:01 nto last message repeated 9 times
Aug 20 17:47:04 nto pppd[639010-1]: LCP: timeout sending Config-Requests
Aug 20 17:47:04 nto pppd[639010-1]: Connection terminated.
Aug 20 17:47:04 nto pppd[639010-1]: Status print: PPPD Status: Connection Terminated
Aug 20 17:47:04 nto pppd[639010-1]: Serial link is not 8-bit clean:
Aug 20 17:47:04 nto pppd[639010-1]: All received characters had bit 7 set to 0
Aug 20 17:47:05 nto pppd[639010-1]: Exit.

Will Parsons <> wbp@pcnet.com> > wrote in message
news:> slrnbk597v.2k5.wbp@isis.thalatta> …
I have just installed QNX 6.2.1NC and am having problems getting PPP to
work. (I had similar problems a year or so ago with 6.1.0 which I was
never able to resolve.) After creating a device for the modem and setting
up the dialer, I see the following:

==========================

Opening device ‘/dev/ser3’
Initializing modem
ATZ

ok
ATM1

ok
Dialing nnn-nnnn
ATDTnnn-nnnn

connect 45333 v42bis
Link Established
Negotiating PPP connection
Loading npm-pppmsgr.so <=== additional message with phdialer -d
pppd started
Connection terminated
PPPD connection closed

==========================

I realize this is probably not enough information to diagnose the problem,
but how do I get more information? I have on the same machine installed
Linux, FreeBSD, and Windows XP, and have no problems in the other OS’s
with the settings I used for the QNX dialer.

Also, the ISP apparently uses CHAP authentication.