pppd doesn't accept connection

[m***@thales-is.com]

I am having problems setting up pppd on a RHEL4 Linux box, using an
old WinNT client that works OK to our old system (Digital Unix)
The Windows client dials using Dial-Up Networking via modem at 57600
bps, the modem on Linux box answers the call at 57600 (checked using
Hyperterminal at the client to see the CONNECT 57600 message), but
then client then fails to connect - it times out at the "Verifying
username and password" stage.
pppd debug at the server shows nothing during the whole dial-in.
The server modem is connected via a usb-serial connector.

Now the details at the server:
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"
(based on similar options used in Digital Unix)

/etc/ppp/options contains:
asyncmap 200a0000
escape 7e,7f,fe,ff,93
mru 296
crtscts
defaultroute
silent
ipcp-accept-remote
modem
proxyarp

I have tried without "require-pap", and also tried with "noauth".
pap-secrets currently contains three asterisks while I try and get
this working, I have also tried three asterisks and an expected IP
address, and four asterisks.

When pppd starts, the debug output is:
Using channel 21
Using interface ppp0
Connect: ppp0 <--> /dev/usb-rear-upper

but then nothing more as the client tries to connect.

Anyone help please?!
Mark

[Doug Mitton]

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box, using an
old WinNT client that works OK to our old system (Digital Unix)
The Windows client dials using Dial-Up Networking via modem at 57600
bps, the modem on Linux box answers the call at 57600 (checked using
Hyperterminal at the client to see the CONNECT 57600 message), but
then client then fails to connect - it times out at the "Verifying
username and password" stage.
pppd debug at the server shows nothing during the whole dial-in.
The server modem is connected via a usb-serial connector.
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"
(based on similar options used in Digital Unix)
asyncmap 200a0000
escape 7e,7f,fe,ff,93
mru 296
crtscts
defaultroute
silent
ipcp-accept-remote
modem
proxyarp
I have tried without "require-pap", and also tried with "noauth".
pap-secrets currently contains three asterisks while I try and get
this working, I have also tried three asterisks and an expected IP
address, and four asterisks.
Using channel 21
Using interface ppp0
Connect: ppp0 <--> /dev/usb-rear-upper
but then nothing more as the client tries to connect.
Anyone help please?!
Mark

I'm not sure how many response you will get to this BUT I have it set
up and here are some "gotchas"!

In my experience, pppd doesn't monitor the modem itself. I had to
install mgetty and configure that to accept a terminal session itself
or pass on a PPP connection request to pppd.

Also, if you already use pppd to connect to your ISP be prepared to
edit the ip-up.local and ip-down.local scripts to allow multiple ppp
connections to co-exist. By default my dial-up ppp request was
causing my ISP ppp connection to terminate and replacing it with the
dialup session. Not really what I wanted.

Thats about all I can think of right now BUT when you get to the point
that you can either login from a dial-up terminal prompt or actually
get ppp dial-up debug information to be displayed then ask more
questions and we can work from there.

Good luck! I find it very convenient to run my own ppp dial-up
service.

[m***@thales-is.com]

Post by Doug Mitton

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box, using an
old WinNT client that works OK to our old system (Digital Unix)
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"
(based on similar options used in Digital Unix)

In my experience, pppd doesn't monitor the modem itself. I had to
install mgetty and configure that to accept a terminal session itself
or pass on a PPP connection request to pppd.

Could you expand on that please?
I can run mgetty (without running pppd) and dial-in using Hypterminal
from the Windows client to get a login session, but do I need both
mgetty and pppd running at the server? I thought pppd deals with the
login process itself?

(You imply either use mgetty to accept session or a second method
passing connection to pppd?)

Mark

[Doug Mitton]

Post by m***@thales-is.com

Post by Doug Mitton

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box, using an
old WinNT client that works OK to our old system (Digital Unix)
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"
(based on similar options used in Digital Unix)

In my experience, pppd doesn't monitor the modem itself. I had to
install mgetty and configure that to accept a terminal session itself
or pass on a PPP connection request to pppd.

Could you expand on that please?
I can run mgetty (without running pppd) and dial-in using Hypterminal
from the Windows client to get a login session, but do I need both
mgetty and pppd running at the server? I thought pppd deals with the
login process itself?
(You imply either use mgetty to accept session or a second method
passing connection to pppd?)
Mark

In my case ... and I don't remember where I found the original
instructions, mgetty looks after the actual modem and then either
allows a terminal access or, if it sees ppp data starts running pppd
itself. I use pppd for my dsl connection so I always have it running
BUT I don't believe thats necessary.

