Problems linking 2 Linux with PPP
Frederico Marques
I have a Linux PPPD Server werking nice with mgetty.
My /etc/ppp/options is:
---
lock
asyncmap 0
netmask 255.255.255.224
proxyarp
lock
crtscts
modem
mtu 552
mru 552
---
I'm using mgetty -> /etc/passwd authentication -> login -> pppd -detach
With a win95 client I have no problems during the
authentication/LCP/IPCP
negociation. Everything runs nicely, good pings, routing, etc.
BUT, if I connect with a Linux client (CHAT + PPPD), I can't get thru
IPCP (first
packet).
Here it is the following log from one session:
---
Nov 4 23:54:28 stoned pppd[619]: pppd 2.2.0 started by dsi1, uid 1000
Nov 4 23:54:28 stoned pppd[619]: Using interface ppp0
Nov 4 23:54:28 stoned pppd[619]: Connect: ppp0 <--> /dev/ttyS0
Nov 4 23:54:28 stoned pppd[619]: sent [LCP ConfReq id=0x1 <mru 552>
<asyncmap 0x0> <magic 0x9f3bd33a> <pcomp> <accomp>]
Nov 4 23:54:29 stoned pppd[619]: rcvd [LCP ConfAck id=0x1 <mru 552>
<asyncmap 0x0> <magic 0x9f3bd33a> <pcomp> <accomp>]
Nov 4 23:54:30 stoned pppd[619]: rcvd [LCP ConfReq id=0x1 <mru 552>
<asyncmap 0x0> <magic 0xac5ab90b> <pcomp> <accomp>]
Nov 4 23:54:30 stoned pppd[619]: sent [LCP ConfAck id=0x1 <mru 552>
<asyncmap 0x0> <magic 0xac5ab90b> <pcomp> <accomp>]
Nov 4 23:54:30 stoned pppd[619]: sent [IPCP ConfReq id=0x1 <addr
192.168.254.35> <compress VJ 0f 01>]
Nov 4 23:54:58 stoned last message repeated 9 times
Nov 4 23:55:01 stoned pppd[619]: IPCP: timeout sending Config-Requests
---
192.168.254.35 is the ip address of my server (STONED).
I don't have PAP/CHAP.
Both machines have the same PPP version -> 2.2.0.
On the client side:
same thing, whit last line:
---
Nov 4 23:55:32 moby pppd[199]: sent [IPCP ConfReq id=0x1 <addr
192.168.254.35> <compress Vj 0f 01>]
Nov 4 23:56:02 moby pppd[199]: IPCP: timeout sending Config-Requests
---
Why they can't continue with IPCP ?
TIA for any info on this,
Fred
--
Frederico Marques - fr...@meganet.pt
System Administrator - Meganet - ask for my PGP key.
Comnexo - Redes de Comunicação, S.A.
andrew sun
When PPP breaks after LCP,
it is often the result
of character transparency problems through the serial
connection. (Some control characters are not getting through).
Since your connection works with Win95,
try setting your Linux client with "asyncmap 000a0000"
which is the Win95 behavior.
And, if this should work, the preferable fix is to
revert back to asyncmap 0, and determine
why ctrl-s and/or ctrl-q are not getting through.
Perhaps a modem is undesirably set to software flow control.
--
Sun, Andrew, "Using & Managing PPP," O'Reilly & Associates, January 1999
http://www.oreilly.com/catalog/umppp