pppd

QNX USERS QNX6 - OS
1

Hi

I’m trying to connect to a windows server via modem. I’m using pppd like this:

pppd debug connect “chat -v -f/etc/conect_modem” chap /dev/ser1 115200 logfile /root/pppd.log

This is what the log shows me:

Serial connection established.
Using interface ppp0
Connect: ppp0 <–> /dev/ser1
Warning - secret file /etc/ppp/pap-secrets has world and/or group access
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6362eb64> ]
rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap 81> <magic 0x73d079d7> <mrru 1614> <endpoint [MAC:00:21:97:ab:da:1c]> < 17 04 00 18>]
sent [LCP ConfRej id=0x0 <auth chap 81> <mrru 1614> < 17 04 00 18>]
rcvd [LCP ConfNak id=0x1 <auth chap 81>]
sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x6362eb64> ]
rcvd [LCP TermReq id=0x1 “s\37777777720y\37777777727\000<\37777777715t\000\000\003\37777777627”]
sent [LCP TermAck id=0x1]
Hangup (SIGHUP)
sent [LCP TermReq id=0x3 “User request”]
sent [LCP TermReq id=0x4 “User request”]
rcvd [LCP TermReq id=0x4 “User request”]
sent [LCP TermAck id=0x4]
rcvd [LCP TermAck id=0x4]
Connection terminated.

I don’t know why is terminated. :frowning:

Thanks

2

Manueloid,

It looks to me that the Microsoft server has callback CBCP enabled on it (in other words it expect you to call in and then it calls you back to actually complete the connection and allow access) based on this inital reply:

rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap 81> <magic 0x73d079d7> <mrru 1614> <endpoint [MAC:00:21:97:ab:da:1c]> < 17 04 00 18>]

Then on the QNX side it appears you are rejecting that:

sent [LCP ConfRej id=0x0 <auth chap 81> <mrru 1614> < 17 04 00 18>]

at which point the Microsoft server sends a hangup and terminates the connection.

This is just a best guess based on looking at the logs and googling CBCP.

Tim

3

Hi Tim,

This warning:
Warning - secret file /etc/ppp/pap-secrets has world and/or group access

It looks it is using the pap option,and because I’m connecting to a Windowx XP server it needs to be the chap option. Don’t you think?

Thanks

4

Manueloid,

If you go to this link:

cisco.com/en/US/tech/tk713/t … e945.shtml

and scroll down slightly to the 2nd table you can see what all the packets (CONFREQ, CONFREJ etc) mean.

So translating your debug data I read:

sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6362eb64> ]

QNX sends a configure request to the Windows Server and appears to me to request chap authorization with MD5.

rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap 81> <magic 0x73d079d7> <mrru 1614> <endpoint [MAC:00:21:97:ab:da:1c]> < 17 04 00 18>]

Windows sends a configure request for chap 81 (not sure what the difference between MD5 and 81 is but I am sure you can easily google what chap algorithm 81 is) and a CBCP callback.

sent [LCP ConfRej id=0x0 <auth chap 81> <mrru 1614> < 17 04 00 18>]

QNX sends a configure reject meaning chap 81 / CBCP is not supported or recognizable.

rcvd [LCP ConfNak id=0x1 <auth chap 81>]

Windows sends a configure NAK indicating it can only take chap 81.

sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x6362eb64> ]

QNX sends a 2nd configure request (id=0x2) for something else.

rcvd [LCP TermReq id=0x1 “s\37777777720y\37777777727\000<\37777777715t\000\000\003\37777777627”]

Windows send a termination request to hang up because the 2 sides can’t agree on a chap algorithm/CBCP.

sent [LCP TermAck id=0x1]

QNX acknowledges the hangup

Hangup (SIGHUP)

You hang up.

So it appears to me that QNX does not support either/both of chap 81 and CBCP. It may just be a simple configuration change to your modem script to change to the 81 algorithm instead of MD5.

Tim

5

Hi Tim,

I solved my problem only by changing the +chap option to +pap option. With this aut chap change to 81

Thanks