With only mgetty running and properly configured I can access my
system as a dial-up terminal session or as a ppp session.

The applicable configuration appears to be in
/etc/mgetty/login.config:

/AutoPPP/ - - /usr/sbin/pppd nodefaultroute auth -chap +pap
192.168.10.1:192.168.10.253 ms-dns 192.168.10.1
(It looks like it wrapped.)

(I use this line so that I can give any dialup ppp client a specific
IP address and control the configuration in /etc/ppp/ip-up.local.
This is just the way I chose to do it.)

Good luck!

[m***@thales-is.com]

Post by Doug Mitton

Post by Doug Mitton

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box,
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"

In my experience, pppd doesn't monitor the modem itself. I had to
install mgetty and configure that to accept a terminal session itself

The applicable configuration appears to be in
/AutoPPP/ - - /usr/sbin/pppd nodefaultroute auth -chap +pap
192.168.10.1:192.168.10.253 ms-dns 192.168.10.1

Ah, a life-saver!
Yes, I've put my pppd line into login.config and it works fine!
(Shame the pppd man-page didn't mention this)

My only problem is that if I disconnect the ppp connection from the
Windows client, the phone hangs up, but pppd does not notice (i.e.
pppd does not die, mgetty does not respawn, further dial-ins not
possible). If I kill pppd manually, mgetty respawns and all is ready
for next time.
Do I need to use other pppd options? Should I remove the "nodetach"?

TIA
Mark

[Clifford Kite]

Post by m***@thales-is.com
My only problem is that if I disconnect the ppp connection from the
Windows client, the phone hangs up, but pppd does not notice (i.e.
pppd does not die, mgetty does not respawn, further dial-ins not
possible). If I kill pppd manually, mgetty respawns and all is ready
for next time.
Do I need to use other pppd options? Should I remove the "nodetach"?

No, and yes. It's almost certainly a lock file problem although your
original post didn't have lock as a pppd option. Until pppd removes
it's lock file (upon exiting) mgetty won't respawn.

[m***@thales-is.com]

Post by Clifford Kite

Post by m***@thales-is.com
My only problem is that if I disconnect the ppp connection from the
Windows client, the phone hangs up, but pppd does not notice (i.e.
pppd does not die, mgetty does not respawn,
Do I need to use other pppd options? Should I remove the "nodetach"?

No, and yes. It's almost certainly a lock file problem although your
original post didn't have lock as a pppd option.

I have now tried removing "nodetach", and also using "lock" option -
no better.
The pppd does not die.
At the point when the Dial-Up Networking on the Windows Client
disconnects, the phone line disconnects, but I see no output in either
ppp debug file or mgetty debug.
I did turn on the pppd "record" option, which does generate further
output when the phone line disconnects, here viewed with "od -c":

0004720 ... 005 \0 \0 001 n 002 \0
0004740 006 \r \n N O C 002 \0 \b A R R I
E R
0004760 \r \n

How can I get pppd to recognise the connection has been dropped?

Mark

[Clifford Kite]

Post by m***@thales-is.com

Post by Clifford Kite

Post by m***@thales-is.com
My only problem is that if I disconnect the ppp connection from the
Windows client, the phone hangs up, but pppd does not notice (i.e.
pppd does not die, mgetty does not respawn,
Do I need to use other pppd options? Should I remove the "nodetach"?

No, and yes. It's almost certainly a lock file problem although your
original post didn't have lock as a pppd option.

Saved by "almost" - again. :)

Post by m***@thales-is.com
I have now tried removing "nodetach", and also using "lock" option -
no better.
The pppd does not die.
At the point when the Dial-Up Networking on the Windows Client
disconnects, the phone line disconnects, but I see no output in either
ppp debug file or mgetty debug.

At one point you said "I've put my pppd line into login.config" and if
that is the line "pppd debug nodetach require-pap ttyUSB0 57600" in the
original post then the problem may have to do with specifying ttyUSB0
and 57600. With pppd using chat that's correct but with not with mgetty.
You specify the serial port and speed for mgetty and mgetty passes them
on to pppd.

The inittab line might be something like

d1:3:respawn:/usr/local/sbin/mgetty -D -s 57600 -m '"" AT\&F1 OK \c' ttyUSB0

with lines such as

answer-chat "" ATA CONNECT \c
answer-chat-timeout 45

in mgetty.config for answering the call-in.

Regards-

[James Carlson]

Post by m***@thales-is.com
I did turn on the pppd "record" option, which does generate further
0004720 ... 005 \0 \0 001 n 002 \0
0004740 006 \r \n N O C 002 \0 \b A R R I
E R
0004760 \r \n

I don't see any PPP traffic there.

Post by m***@thales-is.com
How can I get pppd to recognise the connection has been dropped?

The modem should be configured to drop DCD when the connection drops
(AT&C2, I think).

[Doug Mitton]

Post by m***@thales-is.com

Post by Doug Mitton

Post by Doug Mitton

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box,
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"

In my experience, pppd doesn't monitor the modem itself. I had to
install mgetty and configure that to accept a terminal session itself

The applicable configuration appears to be in
/AutoPPP/ - - /usr/sbin/pppd nodefaultroute auth -chap +pap
192.168.10.1:192.168.10.253 ms-dns 192.168.10.1

Ah, a life-saver!
Yes, I've put my pppd line into login.config and it works fine!
(Shame the pppd man-page didn't mention this)
My only problem is that if I disconnect the ppp connection from the
Windows client, the phone hangs up, but pppd does not notice (i.e.
pppd does not die, mgetty does not respawn, further dial-ins not
possible). If I kill pppd manually, mgetty respawns and all is ready
for next time.
Do I need to use other pppd options? Should I remove the "nodetach"?
TIA
Mark

Have you had any luck resolving this?

I use a minimat /etc/ppp/options file and I don't use nodetach at all.

I haven't seen this problem myself. Maybe a search of the log files
... if you activate a higher debugging level in mgetty and pppd.

I like this mgetty option as I can either log into a console prompt OR
use ppp ... my choice.

Good luck!

[m***@thales-is.com]

Post by m***@thales-is.com
if I disconnect the ppp connection from the

Post by m***@thales-is.com
Windows client, the phone hangs up, but pppd does not notice

Have you had any luck resolving this?
Maybe a search of the log files ... if you activate a higher debugging level in mgetty and pppd.

No joy yet, see my other post listing output using pppd's "record"
option; can't get pppd to die when it sees the disconnection.

Mark

[Clifford Kite]

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box, using an
old WinNT client that works OK to our old system (Digital Unix)
The Windows client dials using Dial-Up Networking via modem at 57600
bps, the modem on Linux box answers the call at 57600 (checked using
Hyperterminal at the client to see the CONNECT 57600 message), but
then client then fails to connect - it times out at the "Verifying
username and password" stage.
pppd debug at the server shows nothing during the whole dial-in.
The server modem is connected via a usb-serial connector.
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"
(based on similar options used in Digital Unix)
asyncmap 200a0000
escape 7e,7f,fe,ff,93
mru 296
crtscts
defaultroute
silent
ipcp-accept-remote
modem
proxyarp
I have tried without "require-pap", and also tried with "noauth".
pap-secrets currently contains three asterisks while I try and get
this working, I have also tried three asterisks and an expected IP
address, and four asterisks.
Using channel 21
Using interface ppp0
Connect: ppp0 <--> /dev/usb-rear-upper
but then nothing more as the client tries to connect.

I don't see chat anywhere. Try adding the pppd option

connect 'chat CONNECT \\d\\c'
or maybe for the windows client
connect 'chat CONNECT \\d\\c CLIENT CLIENTSERVER\\c'

Post by m***@thales-is.com
Anyone help please?!
Mark

Regards-

[m***@thales-is.com]

Post by Clifford Kite

I am having problems setting up pppd on a RHEL4 Linux box...
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"

I don't see chat anywhere. Try adding the pppd option
connect 'chat CONNECT \\d\\c'

I tried that, and I'm still not connecting. I see errors "Connect
script failed" - can you give a few more ideas?
(I have looked in man page etc, but seem more geared to outgoing
connect scripts. On Digital Unix I didn't need anything so it's new
to me)

Thanks
Mark

[Clifford Kite]

Post by m***@thales-is.com

Post by Clifford Kite

I am having problems setting up pppd on a RHEL4 Linux box...
I'm running "pppd debug nodetach require-pap ttyUSB0 57600"

I don't see chat anywhere. Try adding the pppd option
connect 'chat CONNECT \\d\\c'

I tried that, and I'm still not connecting. I see errors "Connect
script failed" - can you give a few more ideas?
(I have looked in man page etc, but seem more geared to outgoing
connect scripts. On Digital Unix I didn't need anything so it's new
to me)

Right, and what I suggested failed because my thinking was "outgoing."
The modem must first be put in the answer mode with ATATA and even then
chat would timeout in about 45 seconds. As the other responder has
suggested mgetty appears to be your best option.

[Clifford Kite]

Post by Clifford Kite
Right, and what I suggested failed because my thinking was "outgoing."
The modem must first be put in the answer mode with ATATA and even then

^^^^^
Arrgghh! That, of course, should be ATA.

Post by Clifford Kite
chat would timeout in about 45 seconds. As the other responder has
suggested mgetty appears to be your best option.

[James Carlson]

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box, using an
old WinNT client that works OK to our old system (Digital Unix)
The Windows client dials using Dial-Up Networking via modem at 57600
bps, the modem on Linux box answers the call at 57600 (checked using
Hyperterminal at the client to see the CONNECT 57600 message), but
then client then fails to connect - it times out at the "Verifying
username and password" stage.
pppd debug at the server shows nothing during the whole dial-in.
The server modem is connected via a usb-serial connector.

This sounds like either a bad USB-serial device or a misconfigured
modem.

Since pppd's debug isn't saying anything, this means that either no
data are getting through, or what is getting through is massively
corrupted and doesn't look at all like PPP.

I'd recommend looking into the serial connection. Two ways to do
that:

- Enable the 'record' option in pppd so that you can see what bytes
pppd thinks it's getting off of the serial line.

- Get pppd out of the picture and try answering the call with
something like miniterm, kermit, or cu. Talk to the modem
directly and see what happens.

At a guess, you need to have something like this in your pppd
configuration:

init "chat '' 'AT&F1'"

Just a guess, though.

Post by m***@thales-is.com
asyncmap 200a0000
escape 7e,7f,fe,ff,93
mru 296
silent

That's a pretty motley set of options. Are you sure those are what
you really need? Something's quite fishy here.

(Why 93 but not 91? Why 7f, fe and ff? Why list 7e at all, as that's
the PPP AHDLC escape character and is _always_ escaped, no matter what
you do? Why include the XON/XOFF characters in the asyncmap when
you're using hardware flow control? Why include the default
/usr/bin/telnet command line escape character?)

[m***@thales-is.com]

Post by James Carlson

Post by m***@thales-is.com
I am having problems setting up pppd on a RHEL4 Linux box

- Enable the 'record' option in pppd so that you can see what bytes
pppd thinks it's getting off of the serial line.

Right, I hadn't noticed that option.

Post by James Carlson
- Get pppd out of the picture and try answering the call with
something like miniterm, kermit, or cu.

Done that, seems OK.

Post by James Carlson
At a guess, you need to have something like this in your pppd
init "chat '' 'AT&F1'"

OK, might try that, although I have now got pppd running via mgetty as
in another post. Whether there are any disadvantages to doing it that
way I don't know yet.

Post by James Carlson

Post by m***@thales-is.com
asyncmap 200a0000
escape 7e,7f,fe,ff,93
mru 296
silent

That's a pretty motley set of options. Are you sure those are what
you really need? Something's quite fishy here.

They're actually the default options from /etc/ppp/config in Digital
Unix (where I'm porting my system from), but I take your points -
thanks (I was actually hoping you would reply, based on your previous
input to the newsgroup; I value your input)

Thanks
Mark

[James Carlson]

Post by m***@thales-is.com

Post by James Carlson
At a guess, you need to have something like this in your pppd
init "chat '' 'AT&F1'"

OK, might try that, although I have now got pppd running via mgetty as
in another post. Whether there are any disadvantages to doing it that
way I don't know yet.

No disadvantages -- you just need to set up mgetty properly.

[Unruh]

Post by James Carlson

Post by m***@thales-is.com

Post by James Carlson
At a guess, you need to have something like this in your pppd
init "chat '' 'AT&F1'"

OK, might try that, although I have now got pppd running via mgetty as
in another post. Whether there are any disadvantages to doing it that
way I don't know yet.

mgetty is for people calling in. chat is for you calling out in general.
mgetty has lines in /etc/mgetty*/mgetty.config for you to put in an input
string to be sent to your modem when it starts up. The above may well be
appropriate to place into the string. (I assume you have a USR Sportster
modem since they are the ones that use AT&F1. Most others have their
hardware default flow control be as AT&F

Post by James Carlson
No disadvantages -- you just need to set up mgetty properly.
--
Sun Microsystems / 1 Network Drive 71.232W Vox [phone]
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax [phone]