Re: ppp problem with isp
From: laura fairhead (run_signature_script_for_my_email_at_INVALID.com)
Date: 05/27/05
- Next message: cragazzon_at_tiscali.it: "Problem/conflict with upper/lower case file name"
- Previous message: Carlos Moreno: "Re: Anybody using a "real" Linux domain?"
- In reply to: Clifford Kite: "Re: ppp problem with isp"
- Next in thread: Unruh: "Re: ppp problem with isp"
- Reply: Unruh: "Re: ppp problem with isp"
- Reply: Clifford Kite: "Re: ppp problem with isp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 May 2005 19:46:12 GMT
On Fri, 27 May 2005 12:16:01 -0500, Clifford Kite <kite@see.signature.id> wrote:
>laura fairhead <run_signature_script_for_my_email@invalid.com> wrote:
>
>> Hi ppl,
>
>> I am experiencing a problem with the PPP setup
>> connecting to my (dial-up) service/connection
>> provider (btinternet). It has worked fine for
>> years but recently the internet connection under
>> Linux fails (Windows 98 still functions).
>
>Dual boot or two different computers?
Hi Clifford :)
This is just one comp with one modem, dual linux/win98
>
>> It does actually connect but I don't receive
>> any packets - well an ifconfig shows the ppp
>> device as having received those packets but
>> most of them are getting a "frame" error.
>> I wonder if it has something to do with
>> the MRU, presently I don't understand what
>> a frame error is.
>
>I suspect it means that the AHDLC frame used by PPP has a CRC error.
I thought it could be something like the MRU negociation being
bugged linux talking and windoze just leaving it with the default
or something But that doesn't seem to be the case.... Maybe it is one of
the compression protocols (ACP, PCP) or something lower level
than LCP (is that what you mean by AHDLC I'm not familiar with
the term ?)
>
>> Well I would appreciate any help, I have
>> started reading RFC1661 on PPP and eventually
>> maybe work out what is going on but it would
>> be great if someone with more experience
>> could advise me.
>
>If the ISP has changed it's PPP implementation or DCE and the new
><whichever> has a bug or configuration error then reading an RFC
>won't help.
I'd been putting off reading it for a long time, the subject
really fascinates me !
>
>Add the pppd option debug and the chat option -v, if chat is used
>to make the serial connection. Then make a PPP connection and
>after it's terminated post an exact copy, including timestamps,
>of /var/log/ppp.log so we can see what happens during PPP link
>negotiations.
Okay I did this plus I decoded the windoze log (at least just the
LCP stage maybe its not that )
>
>> I suppose BT/Yahoo changed something in the
>> PPP setup and it just happens that 98
>> is happy with it and Linux is not
>
>It is likely BT/Yahoo changed something. The alternative would seem
>to be that something has gone bad on the Linux host, such as kernel
>or pppd corruption, a modem or serial device problem, ect.
Okay here goes :)...
May 27 19:59:28 bell486 pppd[474]: Perms of /dev/ttyS1 are ok, no 'mesg n' neccesary.
May 27 19:59:29 bell486 chat[475]: abort on (NO CARRIER)
May 27 19:59:29 bell486 chat[475]: abort on (NO DIALTONE)
May 27 19:59:29 bell486 chat[475]: abort on (BUSY)
May 27 19:59:29 bell486 chat[475]: send (++AT&F^M)
May 27 19:59:29 bell486 chat[475]: expect (OK)
May 27 19:59:29 bell486 chat[475]: ++AT&F^M^M
May 27 19:59:29 bell486 chat[475]: OK
May 27 19:59:29 bell486 chat[475]: -- got it
May 27 19:59:29 bell486 chat[475]: send (ATM0^M)
May 27 19:59:29 bell486 chat[475]: expect (OK)
May 27 19:59:29 bell486 chat[475]: ^M
May 27 19:59:29 bell486 chat[475]: ATM0^M^M
May 27 19:59:29 bell486 chat[475]: OK
May 27 19:59:29 bell486 chat[475]: -- got it
May 27 19:59:29 bell486 chat[475]: send (ATDTxxxxxxxxxxxx^M)
May 27 19:59:30 bell486 chat[475]: timeout set to 600 seconds
May 27 19:59:30 bell486 chat[475]: expect (CONNECT 115200)
May 27 19:59:45 bell486 chat[475]: ATDTxxxxxxxxxxx^M^M
May 27 19:59:45 bell486 chat[475]: CARRIER 33600^M
May 27 19:59:46 bell486 chat[475]: ^M
May 27 19:59:46 bell486 chat[475]: PROTOCOL: LAP-M^M
May 27 19:59:46 bell486 chat[475]: ^M
May 27 19:59:46 bell486 chat[475]: CONNECT 115200
May 27 19:59:46 bell486 chat[475]: -- got it
May 27 19:59:46 bell486 pppd[474]: Serial connection established.
May 27 19:59:46 bell486 pppd[474]: Using interface ppp0
May 27 19:59:46 bell486 pppd[474]: Connect: ppp0 <--> /dev/ttyS1
May 27 19:59:47 bell486 pppd[474]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xd8d563ff> <pcomp> <accomp>]
May 27 19:59:47 bell486 pppd[474]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xd8d563ff> <pcomp> <accomp>]
May 27 19:59:49 bell486 pppd[474]: rcvd [LCP ConfReq id=0x34 <asyncmap 0xa0000> <auth chap MD5> <magic 0x4d848d69> <pcomp> <accomp>]
May 27 19:59:49 bell486 pppd[474]: sent [LCP ConfAck id=0x34 <asyncmap 0xa0000> <auth chap MD5> <magic 0x4d848d69> <pcomp> <accomp>]
May 27 19:59:49 bell486 pppd[474]: sent [LCP EchoReq id=0x0 magic=0xd8d563ff]
May 27 19:59:50 bell486 pppd[474]: rcvd [CHAP Challenge id=0x2f xxxxxxxxxxxxxxxxx ]
May 27 19:59:50 bell486 pppd[474]: sent [CHAP Response id=0x2f xxxxxxxxxxxxxxxx ]
May 27 19:59:50 bell486 pppd[474]: rcvd [LCP EchoRep id=0x0 magic=0x4d848d69]
May 27 19:59:50 bell486 pppd[474]: rcvd [CHAP Success id=0x2f ""]
May 27 19:59:50 bell486 pppd[474]: sent [IPCP ConfReq id=0x1 <addr 192.168.xxxxx> <compress VJ 0f 01> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
May 27 19:59:50 bell486 pppd[474]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
May 27 19:59:50 bell486 pppd[474]: rcvd [IPCP ConfReq id=0x79 <addr 212.140.212.63>]
May 27 19:59:50 bell486 pppd[474]: sent [IPCP ConfAck id=0x79 <addr 212.140.212.63>]
May 27 19:59:50 bell486 pppd[474]: rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
May 27 19:59:50 bell486 pppd[474]: sent [IPCP ConfReq id=0x2 <addr 192.168.xxxxx> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
May 27 19:59:50 bell486 pppd[474]: rcvd [LCP ProtRej id=0x17 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
May 27 19:59:50 bell486 pppd[474]: rcvd [IPCP ConfNak id=0x2 <addr 81.131.41.46> <ms-dns1 213.120.62.97> <ms-dns3 213.120.62.104>]
May 27 19:59:50 bell486 pppd[474]: sent [IPCP ConfReq id=0x3 <addr 81.131.41.46> <ms-dns1 213.120.62.97> <ms-dns3 213.120.62.104>]
May 27 19:59:59 bell486 last message repeated 3 times
May 27 20:00:01 bell486 pppd[474]: rcvd [IPCP ConfReq id=0x7a <addr 212.140.212.63>]
May 27 20:00:01 bell486 pppd[474]: sent [IPCP ConfAck id=0x7a <addr 212.140.212.63>]
May 27 20:00:01 bell486 pppd[474]: rcvd [IPCP ConfAck id=0x3 <addr 81.131.41.46> <ms-dns1 213.120.62.97> <ms-dns3 213.120.62.104>]
May 27 20:00:01 bell486 pppd[474]: local IP address 81.131.41.46
May 27 20:00:01 bell486 pppd[474]: remote IP address 212.140.212.63
May 27 20:00:01 bell486 pppd[474]: primary DNS address 213.120.62.97
May 27 20:00:01 bell486 pppd[474]: secondary DNS address 213.120.62.104
May 27 20:00:01 bell486 pppd[474]: Script /etc/ppp/ip-up started (pid 478)
May 27 20:00:01 bell486 pppd[474]: Script /etc/ppp/ip-up finished (pid 478), status = 0x0
May 27 20:00:19 bell486 pppd[474]: sent [LCP EchoReq id=0x1 magic=0xd8d563ff]
May 27 20:00:20 bell486 pppd[474]: rcvd [LCP EchoRep id=0x1 magic=0x4d848d69]
May 27 20:00:49 bell486 pppd[474]: sent [LCP EchoReq id=0x2 magic=0xd8d563ff]
May 27 20:00:50 bell486 pppd[474]: rcvd [LCP EchoRep id=0x2 magic=0x4d848d69]
Threebits in that worried me, the LAP, CARRIER thing at the start and the
repeated NAK thing in the middle and also that Protocol reject thing (could
the protocol compression be to blame?) ... I don't know about it though
I also ran ifconfig after the IP came up and it reported about 4 frame
errors which seemed to related directly to the echo req/rep
I decoded the windows PPP log, the rfc didn't have it but
I suppose ACCM in the below is async map and the LCP requests
CHAP (C223) with MD5 (the 5).
05-24-2005 10:03:16.05 - Microsoft Dial Up Adapter log opened.
05-24-2005 10:03:16.05 - Server type is PPP (Point to Point Protocol).
05-24-2005 10:03:16.05 - FSA : Software compression disabled.
05-24-2005 10:03:16.05 - FSA : Protocol not bound - skipping control protocol 803f (NBFCP).
05-24-2005 10:03:16.05 - FSA : Adding Control Protocol 8021 (IPCP) to control protocol chain.
05-24-2005 10:03:16.05 - FSA : Protocol not bound - skipping control protocol 802b (IPXCP).
05-24-2005 10:03:16.05 - FSA : Adding Control Protocol c029 (CallbackCP) to control protocol chain.
05-24-2005 10:03:16.05 - FSA : Adding Control Protocol c027 (no description) to control protocol chain.
05-24-2005 10:03:16.05 - FSA : Adding Control Protocol c023 (PAP) to control protocol chain.
05-24-2005 10:03:16.05 - FSA : Adding Control Protocol c223 (CHAP) to control protocol chain.
05-24-2005 10:03:16.06 - FSA : Adding Control Protocol c021 (LCP) to control protocol chain.
05-24-2005 10:03:16.06 - LCP : Callback negotiation enabled.
05-24-2005 10:03:16.06 - LCP : Layer started.
05-24-2005 10:03:16.06 - PPP : Transmitting Control Packet of length: 25
05-24-2005 10:03:16.06 - Data 0000: c0 21 01 01 00 17 02 06 | .!.....
05-24-2005 10:03:16.06 - Data 0008: 00 0a 00 00 05 06 00 01 | ........
05-24-2005 10:03:16.06 - Data 0010: 3a 91 07 02 08 02 0d 03 | :.......
05-24-2005 10:03:16.06 - Data 0018: 06 00 00 00 00 00 00 00 | ........
C0 21 01 01 00 17 = TRANSMIT configure request id#01
02 06 00 0A 00 00 type 02 (??->ACCM) =000A0000
05 06 00 01 3A 91 type 05 (magic no.)=00013A91
07 02 type 07 (proto field compression)
08 02 type 08 (addr + control field compression)
0D 03 06 type 0D (??->callback control option??)
05-24-2005 10:03:16.25 - PPP : Received Control Packet of length: 27
05-24-2005 10:03:16.25 - Data 0000: c0 21 01 99 00 19 02 06 | .!.....
05-24-2005 10:03:16.25 - Data 0008: 00 0a 00 00 03 05 c2 23 | .......#
05-24-2005 10:03:16.25 - Data 0010: 05 05 06 3b ef 1b ae 07 | ...;...
05-24-2005 10:03:16.25 - Data 0018: 02 08 02 00 00 00 00 00 | ........
C0 21 01 99 00 19 = RECEIVE configure request id#99
02 06 00 0A 00 00 type 02 (??->ACCM) =000A0000
03 05 C2 23 05 type 03 (auth) =C223 (chap) 05 (??)
05 06 3B EF 1B AE type 05 (magic no.)=3BEF1BAE
07 02 type 07 (proto field compression)
08 02 type 08 (addr + control field compression)
[ 00 00 00 00 00 ] PAD
05-24-2005 10:03:16.25 - LCP : Received and accepted ACCM of a0000.
05-24-2005 10:03:16.25 - LCP : Received and accepted authentication protocol c223 (CHAP).
05-24-2005 10:03:16.25 - LCP : Received and accepted magic number 3bef1bae.
05-24-2005 10:03:16.25 - LCP : Received and accepted protocol field compression option.
05-24-2005 10:03:16.25 - LCP : Received and accepted address+control field compression option.
05-24-2005 10:03:16.25 - PPP : Transmitting Control Packet of length: 27
C0 21 02 99 00 19 = TRANSMIT configure ack id#99
02 06 00 0A 00 00 (ack above request #99)
03 05 C2 23 05
05 06 3B EF 1B AE
07 02
08 02
05-24-2005 10:03:16.25 - Data 0000: c0 21 02 99 00 19 02 06 | .!.....
05-24-2005 10:03:16.25 - Data 0008: 00 0a 00 00 03 05 c2 23 | .......#
05-24-2005 10:03:16.25 - Data 0010: 05 05 06 3b ef 1b ae 07 | ...;...
05-24-2005 10:03:16.25 - Data 0018: 02 08 02 00 00 00 00 00 | ........
05-24-2005 10:03:16.25 - PPP : Received Control Packet of length: 9
05-24-2005 10:03:16.25 - Data 0000: c0 21 04 01 00 07 0d 03 | .!......
05-24-2005 10:03:16.25 - Data 0008: 06 00 00 00 00 00 00 00 | ........
C0 21 04 01 00 07 = RECEIVE configure reject id#01
0D 03 06 type 0D (??)
05-24-2005 10:03:16.25 - LCP : Received configure reject for callback control protocol option.
05-24-2005 10:03:16.25 - PPP : Transmitting Control Packet of length: 22
05-24-2005 10:03:16.25 - Data 0000: c0 21 01 02 00 14 02 06 | .!......
05-24-2005 10:03:16.25 - Data 0008: 00 0a 00 00 05 06 00 01 | ........
05-24-2005 10:03:16.25 - Data 0010: 3a 91 07 02 08 02 00 00 | :.......
C0 21 01 02 00 14 = TRANSMIT configure request id#02
02 06 00 0A 00 00 type 02 (??->ACCM) = 000A0000
05 06 00 01 3A 91 type 05 (magic no.)= 00013A91
07 02 type 07 (proto field compression)
08 02 type 08 (address + control field compression)
05-24-2005 10:03:16.39 - PPP : Received Control Packet of length: 22
05-24-2005 10:03:16.39 - Data 0000: c0 21 02 02 00 14 02 06 | .!......
05-24-2005 10:03:16.39 - Data 0008: 00 0a 00 00 05 06 00 01 | ........
05-24-2005 10:03:16.39 - Data 0010: 3a 91 07 02 08 02 00 00 | :.......
C0 21 02 02 00 14 = RECEIVE configure ack id#02
02 06 00 0A 00 00 (ack above request id#02)
05 06 00 01 3A 91
07 02
08 02
05-24-2005 10:03:16.39 - LCP : Layer up.
05-24-2005 10:03:16.39 - CHAP : Layer started.
bestwishesfrom
laura
>
>-- Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
>PPP-Q&A links, downloads: http://ckite.no-ip.net/
>/* In my book, the first poster to resort to personal abuse in a Usenet
> debate loses by default. - Rod Smith */
>
-- echo alru_aafriehdab@ittnreen.tocm |sed 's/\(.\)\(.\)/\2\1/g'
- Next message: cragazzon_at_tiscali.it: "Problem/conflict with upper/lower case file name"
- Previous message: Carlos Moreno: "Re: Anybody using a "real" Linux domain?"
- In reply to: Clifford Kite: "Re: ppp problem with isp"
- Next in thread: Unruh: "Re: ppp problem with isp"
- Reply: Unruh: "Re: ppp problem with isp"
- Reply: Clifford Kite: "Re: ppp problem with isp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
