ppp problems

QNX Newsgroups (Archives) qdn.public.qnxrtp.installation
1

I am running into problems getting a PPP dial-up connexion established with
Dialer under QNX 6.1.0. The modem dials out and connects to the ISP, but
then fails with the following messages:

Serial line is not 8-bit clean:
All received characters had bit 7 set to 0.

I have an older version of QNX RTP (Patch B) installed on another computer,
and PPP works fine. As far as I can tell, the Dialer is configured virtually
the same on both systems (PAP/CHAP Login), with the exception that the
serial port is /dev/ser4 in the working system and /dev/ser3 in the non-
working system. (/dev/ser3 is created with the command:
devc-ser8250 -u1 3f8,4 -u2 2f8,3 -u3 c000,9 in rc.local.)

Any hints would be much appreciated.

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

2

Hello Will,

There is a fixed pppd found at http://developers.qnx.com in the fixes
section. Give this a try and see if it solves your problem.

Regards,
Dave B.



Will Parsons wrote:

I am running into problems getting a PPP dial-up connexion established with
Dialer under QNX 6.1.0. The modem dials out and connects to the ISP, but
then fails with the following messages:

Serial line is not 8-bit clean:
All received characters had bit 7 set to 0.

I have an older version of QNX RTP (Patch B) installed on another computer,
and PPP works fine. As far as I can tell, the Dialer is configured virtually
the same on both systems (PAP/CHAP Login), with the exception that the
serial port is /dev/ser4 in the working system and /dev/ser3 in the non-
working system. (/dev/ser3 is created with the command:
devc-ser8250 -u1 3f8,4 -u2 2f8,3 -u3 c000,9 in rc.local.)

Any hints would be much appreciated.

3

apps <apps@qnx.com> wrote:

Hello Will,

There is a fixed pppd found at > http://developers.qnx.com > in the fixes
section. Give this a try and see if it solves your problem.

Regards,
Dave B.

Unfortunately, no, though it changes the symptoms. The modem connects to
the ISP, I see the messages “Negotiating PPP connection” and “pppd Started”,
then after a pause:

Connection terminated

PPPD connection closed


Will Parsons wrote:

I am running into problems getting a PPP dial-up connexion established with
Dialer under QNX 6.1.0. The modem dials out and connects to the ISP, but
then fails with the following messages:

Serial line is not 8-bit clean:
All received characters had bit 7 set to 0.

I have an older version of QNX RTP (Patch B) installed on another computer,
and PPP works fine. As far as I can tell, the Dialer is configured virtually
the same on both systems (PAP/CHAP Login), with the exception that the
serial port is /dev/ser4 in the working system and /dev/ser3 in the non-
working system. (/dev/ser3 is created with the command:
devc-ser8250 -u1 3f8,4 -u2 2f8,3 -u3 c000,9 in rc.local.)

Any hints would be much appreciated.

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

4

The orginal error “serial line is not 8-bit clean” usually indicates an
authentication error. pppd sends LCP (link control protocol) packets to the
other side - if they are reflected (either because pppd isn’t started on the
otherside or your login script has failed to authenticate you) with the 8th
bit stripped off (ASCII is 7bits)

Try turning on the terminal screen, so you can see what is being
communicated across. Also have syslogd running, and check it’s logs.

–
Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Will Parsons” <wbp@pcnet.deletethis.com> wrote in message
news:slrna518g6.2v8.wbp@aigialos.thalatta…

apps <> apps@qnx.com> > wrote:
Hello Will,

There is a fixed pppd found at > http://developers.qnx.com > in the fixes
section. Give this a try and see if it solves your problem.

Regards,
Dave B.


Unfortunately, no, though it changes the symptoms. The modem connects to
the ISP, I see the messages “Negotiating PPP connection” and “pppd
Started”,
then after a pause:

Connection terminated

PPPD connection closed



Will Parsons wrote:

I am running into problems getting a PPP dial-up connexion established
with
Dialer under QNX 6.1.0. The modem dials out and connects to the ISP,
but
then fails with the following messages:

Serial line is not 8-bit clean:
All received characters had bit 7 set to 0.

I have an older version of QNX RTP (Patch B) installed on another
computer,
and PPP works fine. As far as I can tell, the Dialer is configured
virtually
the same on both systems (PAP/CHAP Login), with the exception that the
serial port is /dev/ser4 in the working system and /dev/ser3 in the
non-
working system. (/dev/ser3 is created with the command:
devc-ser8250 -u1 3f8,4 -u2 2f8,3 -u3 c000,9 in rc.local.)

Any hints would be much appreciated.

\

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

5

Adam Mallory <amallory@qnx.com> wrote:

The orginal error “serial line is not 8-bit clean” usually indicates an
authentication error. pppd sends LCP (link control protocol) packets to the
other side - if they are reflected (either because pppd isn’t started on the
otherside or your login script has failed to authenticate you) with the 8th
bit stripped off (ASCII is 7bits)

