Preface to the remarks about the log below.
I can't say what's wrong, but maybe the comments on what is happening can
help clarify what is being negotiated by who for whom. I really don't know
much about MPPE though, and know nothing about the patched pppd's. The
messages concerning MPPE are interpreted according to the MPPE draft at
http://search.ietf.org/internet-drafts/draft-ietf-pppext-mppe-04.txt
On Wed, 17 May 2000 [EMAIL PROTECTED] wrote:
|Recently, my dialup account went from a standard PPP to an RAS-served
|one. Since that time I have struggled to get connected, authenticated,
|and accepted by this new setup. I am nearly there (thanks in part to
|perusing the archives of this list on mail-archive.com). I'm hoping
|someone out there can push me through the last wall.
|
|Here's the situation: I have grabbed and compiled the patches to both
|2.3.8 and 2.3.10 from http://www.moretonbay.com/vpn/download_pptp.html.
|This includes copying the SSLeay rc4.h and rc4_enc.c files for the
|build. I have updated my conf.modules to alias ppp_mppe, and have added
|the +chapms and mppe-40 lines to my ppp/options file. [near as I can
|tell, the patched 2.3.8 and 2.3.10 perform identically for the rest of
|this discussion.] Thanks in advance for any willing to wade through the
|following morass of data.
|
|Here is the command line I use to invoke/connect pppd:
|
|/usr/sbin/pppd -d -detach noauth connect "/usr/sbin/chat -v '' ATZ OK
|ATDT<<PHONENUMBER...REST OF LOGIN SCRIPT>>" /dev/ttyS1 115200
|ipcp-accept-local &
[Edited so I don't get an Excedrin headache too. :-)]
|Serial connection established.
|Using interface ppp0
|Connect: ppp0 <--> /dev/ttyS1
|sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x2f0f22bb> <pcomp> <accomp>]
|sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x2f0f22bb> <pcomp> <accomp>]
|rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap m$oft> <magic 0xcbf>
|<pcomp> <accomp>]
|sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth chap m$oft> <magic 0xcbf>
|<pcomp> <accomp>]
|rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x2f0f22bb> <pcomp> <accomp>]
|rcvd [CHAP Challenge id=0x68 <fddf93be36121e40>, name = "<<ACCT_SERVER>>"]
|sent [CHAP Response id=0x68
|<0000000000000000000000000000000000000000000000004b20b409f6ffcd816e5f387ae641f05eebe924ee484ddc6401>,
|name = "<<ME>>"]
|rcvd [CHAP Success id=0x68 ""]
All the above are normal.
|sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <compress VJ 0f 01>]
|sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <mppe 0 0 0 20>
|<bsd v1 15>]
MS doesn't do any of the CCP algorithms above except MPPE. Using the
options "nobsdcomp" and "nodeflate" will prevent useless negotiation.
The MPPE request is for the peer to send data compressed with a 40 bit key.
|rcvd [CCP ConfReq id=0x2 <mppe 0 0 0 71>]
This is a peer request that you send data compressed with MPPE at any
level of compression you want, and to use stateless mode.
|sent [CCP ConfNak id=0x2 <mppe 0 0 0 60>]
This is a "no thanks" from you to the peer request, and a suggestion to
request either a 40 bit or 128 bit key instead.
|rcvd [IPCP ConfReq id=0x3 <compress VJ 0f 01> <addr <<SERVER_IP>> >]
|sent [IPCP ConfAck id=0x3 <compress VJ 0f 01> <addr <<SERVER_IP>> >]
Peer requests and gets the IP address it asked for. Normal.
|rcvd [IPCP ConfNak id=0x1 <addr <<MY_NEW_IP>> >]
|sent [IPCP ConfReq id=0x2 <addr <<MY_NEW_IP>> > <compress VJ 0f 01>]
Peer says "no thanks" 0.0.0.0 and suggests MY_NEW_IP. Normal, 0.0.0.0 is
the standard way of asking the peer to provide your IP address for the PPP
connection. Normal.
|rcvd [CCP ConfRej id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
Peer rejects all CCP algorithms except MPPE.
|sent [CCP ConfReq id=0x2 <mppe 0 0 0 20>]
You ask the peer to send you data compressed using a 40 bit key, but
not using stateless mode.
|rcvd [CCP ConfReq id=0x4 <mppe 0 0 0 40>]
|sent [CCP ConfAck id=0x4 <mppe 0 0 0 40>]
The peer now requests data be sent to it compressed with a 128 bit key, and
you agree.
|rcvd [IPCP ConfAck id=0x2 <addr <<MY_NEW_IP>> > <compress VJ 0f 01>]
|local IP address <<MY_NEW_IP>>
|remote IP address <<SERVER_IP>>
Peer accepts your request for the IP address that it suggested.
|Script /etc/ppp/ip-up started (pid 4937)
|rcvd [CCP ConfAck id=0x2 <mppe 0 0 0 20>]
The peer will send data with a 40 bit key, as you requested.
|MPPE 40 bit, non-stateless compression enabled
You apparently are now ready to receive data with a MPPE 40 bit key.
|Script /etc/ppp/ip-up finished (pid 4937), status = 0x0
|MPPE-40 However, I
| cannot now ping <<SERVER_IP>> without seeing:
|
|rcvd [LCP ProtRej id=0x5 c0 d6 7d 15 da 80 73 e4 ee 28 ff 7d 1e 1d 6f 73
|d6 23 9f 3f 12 33 f3 e1 cb c3 15 f0 27 30 cc 15 dd 7e 4b fe 30 0a 79 0c
|cc bf c1 4c d5 25 0e 99 59 21 88 9c 4f dc 38 e7 bb a3 6b b1 5f 7d 3a 5b
|95 fc 6f d1 44 56 0b a1 ff 23 bb c3 c8
|Protocol-Reject for unsupported protocol 0xc0d6
These aren't protocols, but I don't recognize a pattern that suggests what
they actually are.
---
Clifford Kite Not a guru. (tm)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
