OESF Portables Forum

Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Security and Networking => Topic started by: prokaryx on October 01, 2004, 08:43:10 am

Title: What's "LCP: timeout sending Config-Requests"
Post by: prokaryx on October 01, 2004, 08:43:10 am: I'm trying to get my zaurus c860 online with GPRS using my mobile phone, via bluetooth.

Here's my specs:
ROM: Cacko 1.21b (didn't install any extra bluetooth stuff)
Phone: Ericsson T39m
CID=2
Init string: ATZ
Bluetooth CF: Bluetake BT0100M

I've set up the connection using the "Network" settings. Didn't tinker with any ppp dialup or chatscripts.

I don't think the bluetooth part is the problem, as you can see from the /var/log/messages below. I started the syslog just before I attempted the connection and stopped syslog when the connection was broken.

Oct 1 11:53:48 localhost syslogd 1.4.1: restart.
Oct 1 11:53:48 localhost syslog: syslogd startup succeeded
Oct 1 11:53:48 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 1 11:53:48 localhost kernel: pxa_pcmcia_suspend(0)
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: udc_disable: ep0_urb already NULL
Oct 1 11:53:48 localhost kernel: udc_disable: ep0_urb already NULL
Oct 1 11:53:48 localhost kernel: usbdcore: usbdcore 0.1 035 2002-06-12 20:00 exiting
Oct 1 11:53:48 localhost kernel: monitor_pm_event: suspend finished (rc=0)
Oct 1 11:53:48 localhost kernel: pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
Oct 1 11:53:48 localhost kernel: sharp_sl_nand_suspend
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost syslog: klogd startup succeeded
Oct 1 11:53:48 localhost kernel: FCS : CCCR = 161
Oct 1 11:53:48 localhost kernel: sharp_sl_nand_resume
Oct 1 11:53:48 localhost kernel: pxa_pcmcia_init(0)
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: pxa_pcmcia_init(1)
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: [SD]-clustsize = 4000
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost last message repeated 4 times
Oct 1 11:53:48 localhost kernel: usbdcore: usbdcore 0.1 035 2002-06-12 20:00 (dbg="")
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: net_fd 0.1 035 2002-06-12 20:00 (dbg="",alwaysup=0,OUT=64,IN=64)
Oct 1 11:53:48 localhost kernel: vendorID: 4dd productID: 9031
Oct 1 11:53:48 localhost kernel: pxa_bi 0.1-alpha 035 2002-06-12 20:00 (dbg="")
Oct 1 11:53:48 localhost kernel: bi_modinit: call udc_startup_events
Oct 1 11:53:48 localhost kernel: bi_device_event: call udc_enable
Oct 1 11:53:48 localhost kernel: bi_device_event: call udc_all_interrupts
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost last message repeated 45 times
Oct 1 11:53:48 localhost kernel: udc_disable: ep0_urb already NULL
Oct 1 11:53:48 localhost kernel: udc_disable: ep0_urb already NULL
Oct 1 11:53:48 localhost kernel: usbdcore: usbdcore 0.1 035 2002-06-12 20:00 exiting
Oct 1 11:53:48 localhost kernel: monitor_pm_event: suspend finished (rc=0)
Oct 1 11:53:48 localhost kernel: pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
Oct 1 11:53:48 localhost kernel: pxa_pcmcia_suspend(0)
Oct 1 11:53:48 localhost kernel: sharp_sl_nand_suspend
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: FCS : CCCR = 161
Oct 1 11:53:48 localhost kernel: sharp_sl_nand_resume
Oct 1 11:53:48 localhost kernel: pxa_pcmcia_init(0)
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: pxa_pcmcia_init(1)
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: [SD]-clustsize = 4000
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost last message repeated 4 times
Oct 1 11:53:48 localhost kernel: usbdcore: usbdcore 0.1 035 2002-06-12 20:00 (dbg="")
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: net_fd 0.1 035 2002-06-12 20:00 (dbg="",alwaysup=0,OUT=64,IN=64)
Oct 1 11:53:48 localhost kernel: vendorID: 4dd productID: 9031
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost kernel: pxa_bi 0.1-alpha 035 2002-06-12 20:00 (dbg="")
Oct 1 11:53:48 localhost kernel: bi_modinit: call udc_startup_events
Oct 1 11:53:48 localhost kernel: bi_device_event: call udc_enable
Oct 1 11:53:48 localhost kernel: bi_device_event: call udc_all_interrupts
Oct 1 11:53:48 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:53:48 localhost last message repeated 62 times

Oct 1 11:53:48 localhost kernel: BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Oct 1 11:53:48 localhost kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Oct 1 11:53:48 localhost kernel: BlueZ RFCOMM ver 1.1
Oct 1 11:53:48 localhost kernel: Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Oct 1 11:53:48 localhost kernel: Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>
Oct 1 11:53:53 localhost pppd[29345]: pppd 2.4.0 started by root, uid 0
Oct 1 11:53:53 localhost kernel: bcsp_timed_event: Timeout, retransmitting 1 pkts
Oct 1 11:54:02 localhost hcid[29303]: link_key_request (sba=00:08:F4:20:01:F7, dba=00:80:37:26:B0:73)
Oct 1 11:54:04 localhost chat[29347]: abort on (NO CARRIER)
Oct 1 11:54:04 localhost chat[29347]: abort on (NO DIALTONE)
Oct 1 11:54:04 localhost chat[29347]: abort on (BUSY)
Oct 1 11:54:04 localhost chat[29347]: send (ATZ^M)
Oct 1 11:54:04 localhost chat[29347]: expect (OK)
Oct 1 11:54:04 localhost chat[29347]: ATZ^M^M
Oct 1 11:54:04 localhost chat[29347]: OK
Oct 1 11:54:04 localhost chat[29347]: -- got it
Oct 1 11:54:04 localhost chat[29347]: send (ATDT*99***2#^M)
Oct 1 11:54:04 localhost chat[29347]: expect (CONNECT)
Oct 1 11:54:04 localhost chat[29347]: ^M
Oct 1 11:54:05 localhost chat[29347]: ATDT*99***2#^M^M
Oct 1 11:54:05 localhost chat[29347]: CONNECT
Oct 1 11:54:05 localhost chat[29347]: -- got it
Oct 1 11:54:05 localhost pppd[29345]: Serial connection established.
Oct 1 11:54:05 localhost pppd[29345]: Using interface ppp0
Oct 1 11:54:05 localhost pppd[29345]: Connect: ppp0 <--> /dev/rfcomm0
Oct 1 11:55:00 localhost pppd[29345]: LCP: timeout sending Config-Requests
Oct 1 11:55:00 localhost pppd[29345]: Connection terminated.
Oct 1 11:55:02 localhost pppd[29345]: Exit.
Oct 1 11:55:08 localhost kernel: Kernel logging (proc) stopped.
Oct 1 11:55:08 localhost kernel: Kernel log daemon terminating.
Oct 1 11:55:09 localhost syslog: klogd shutdown succeeded
Oct 1 11:55:09 localhost exiting on signal 15

I can see on my phone that the pairing with my zaurus is successful and the phone is able to dial out. I can see the "Connecting..." message on my phone and after some time, it breaks and displays "Disconnected. Last session received 0 bytes; sent 0 bytes"

Sometimes, when I do a fresh insert of the bluetooth card, the connection is successful and the network applet shows that I am online but when I try to access a page in Netfront or Opera, I get "DNS host not found". What on earth does that mean? The network applet shows all my IP correctly, as given by my ISP.

Since I don't know anything about networking in general, I need help on what these errors mean. Thanks in advance.
Title: What's "LCP: timeout sending Config-Requests"
Post by: lardman on October 01, 2004, 09:49:41 am: LCP is something like Link Connection Protocol, there are lots of hits on google about this (though I don't know whether there are any answers).

What does your chatscript look like? Do you have entries in pap- and chap-secrets?

Si
Title: What's "LCP: timeout sending Config-Requests"
Post by: cvmiller on October 01, 2004, 03:00:18 pm: prokaryx,

Configuration Request means that it is looking for the PPP server on the far side, and it isn't finding it (and therefore hanging up).

I have a trace from PPPoE, but the PPP messages are the same:
Code: [Select]
1 0.000000 00:30:65:c0:d5:38 ff:ff:ff:ff:ff:ff PPPoED Active Discovery Initiation (PADI) 2 0.000541 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPPoED Active Discovery Offer (PADO) 3 0.010855 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPPoED Active Discovery Request (PADR) 4 0.230119 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPPoED Active Discovery Session-confirmation (PADS) 5 0.231701 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP LCP PPP LCP Configuration Request 6 0.232777 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP LCP PPP LCP Configuration Request 7 0.232825 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP LCP PPP LCP Configuration Ack 8 0.234319 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP LCP PPP LCP Configuration Ack 9 0.235079 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP LCP PPP LCP Echo Request 10 0.235147 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP PAP PPP PAP Authenticate-Request 11 0.235566 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP LCP PPP LCP Echo Reply 12 0.242109 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP PAP PPP PAP Authenticate-Ack 13 0.242409 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP IPCP PPP IPCP Configuration Request 14 0.243492 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP IPCP PPP IPCP Configuration Request 15 0.243784 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP IPCP PPP IPCP Configuration Ack 16 0.244634 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP IPCP PPP IPCP Configuration Nak 17 0.244949 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP IPCP PPP IPCP Configuration Request 18 0.245586 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP IPCP PPP IPCP Configuration Ack 19 1.767249 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPP LCP PPP LCP Echo Request 20 1.767631 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPP LCP PPP LCP Echo Reply 22 3.405246 1.0.0.1 50.0.0.1 ICMP Echo (ping) request 23 3.406181 50.0.0.1 1.0.0.1 ICMP Echo (ping) reply 24 4.404803 1.0.0.1 50.0.0.1 ICMP Echo (ping) request 25 4.405962 50.0.0.1 1.0.0.1 ICMP Echo (ping) reply 26 5.404812 1.0.0.1 50.0.0.1 ICMP Echo (ping) request 27 5.405833 50.0.0.1 1.0.0.1 ICMP Echo (ping) reply 29 6.404814 1.0.0.1 50.0.0.1 ICMP Echo (ping) request 30 6.405734 50.0.0.1 1.0.0.1 ICMP Echo (ping) reply 33 11.968488 00:30:65:c0:d5:38 00:05:5e:2d:fd:52 PPPoED Active Discovery Terminate (PADT) 34 11.968987 00:05:5e:2d:fd:52 00:30:65:c0:d5:38 PPPoED Active Discovery Terminate (PADT)
As you can see, you haven't even hit the Authentication phase of PPP yet.

I hope this helps,

Craig...
Title: What's "LCP: timeout sending Config-Requests"
Post by: lardman on October 02, 2004, 06:29:07 am: Does the number you're dialing support both ppp and a terminal login?

If so you may want to add a "~ ''" to the end of the chatscript so that it waits for ppp to start (~ is the first char of the ppp data, the '' - two single quotes - means send nothing back) on the other end before it returns (so that the other end doesn't think it's being asked for the terminal login)

Si