Try turning on the terminal screen, so you can see what is being
communicated across. Also have syslogd running, and check it’s logs.

I not sure what you mean by “turning on the terminal screen”. Is it something
other than the log window? I have started phdialer in a pterm with the -d
option, but it doesn’t give me any indication of what is being communicated.

As far as syslogd, it doesn’t seem to exist either on the disk or (as far as I
can tell) on the repository on the installation CD.

“Will Parsons” <> wbp@pcnet.deletethis.com> > wrote in message
news:> slrna518g6.2v8.wbp@aigialos.thalatta> …
apps <> apps@qnx.com> > wrote:
Hello Will,

There is a fixed pppd found at > http://developers.qnx.com > in the fixes
section. Give this a try and see if it solves your problem.

Regards,
Dave B.


Unfortunately, no, though it changes the symptoms. The modem connects to
the ISP, I see the messages “Negotiating PPP connection” and “pppd
Started”,
then after a pause:

Connection terminated

PPPD connection closed



Will Parsons wrote:

I am running into problems getting a PPP dial-up connexion established
with
Dialer under QNX 6.1.0. The modem dials out and connects to the ISP,
but
then fails with the following messages:

Serial line is not 8-bit clean:
All received characters had bit 7 set to 0.

I have an older version of QNX RTP (Patch B) installed on another
computer,
and PPP works fine. As far as I can tell, the Dialer is configured>virtually
the same on both systems (PAP/CHAP Login), with the exception that the
serial port is /dev/ser4 in the working system and /dev/ser3 in the
non-
working system. (/dev/ser3 is created with the command:
devc-ser8250 -u1 3f8,4 -u2 2f8,3 -u3 c000,9 in rc.local.)

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

6

“Will Parsons” <wbp@pcnet.deletethis.com> wrote in message
news:slrna546ad.71s.wbp@aigialos.thalatta…

Adam Mallory <> amallory@qnx.com> > wrote:
The orginal error “serial line is not 8-bit clean” usually indicates an
authentication error. pppd sends LCP (link control protocol) packets to
the
other side - if they are reflected (either because pppd isn’t started on
the
otherside or your login script has failed to authenticate you) with the
8th
bit stripped off (ASCII is 7bits)

Try turning on the terminal screen, so you can see what is being
communicated across. Also have syslogd running, and check it’s logs.

I not sure what you mean by “turning on the terminal screen”. Is it
something
other than the log window? I have started phdialer in a pterm with the -d
option, but it doesn’t give me any indication of what is being
communicated.

There is an option in the Dialer to “Show Terminal”

As far as syslogd, it doesn’t seem to exist either on the disk or (as far
as I
can tell) on the repository on the installation CD.

That’s strange, it should be located as /usr/sbin/syslogd, and is part of
the core OS package.

–
Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

7

Adam Mallory <amallory@qnx.com> wrote:

“Will Parsons” <> wbp@pcnet.deletethis.com> > wrote in message
news:> slrna546ad.71s.wbp@aigialos.thalatta> …
Adam Mallory <> amallory@qnx.com> > wrote:
The orginal error “serial line is not 8-bit clean” usually indicates an
authentication error. pppd sends LCP (link control protocol) packets to
the
other side - if they are reflected (either because pppd isn’t started on
the
otherside or your login script has failed to authenticate you) with the
8th
bit stripped off (ASCII is 7bits)

Try turning on the terminal screen, so you can see what is being
communicated across. Also have syslogd running, and check it’s logs.

I not sure what you mean by “turning on the terminal screen”. Is it
something
other than the log window? I have started phdialer in a pterm with the -d
option, but it doesn’t give me any indication of what is being
communicated.

There is an option in the Dialer to “Show Terminal”

OK - I had already done this, but it just gives me the errors I mentioned
in the original post.

As far as syslogd, it doesn’t seem to exist either on the disk or (as far
as I
can tell) on the repository on the installation CD.

That’s strange, it should be located as /usr/sbin/syslogd, and is part of
the core OS package.

And so it is. (I must have hallucinated I had already looked there.)

So, I have added /usr/sbin/syslogd to rc.local, created /var/log/syslog,
and started phdialer with the -d option. The terminal window still gives
me the same unhelpful messages; the logfile shows:

Connect: ppp0 <-> /dev/ser3
sent [LCP ConfigReq id=0x1 <asyncmap 0x0> <magic 0x2b0933aa> ]
last message repeated 9 times
LCP: timeout sending Config-Requests
Connection terminated.
Serial link is not 8-bit clean: &c.

I don’t see where the remote side is making an authorization request.

When I try the same thing on another computer running 6.0 patch B:

  1. I can see the extensive messages between pppd and the remote side in
    both the terminal window and the log file.

  2. Both in the terminal window and the log file I can see the remote
    side requesting PAP authorization and pppd sending user name and password.

  3. Successful connexion.

(Note: I have retyped the password several times to make sure I didn’t
mis-type it.)

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