>> No! You stupid win95 machine!
>>
>> This *very brief* ppp log (below) shows my win95 machine issuing a
>> TermReq.....? Why? Why did the windows machine decide to bail from this
>
>I don't think it did...
>
>> connection? Should I invest in a sledge hammer for the windows machine?
>
>Probably not yet. Although I can't argue with your logic.
Why use a sledge hammer when you can just clean the disk and install
Linux? ;^)
>>
>> I would really appreciate any help I'm given.
>>
>
>It looks to me like you are in a serial loopback state. E.g. everything you
>send out you receive unmodified. Look at the magic numbers in your LCP
>negotiation. Notice how the packets you receive are the same as the ones
>you send. I believe they are suppose to be different, therefore catching
>any loopback problems. PPPD use to print this error out. Not sure why it
>isn't here.
This does not appear to be the case. If you'll notice, the Linux
machine sent an LCP Configure-Request request with a magic number
of 0xaf8b9050. If the link were in a loopback state, the LCP Configure-
Request it received (apparently from the Windows machine) would have
the same magic number (and other options). That didn't happen. The
Windows peer sent it's own LCP Configure-Request packet with it's own
options (most of them the same as Linux is using).
The thing that puzzles me is why the Windows peer agreed to authenticate
itself with PAP and then never sent an Authentciate-Request packet once
LCP reached the Opened state?!? After LCP was Opened, the Windows peer
just waited 5 seconds and decided to close the connection! Maybe the
Windows machine was not configure to do any authentciation, and it
just has a bad way of saying so?
>> Apr 19 13:49:26 gibberling pppd[2507]: pppd 2.3.7 started by root, uid 0
>> Apr 19 13:49:26 gibberling pppd[2507]: Using interface ppp0
>> Apr 19 13:49:26 gibberling pppd[2507]: Connect: ppp0 <--> /dev/ttya0
>> Apr 19 13:49:26 gibberling pppd[2507]: sent [LCP ConfReq id=0x1
>> <asyncmap 0x0> <auth pap> <magic 0xaf8b9050> <pcomp> <accomp>]
>> Apr 19 13:49:29 gibberling pppd[2507]: sent [LCP ConfReq id=0x1
>> <asyncmap 0x0> <auth pap> <magic 0xaf8b9050> <pcomp> <accomp>]
>> Apr 19 13:49:31 gibberling pppd[2507]: rcvd [LCP ConfReq id=0x1 <magic
>> 0x67e2a0> <pcomp> <accomp>]
>> Apr 19 13:49:31 gibberling pppd[2507]: sent [LCP ConfAck id=0x1 <magic
>> 0x67e2a0> <pcomp> <accomp>]
>> Apr 19 13:49:32 gibberling pppd[2507]: sent [LCP ConfReq id=0x1
>> <asyncmap 0x0> <auth pap> <magic 0xaf8b9050> <pcomp> <accomp>]
>> Apr 19 13:49:35 gibberling pppd[2507]: sent [LCP ConfReq id=0x1
>> <asyncmap 0x0> <auth pap> <magic 0xaf8b9050> <pcomp> <accomp>]
>> Apr 19 13:49:37 gibberling pppd[2507]: rcvd [LCP ConfAck id=0x1
>> <asyncmap 0x0> <auth pap> <magic 0xaf8b9050> <pcomp> <accomp>]
>> Apr 19 13:49:42 gibberling pppd[2507]: rcvd [LCP TermReq id=0x2]
>> Apr 19 13:49:42 gibberling pppd[2507]: LCP terminated by peer
>> Apr 19 13:49:42 gibberling pppd[2507]: sent [LCP TermAck id=0x2]
>> Apr 19 13:49:45 gibberling pppd[2507]: Connection terminated.
>> Apr 19 13:49:45 gibberling pppd[2507]: Connect time 0.4 minutes.
>> Apr 19 13:49:45 gibberling pppd[2507]: Exit.
============================================================================
Patrick Klos Email: [EMAIL PROTECTED]
Klos Technologies, Inc. Web: http://www.klos.com/
============================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
