* [Bluez-users] RFCOMM Connect problem
@ 2005-04-09 22:32 Magnus Larsson
0 siblings, 0 replies; 3+ messages in thread
From: Magnus Larsson @ 2005-04-09 22:32 UTC (permalink / raw)
To: bluez-users
I have tried to get Internet access working from my Dell LATITUDE D800 (Suse
9.2) via "Dial Up Networking" over Bluetooth and GPRS (Sony Ericsson S700i).
I have basically followed the instructions in the article "Linux : Net Access
with Bluetooth and GPRS" at
http://www.pcquest.com/content/linux/2004/104050807.asp.
I actually got it working once but now I can't get it up and running again.
See error messages from the "wvdial GPRS" command below.
File transfer over Bluetooth works "out of the box" in both directions so
basic setup seems to be ok.
I have tried to get a clue by reading old postings to this maillist but I seem
to miss something.
Below I have added configuration information as I understand is of importance.
Please advice me on what to change to get it up and running again!
Thanks in advance!
linux:~ # sdptool search --bdaddr 00:0F:DE:0B:A0:F5 DUN
Searching for DUN on 00:0F:DE:0B:A0:F5 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
linux:~ # rfcomm bind 0 00:0F:DE:0B:A0:F5 1
linux:~ # more /etc/wvdial.conf
[Modem0]
Modem = /dev/rfcomm0
Baud = 57600
SetVolume = 0
Dial Command = ATDT
Init1 = ATZ
Init3 = ATM0
FlowControl = None
[Dialer GPRS]
Username = user
Password = user
Phone = ATD*99#
Stupid Mode = 1
Inherits = Modem0
linux:~ # wvdial GPRS
--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/rfcomm0: Connection refused
--> Cannot open /dev/rfcomm0: Connection refused
--> Cannot open /dev/rfcomm0: Connection refused
linux:~ # hcidump
(from the failing "wvdial GPRS" command)
HCIDump - HCI packet analyzer ver 1.11
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Command Complete (0x0e) plen 6
> HCI Event: Max Slots Change (0x1b) plen 3
> ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0048 scid 0x0040 result 0 status 0
< ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0048 flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 4
MTU 674
> ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 674
< ACL data: handle 0x002e flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0048 flags 0x0000 result 0 clen 0
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0048 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x002e flags 0x02 dlen 18
L2CAP(d): cid 0x0048 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 669 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 19
L2CAP(d): cid 0x0040 len 15 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 330 max_retrans 0 credits 7
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0048 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0048 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0048 scid 0x0040
< ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0048 scid 0x0040
> ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0049 scid 0x0041 result 0 status 0
< ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0049 flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 4
MTU 674
> ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4
MTU 674
< ACL data: handle 0x002e flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0049 flags 0x0000 result 0 clen 0
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0049 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x002e flags 0x02 dlen 18
L2CAP(d): cid 0x0049 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 669 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 19
L2CAP(d): cid 0x0041 len 15 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 330 max_retrans 0 credits 7
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0049 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0049 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0049 scid 0x0041
< ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0049 scid 0x0041
> ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x004a scid 0x0040 result 0 status 0
< ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x004a flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 4
MTU 674
> ACL data: handle 0x002e flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 674
< ACL data: handle 0x002e flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x004a flags 0x0000 result 0 clen 0
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x004a len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x002e flags 0x02 dlen 18
L2CAP(d): cid 0x004a len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 669 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 19
L2CAP(d): cid 0x0040 len 15 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 330 max_retrans 0 credits 7
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x004a len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
< ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x004a len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x004a scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 0x002e flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> ACL data: handle 0x002e flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x004a scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4
--
Magnus Larsson
Callista Enterprise AB
Phone: +46 733 51 91 72
http://www.callista.se/Enterprise/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bluez-users] rfcomm connect problem
@ 2005-06-10 12:10 Mohan K
2005-06-15 7:32 ` [Bluez-users] rfcomm connect problem-help me please Mohan K
0 siblings, 1 reply; 3+ messages in thread
From: Mohan K @ 2005-06-10 12:10 UTC (permalink / raw)
To: bluez-users
Hi Everyone,
I am using two PC's, one consist of VIA mother board
and another one consist of Intel chipset mother board. I am having one
dongle of CSR chipset. In both PC's I installed Bluez(2.17).
First, I plugged the usb bluetooth dongle to VIA PC
and i used "rfcomm connect 0 <BDADDR> 1". It get connected and worked
fine. Then, I plugged the same dongle in the Intel chipset PC and used
"rfcomm connect 0 <BDADDR> 1". This is also working fine.
Again I did the First step. But now "rfcomm connect 0
<BDADDR> 1" fails with the following message:
Can't connect RFCOMM socket: Connection refused
At this time i am getting the following hcidump:
[root@localhost]# hcidump -x
HCI sniffer - Bluetooth packet analyzer ver 1.21
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005)
plen 13
bdaddr 00:80:25:02:02:69 ptype 0xcc18 rswitch
0x01 clkoffset 0x1cb8 (valid)
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
00 01 05 04
> HCI Event: Connect Complete (0x03) plen 11
00 29 00 69 02 02 25 80 00 01 00
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings
(0x02|0x000d) plen 4
handle 41 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Command Complete (0x0e) plen 6
01 0D 08 00 29 00
> HCI Event: Max Slots Change (0x1b) plen 3
29 00 05
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0052 scid
0x0040 result 0 status 0
Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0052 flags 0x00
clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00
result 0 clen 4
Success
MTU 335
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00
clen 4
MTU 335
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0052 flags 0x00
result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0052 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0
fcs 0x1c
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Link Key Request (0x17) plen 6
69 02 02 25 80 00
< HCI Command: Link Key Request Reply
(0x01|0x000b) plen 22
bdaddr 00:80:25:02:02:69 key
4BA5C9668C9B95F6134A074382BE737F
> HCI Event: Command Complete (0x0e) plen 10
01 0B 04 00 69 02 02 25 80 00
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 0 pf 1 ilen 0 fcs
0x36
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0052 scid
0x0040
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid
0x0052
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid
0x0052
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0052 scid
0x0040
> HCI Event: Disconn Complete (0x05) plen 4
00 29 00 13
Can any one tell me why this is happenning?
Advanced thanks for your valuable suggestions
Thanks & Regards,
Mohan
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bluez-users] rfcomm connect problem-help me please
2005-06-10 12:10 [Bluez-users] rfcomm connect problem Mohan K
@ 2005-06-15 7:32 ` Mohan K
0 siblings, 0 replies; 3+ messages in thread
From: Mohan K @ 2005-06-15 7:32 UTC (permalink / raw)
To: bluez-users
Hi all,
Again i am resending the same mail, since i have no idea to
proceed forward.
Can anyone help me to solve this problem, please?
Thanks & Regards,
Mohan
---------- Forwarded message ----------
From: Mohan K <kmohangda@gmail.com>
Date: Jun 10, 2005 5:40 PM
Subject: rfcomm connect problem
To: bluez-users@lists.sourceforge.net
Hi Everyone,
I am using two PC's, one consist of VIA mother board
and another one consist of Intel chipset mother board. I am having one
dongle of CSR chipset. In both PC's I installed Bluez(2.17).
First, I plugged the usb bluetooth dongle to VIA PC
and i used "rfcomm connect 0 <BDADDR> 1". It get connected and worked
fine. Then, I plugged the same dongle in the Intel chipset PC and used
"rfcomm connect 0 <BDADDR> 1". This is also working fine.
Again I did the First step. But now "rfcomm connect 0
<BDADDR> 1" fails with the following message:
Can't connect RFCOMM socket: Connection refused
At this time i am getting the following hcidump:
[root@localhost]# hcidump -x
HCI sniffer - Bluetooth packet analyzer ver 1.21
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005)
plen 13
bdaddr 00:80:25:02:02:69 ptype 0xcc18 rswitch
0x01 clkoffset 0x1cb8 (valid)
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
00 01 05 04
> HCI Event: Connect Complete (0x03) plen 11
00 29 00 69 02 02 25 80 00 01 00
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings
(0x02|0x000d) plen 4
handle 41 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Command Complete (0x0e) plen 6
01 0D 08 00 29 00
> HCI Event: Max Slots Change (0x1b) plen 3
29 00 05
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0052 scid
0x0040 result 0 status 0
Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0052 flags 0x00
clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00
result 0 clen 4
Success
MTU 335
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00
clen 4
MTU 335
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0052 flags 0x00
result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0052 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0
fcs 0x1c
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Link Key Request (0x17) plen 6
69 02 02 25 80 00
< HCI Command: Link Key Request Reply
(0x01|0x000b) plen 22
bdaddr 00:80:25:02:02:69 key
4BA5C9668C9B95F6134A074382BE737F
> HCI Event: Command Complete (0x0e) plen 10
01 0B 04 00 69 02 02 25 80 00
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 0 pf 1 ilen 0 fcs
0x36
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0052 scid
0x0040
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid
0x0052
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid
0x0052
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13)
plen 5
01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0052 scid
0x0040
> HCI Event: Disconn Complete (0x05) plen 4
00 29 00 13
Can any one tell me why this is happenning?
Advanced thanks for your valuable suggestions
Thanks & Regards,
Mohan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-06-15 7:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-10 12:10 [Bluez-users] rfcomm connect problem Mohan K
2005-06-15 7:32 ` [Bluez-users] rfcomm connect problem-help me please Mohan K
-- strict thread matches above, loose matches on Subject: below --
2005-04-09 22:32 [Bluez-users] RFCOMM Connect problem Magnus Larsson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.