[Bluez-users] A blue chamaleon to be

[Bluez-users] A blue chamaleon to be

[zio tom]

Hello, I'm new both to Linux (OpenSuSe 10.0) and to Bluez. I'm using a  
Tecom dongle since two years on win xp (sorry). Now I'd like to use it  
even in Linux, but I can't pair my mobile (Motorola v600) in any way I'm  
trying. Object push works well, in&out.. It's the pairing my only problem.  
I tried to set as "none" the pairing mode in hcid.conf, and to "user" the  
security mode, as I red in your archive on Gmane, but it doesn't work. I  
also tried to set the security as auto, and the pin file text as PIN:****  
and not just ****. Everytime I try to establish a connection in need of  
pairing, my mobile pops up with a request for a pin code I simply... don't  
know. Where and how should I write it before trying to establish a  
connection with my phone?
Thank for your great work,
Giovanni.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[Marcel Holtmann]

Hi Giovanni,

> I'm new both to Linux (OpenSuSe 10.0) and to Bluez. I'm using a  
> Tecom dongle since two years on win xp (sorry). Now I'd like to use it  
> even in Linux, but I can't pair my mobile (Motorola v600) in any way I'm  
> trying. Object push works well, in&out.. It's the pairing my only problem.  
> I tried to set as "none" the pairing mode in hcid.conf, and to "user" the  
> security mode, as I red in your archive on Gmane, but it doesn't work. I  
> also tried to set the security as auto, and the pin file text as PIN:****  
> and not just ****. Everytime I try to establish a connection in need of  
> pairing, my mobile pops up with a request for a pin code I simply... don't  
> know. Where and how should I write it before trying to establish a  
> connection with my phone?

send in the output of "hcidump -X -V" while you are doing this.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[zio tom]

In data Thu, 15 Dec 2005 09:25:47 +0100, zio tom <zio.tom@gmail.com> ha  
scritto:

> Hello, I'm new both to Linux (OpenSuSe 10.0) and to Bluez. I'm using a  
> Tecom dongle since two years on win xp (sorry). Now I'd like to use it  
> even in Linux, but I can't pair my mobile (Motorola v600) in any way I'm  
> trying. Object push works well, in&out.. It's the pairing my only  
> problem. I tried to set as "none" the pairing mode in hcid.conf, and to  
> "user" the security mode, as I red in your archive on Gmane, but it  
> doesn't work. I also tried to set the security as auto, and the pin file  
> text as PIN:**** and not just ****. Everytime I try to establish a  
> connection in need of pairing, my mobile pops up with a request for a  
> pin code I simply... don't know. Where and how should I write it before  
> trying to establish a connection with my phone?
> Thank for your great work,
> Giovanni.

Which kind of log could I post to you for helping in help?




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[zio tom]

In data Thu, 15 Dec 2005 09:53:08 +0100, Marcel Holtmann  
<marcel@holtmann.org> ha scritto:

> Hi Giovanni,
> send in the output of "hcidump -X -V" while you are doing this.

Hi Marcel, thank you very much for you asnwering.
Here it is my output

Password:
linux:/home/giovanni # hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
     bdaddr 00:0A:28:0C:D4:EF ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
     Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
     Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
     status 0x00 handle 5 bdaddr 00:0A:28:0C:D4:EF type ACL encrypt 0x00
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
     handle 5 policy 0x0e
     Link policy: HOLD SNIFF PARK
> HCI Event: Max Slots Change (0x1b) plen 3
     handle 5 slots 5
> HCI Event: Command Complete (0x0e) plen 6
     Write Link Policy Settings (0x02|0x000d) ncmd 1
     status 0x00 handle 5
> HCI Event: Max Slots Change (0x1b) plen 3
     handle 5 slots 5
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
       Connection successful
< ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
       MTU 1024
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
       MTU 1506
< ACL data: handle 5 flags 0x02 dlen 14
     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
       Success
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 2
> ACL data: handle 5 flags 0x02 dlen 18
     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
       Success
       MTU 1024
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 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
     handle 5 packets 1
> ACL data: handle 5 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 5 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [psm 3]
       RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
       dlci 18 frame_type 0 credit_flow 15 pri 7 ack_timer 0
       frame_size 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> ACL data: handle 5 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [psm 3]
       RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
       dlci 18 frame_type 0 credit_flow 14 pri 7 ack_timer 0
       frame_size 1019 max_retrans 0 credits 0
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): SABM: cr 1 dlci 18 pf 1 ilen 0 fcs 0x32
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> HCI Event: Link Key Request (0x17) plen 6
     bdaddr 00:0A:28:0C:D4:EF
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
     bdaddr 00:0A:28:0C:D4:EF
> HCI Event: Command Complete (0x0e) plen 10
     Link Key Request Negative Reply (0x01|0x000c) ncmd 1
     status 0x00 bdaddr 00:0A:28:0C:D4:EF
> HCI Event: PIN Code Request (0x16) plen 6
     bdaddr 00:0A:28:0C:D4:EF
< HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
     bdaddr 00:0A:28:0C:D4:EF
> HCI Event: Command Complete (0x0e) plen 10
     PIN Code Request Negative Reply (0x01|0x000e) ncmd 1
     status 0x00 bdaddr 00:0A:28:0C:D4:EF
> ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DM: cr 1 dlci 18 pf 1 ilen 0 fcs 0x18
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 3
> HCI Event: Disconn Complete (0x05) plen 4
     status 0x00 handle 5 reason 0x13
     Reason: Remote User Terminated Connection
< HCI Command: Create Connection (0x01|0x0005) plen 13
     bdaddr 00:0A:28:0C:D4:EF ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
     Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
     Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
     status 0x00 handle 5 bdaddr 00:0A:28:0C:D4:EF type ACL encrypt 0x00
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
     handle 5 policy 0x0e
     Link policy: HOLD SNIFF PARK
> HCI Event: Command Complete (0x0e) plen 6
     Write Link Policy Settings (0x02|0x000d) ncmd 1
     status 0x00 handle 5
> HCI Event: Max Slots Change (0x1b) plen 3
     handle 5 slots 5
> HCI Event: Max Slots Change (0x1b) plen 3
     handle 5 slots 5
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
       Connection successful
< ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
       MTU 1024
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
       MTU 1506
< ACL data: handle 5 flags 0x02 dlen 14
     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
       Success
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 2
> ACL data: handle 5 flags 0x02 dlen 18
     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
       Success
       MTU 1024
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 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
     handle 5 packets 1
> ACL data: handle 5 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 5 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [psm 3]
       RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
       dlci 18 frame_type 0 credit_flow 15 pri 7 ack_timer 0
       frame_size 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> ACL data: handle 5 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [psm 3]
       RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
       dlci 18 frame_type 0 credit_flow 14 pri 7 ack_timer 0
       frame_size 1019 max_retrans 0 credits 0
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): SABM: cr 1 dlci 18 pf 1 ilen 0 fcs 0x32
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> HCI Event: Link Key Request (0x17) plen 6
     bdaddr 00:0A:28:0C:D4:EF
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
     bdaddr 00:0A:28:0C:D4:EF
> HCI Event: Command Complete (0x0e) plen 10
     Link Key Request Negative Reply (0x01|0x000c) ncmd 1
     status 0x00 bdaddr 00:0A:28:0C:D4:EF
> HCI Event: PIN Code Request (0x16) plen 6
     bdaddr 00:0A:28:0C:D4:EF
< HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
     bdaddr 00:0A:28:0C:D4:EF
> HCI Event: Command Complete (0x0e) plen 10
     PIN Code Request Negative Reply (0x01|0x000e) ncmd 1
     status 0x00 bdaddr 00:0A:28:0C:D4:EF
> ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DM: cr 1 dlci 18 pf 1 ilen 0 fcs 0x18
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 3
> HCI Event: Disconn Complete (0x05) plen 4
     status 0x00 handle 5 reason 0x13
     Reason: Remote User Terminated Connection


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[Marcel Holtmann]

Hi,

> > send in the output of "hcidump -X -V" while you are doing this.
> 
> thank you very much for you asnwering.
> Here it is my output
>
> > HCI Event: Link Key Request (0x17) plen 6
>      bdaddr 00:0A:28:0C:D4:EF
> < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
>      bdaddr 00:0A:28:0C:D4:EF
> > HCI Event: Command Complete (0x0e) plen 10
>      Link Key Request Negative Reply (0x01|0x000c) ncmd 1
>      status 0x00 bdaddr 00:0A:28:0C:D4:EF
> > HCI Event: PIN Code Request (0x16) plen 6
>      bdaddr 00:0A:28:0C:D4:EF
> < HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
>      bdaddr 00:0A:28:0C:D4:EF
> > HCI Event: Command Complete (0x0e) plen 10
>      PIN Code Request Negative Reply (0x01|0x000e) ncmd 1
>      status 0x00 bdaddr 00:0A:28:0C:D4:EF

look like the PIN helper program is not working and so hcid can't input
the PIN code at all. Check your syslog about any errors from hcid.

What version of bluez-utils is installed?

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[zio tom]

In data Thu, 15 Dec 2005 10:22:08 +0100, Marcel Holtmann  
<marcel@holtmann.org> ha scritto:

> Hi,
> What version of bluez-utils is installed?
>
> Regards
>
> Marcel

Hi!
2.19-5 is the number of the version installed. And.. sorry, but for the  
moment I don't know actually how to reach my syslog.. Thank you again.
Giovanni.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[Marcel Holtmann]

Hi Giovanni,

> 2.19-5 is the number of the version installed.

it would be better to upgrade to bluez-utils-2.23, because it fixed some
stuff with the PIN helper handling and even the error reporting was
improved.

> And.. sorry, but for the  
> moment I don't know actually how to reach my syslog.

I will be somewhere in /var/log/.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[zio tom]

In data Thu, 15 Dec 2005 11:22:59 +0100, Marcel Holtmann  
<marcel@holtmann.org> ha scritto:

> Hi Giovanni,
>
>> 2.19-5 is the number of the version installed.
>
> it would be better to upgrade to bluez-utils-2.23, because it fixed some
> stuff with the PIN helper handling and even the error reporting was
> improved.

Dear Marcel, since I'm not able to create a rpm package from a source  
*tar.gz, sorry, but I'm not able to upgrade my bluez-utils version. I'm  
googling in order to fix my technical lacks.
For the moment, i just reinstalled all bluez rpms on my system, and  
situations seems to be some different:
/etc/bluetooth/pin was BlueZ, and I changed it to 123456 (should I put  
there PIN:123456?)

#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $
#

# HCId options
options {
	# Automatically initialize new devices
	autoinit yes;

	# Security Manager mode
	#   none - Security manager disabled
	#   auto - Use local PIN for incoming connections
	#   user - Always ask user for a PIN
	#
	security user;

	# Pairing mode
	#   none  - Pairing disabled
	#   multi - Allow pairing with already paired devices
	#   once  - Pair once and deny successive attempts
	pairing multi;

	# PIN helper
	# if you want a interactiv query of your pin use /usr/bin/bluepin
	# /bin/bluepincat is using the pin in the /etc/bluetooth/pin file
	# pin_helper /usr/bin/bluepin;
	pin_helper /bin/bluepincat;  [strangely, before there was no mention of  
blupincat, etc. wow!]

	# D-Bus PIN helper
	#dbus_pin_helper;
}

# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "BlueZ %h (%d)";

	# Local device class
	# e.g.
	#  0xsss100 = Computer
	#  0xsss104 = Computer Desktop
	#  0xsss108 = Computer Server
	#  0xsss10c = Computer Laptop
	# The 'sss' above defines the service-class (not quite, only the
	# first 11 bits, the next 11 define the device-class, than 2 format bits.)
	# See https://www.bluetooth.org/foundry/assignnumb/document/baseband
	# for more information.
	# 0x100bbb stands for "Object Transfer  (v-Inbox, v-Folder, ...)"
	# 0x020bbb stands for "Networking (LAN, Ad hoc, ...)"
	class 0x000100;

	# Default packet type
	#pkt_type DH1,DM1,HV1;

	# Inquiry and Page scan
	# valid parameters: enable | disable
	iscan enable;
	pscan enable;

	# Default link mode
	#   none   - no specific policy
	#   accept - always accept incoming connections
	#   master - become master on incoming connections,
	#            deny role switch on outgoing connections
	lm accept;

	# Default link policy
	#   none    - no specific policy
	#   rswitch - allow role switch
	#   hold    - allow hold mode
	#   sniff   - allow sniff mode
	#   park    - allow park mode
	lp rswitch,hold,sniff,park;

	# Authentication and Encryption (Security Mode 3)
	auth disable;
	encrypt disable;
}

---------------------------------------------------------
bluepincat contains:

#!/bin/bash
#
# simple none interactiv handler for Bluetooth PIN's
# /etc/bluetooth/pin must only contain one line with the
# PIN code
# With big enhancements from Serguei Leontiev <leo@sai.msu.ru>
#

# if e.g. kbluetoothd is not running, kbluepin throws an error and returns  
1
KBLUETOOTHD_RUN=`ps -ea|grep kbluetoothd`
KBLUEPIN=${KBLUEPIN:-/opt/kde3/sbin/kbluepin}
if [ -x ${KBLUEPIN} \
    -a "X$KBLUETOOTHD_RUN" != "X" ]; then
    PIN=`$KBLUEPIN` && {
        case "$PIN" in
          PIN:*)
            echo "$PIN"
            exit 0
            ;;
        esac
    }
fi;

echo -n "PIN:"
cat /etc/bluetooth/pin

------------------------------------------------------------------
/etc/bluetooth/pin contains only 123456 (should it be PIN:123456?)

and finally rfcomm.conf

#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#

rfcomm0 {
	# Automatically bind the device at startup
	bind no;

	# Bluetooth address of the device
	device 00:0A:28:0C:D4:EF;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "V600";
}

Now I try to run a pairing attemp (using ftp Obex transfer) and I post to  
you the output of hcidump -X -V, ok?


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[zio tom]

In data Thu, 15 Dec 2005 16:50:00 +0100, zio tom <zio.tom@gmail.com> ha  
scritto:

> In data Thu, 15 Dec 2005 11:22:59 +0100, Marcel Holtmann  
> <marcel@holtmann.org> ha scritto:
>
>> Hi Giovanni,
>>
>>> 2.19-5 is the number of the version installed.
>>
>> it would be better to upgrade to bluez-utils-2.23, because it fixed some
>> stuff with the PIN helper handling and even the error reporting was
>> improved.

Marcel seems there is upgrade there,
now mobile and Linux are paired. I can view contents and archives, using  
the kbluepin interface seconds after having dialed the pin in the mobile  
display.
Now, when I'm trying to connect via GPRS through wvdial (after having  
configured wvdial.conf to fit to my provider's profile) here what I get:

giovanni@linux:~> su
Password:
linux:/home/giovanni # wvdial
--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/rfcomm0: Cannot get information for serial port.
--> Cannot open /dev/rfcomm0: Input/output error

What's the problem here?
bye, Giovanni.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] A blue chamaleon to be

[zio tom]

In data Thu, 15 Dec 2005 18:29:17 +0100, zio tom <zio.tom@gmail.com> ha  
scritto:

> Now, when I'm trying to connect via GPRS through wvdial (after having  
> configured wvdial.conf to fit to my provider's profile) here what I get:
>
> giovanni@linux:~> su
> Password:
> linux:/home/giovanni # wvdial
> --> WvDial: Internet dialer version 1.54.0
> --> Cannot open /dev/rfcomm0: Cannot get information for serial port.
> --> Cannot open /dev/rfcomm0: Input/output error

Sorry for having posted that too much in a hurry. Now, what configuration  
file or log should I post to make helping easier?
Thank you in advance,
Giovanni.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] Re: A blue chamaleon to be

[Michael Mauch]

zio tom wrote:

> In data Thu, 15 Dec 2005 18:29:17 +0100, zio tom <zio.tom@gmail.com> ha  
> scritto:
> 
> >Now, when I'm trying to connect via GPRS through wvdial (after having  
> >configured wvdial.conf to fit to my provider's profile) here what I get:
> >
> >giovanni@linux:~> su
> >Password:
> >linux:/home/giovanni # wvdial
> >--> WvDial: Internet dialer version 1.54.0
> >--> Cannot open /dev/rfcomm0: Cannot get information for serial port.
> >--> Cannot open /dev/rfcomm0: Input/output error
> 
> Sorry for having posted that too much in a hurry. Now, what configuration  
> file or log should I post to make helping easier?

"rfcomm" should show rfcomm0 with the device address and the channel.
If not, run "rfcomm bind 0". 

If that works, you could change the "bind no" to "bind yes" in
rfcomm.conf and restart the bluez/bluetooth init script (hopefully it
contains a "rfcomm bind all").


  Michael


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Re: A blue chamaleon to be

[zio tom]

In data Thu, 15 Dec 2005 22:17:16 +0100, Michael Mauch  
<michael.mauch@gmx.de> ha scritto:

> "rfcomm" should show rfcomm0 with the device address and the channel.
> If not, run "rfcomm bind 0".
>
> If that works, you could change the "bind no" to "bind yes" in
> rfcomm.conf and restart the bluez/bluetooth init script (hopefully it
> contains a "rfcomm bind all").

Thanks a lot for aswerin on such a newbie issue!
So, here my GPRS/Bluetooth situation. I start kde, I open the shell, I  
type su and the password, then wvdial, my mobile show a pin request, I  
insert it, the pc pops up with a small window asking the pin, I insert it,  
the phone says "the pin has been verified and saved"

and here what I get:

linux:/home/giovanni # wvdial
--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/rfcomm0: Cannot get information for serial port.
--> Cannot open /dev/rfcomm0: Input/output error
--> Cannot open /dev/rfcomm0: Cannot get information for serial port.
linux:/home/giovanni #


(Two new files appeared in my home folder, after the quantity of attempts  
of configuration of wvdial.conf and /etc/bluetooth I made: ttys1 and  
ttys10: the devices I tried to link to rfcomm0.
for a gprs connection, shall I use wvdial on the shell, and wvdial.conf  
for my provider's settings, right?)

My configuration now is:

#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $
#

# HCId options
options {
	# Automatically initialize new devices
	autoinit yes;

	# Security Manager mode
	#   none - Security manager disabled
	#   auto - Use local PIN for incoming connections
	#   user - Always ask user for a PIN
	#
	security user;

	# Pairing mode
	#   none  - Pairing disabled
	#   multi - Allow pairing with already paired devices
	#   once  - Pair once and deny successive attempts
	pairing multi;

	# PIN helper
	# if you want a interactiv query of your pin use /usr/bin/bluepin
	# /bin/bluepincat is using the pin in the /etc/bluetooth/pin file
	# pin_helper /usr/bin/bluepin;
	pin_helper /bin/bluepincat;

	# D-Bus PIN helper
	#dbus_pin_helper;
}

# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "BlueZ %h (%d)";

	# Local device class
	# e.g.
	#  0xsss100 = Computer
	#  0xsss104 = Computer Desktop
	#  0xsss108 = Computer Server
	#  0xsss10c = Computer Laptop
	# The 'sss' above defines the service-class (not quite, only the
	# first 11 bits, the next 11 define the device-class, than 2 format bits.)
	# See https://www.bluetooth.org/foundry/assignnumb/document/baseband
	# for more information.
	# 0x100bbb stands for "Object Transfer  (v-Inbox, v-Folder, ...)"
	# 0x020bbb stands for "Networking (LAN, Ad hoc, ...)"
	class 0x000100;

	# Default packet type
	#pkt_type DH1,DM1,HV1;

	# Inquiry and Page scan
	# valid parameters: enable | disable
	iscan enable;
	pscan enable;

	# Default link mode
	#   none   - no specific policy
	#   accept - always accept incoming connections
	#   master - become master on incoming connections,
	#            deny role switch on outgoing connections
	lm accept;

	# Default link policy
	#   none    - no specific policy
	#   rswitch - allow role switch
	#   hold    - allow hold mode
	#   sniff   - allow sniff mode
	#   park    - allow park mode
	lp rswitch,hold,sniff,park;

	# Authentication and Encryption (Security Mode 3)
	auth disable;
	encrypt disable;
}



#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#

rfcomm0 {
	# Automatically bind the device at startup
	bind yes;

	# Bluetooth address of the device
	device 00:0A:28:0C:D4:EF;

	# RFCOMM channel for the connection
	channel	1;

	# Description of the connection
	comment "V600";
}

pairing works. When I get the error

Another issue is that I can't use the mobile twice for a connection in the  
need of pairing (for example ftp obex): I always need to erase the pairing  
 from the phone e re-enter the pin on both devices.. Please help me, it's  
the third night I'm spending on this... :(

here is the result of hcidump -X -V while I'm trying to do this:


Password:
linux:/home/giovanni # hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.24
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
     bdaddr 00:0A:28:0C:D4:EF ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
     Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
     Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
     status 0x00 handle 5 bdaddr 00:0A:28:0C:D4:EF type ACL encrypt 0x00
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
     handle 5 policy 0x0f
     Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Max Slots Change (0x1b) plen 3
     handle 5 slots 5
> HCI Event: Command Complete (0x0e) plen 6
     Write Link Policy Settings (0x02|0x000d) ncmd 1
     status 0x00 handle 5
> HCI Event: Max Slots Change (0x1b) plen 3
     handle 5 slots 5
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
       Connection successful
< ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
       MTU 1024
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
       MTU 1506
< ACL data: handle 5 flags 0x02 dlen 14
     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
       Success
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 2
> ACL data: handle 5 flags 0x02 dlen 18
     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
       Success
       MTU 1024
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 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
     handle 5 packets 1
> ACL data: handle 5 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 5 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 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 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1
> ACL data: handle 5 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [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 1019 max_retrans 0 credits 0
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 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
     handle 5 packets 1
> HCI Event: PIN Code Request (0x16) plen 6
     bdaddr 00:0A:28:0C:D4:EF
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
     bdaddr 00:0A:28:0C:D4:EF len 6 pin '123456'
> HCI Event: Command Complete (0x0e) plen 10
     PIN Code Request Reply (0x01|0x000d) ncmd 1
     status 0x00 bdaddr 00:0A:28:0C:D4:EF
> HCI Event: Link Key Notification (0x18) plen 23
     bdaddr 00:0A:28:0C:D4:EF key 41EE651CF109EE6943EF895DFD9C993B type 0
> HCI Event: Encrypt Change (0x08) plen 4
     status 0x00 handle 5 encrypt 0x01
> ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(d): cid 0x0040 len 8 [psm 3]
       RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 1 b3 1 len 15
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8
> ACL data: handle 5 flags 0x02 dlen 13
     L2CAP(d): cid 0x0040 len 9 [psm 3]
       RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 5 fcs 0xaa mcc_len 3
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 1 b3 1 len 15
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(d): cid 0x0040 len 8 [psm 3]
       RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 1 b3 1 len 15
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 3
> ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(d): cid 0x0040 len 8 [psm 3]
       RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 1 b3 1 len 15
< ACL data: handle 5 flags 0x02 dlen 9
     L2CAP(d): cid 0x0040 len 5 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 5 flags 0x02 dlen 12
     L2CAP(s): Connect req: psm 3 scid 0x0041
> ACL data: handle 5 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
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 4
> ACL data: handle 5 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 5 flags 0x02 dlen 12
     L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
       Connection successful
< ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
       MTU 1024
> ACL data: handle 5 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
       MTU 1506
< ACL data: handle 5 flags 0x02 dlen 14
     L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
       Success
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 2
> ACL data: handle 5 flags 0x02 dlen 17
> ACL data: handle 5 flags 0x01 dlen 1
     L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
       Success
       MTU 1024
< ACL data: handle 5 flags 0x02 dlen 8
     L2CAP(d): cid 0x0041 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
     handle 5 packets 1
> ACL data: handle 5 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 5 flags 0x02 dlen 18
     L2CAP(d): cid 0x0041 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 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
     handle 5 packets 1


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] Re: A blue chamaleon to be

[Michael Mauch]

zio tom wrote:

> In data Thu, 15 Dec 2005 22:17:16 +0100, Michael Mauch  
> <michael.mauch@gmx.de> ha scritto:
> 
> >"rfcomm" should show rfcomm0 with the device address and the channel.
> >If not, run "rfcomm bind 0".

What's the output of "rfcomm" now?

> >If that works, you could change the "bind no" to "bind yes" in
> >rfcomm.conf and restart the bluez/bluetooth init script (hopefully it
> >contains a "rfcomm bind all").
> 
> Thanks a lot for aswerin on such a newbie issue!
> So, here my GPRS/Bluetooth situation. I start kde, I open the shell, I  
> type su and the password, then wvdial, my mobile show a pin request, I  
> insert it, the pc pops up with a small window asking the pin, I insert it,  
> the phone says "the pin has been verified and saved"

That's all ok if "rfcomm" shows:

  rfcomm0: 00:0A:28:0C:D4:EF channel 1 clean

before you use wvdial.

Are you sure that the channel number 1 is correct? It's different on
each device. Did you lookup this channel on your device with "sdptool
browse 00:0A:28:0C:D4:EF" or (if that doesn't work) with "sdptool
records 00:0A:28:0C:D4:EF"?

Look for the "Service Name" and the "Channel" lines. I don't know for which
service name you should look, on my phone it's called "SSA" (I don't
know if these names come from the phone or from bluez). If you can't
figure out the suitable channel, post the output of "sdptool records
00:0A:28:0C:D4:EF".


Sorry, I can't help with your other issue.

Regards...
		Michael


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Re: A blue chamaleon to be

[zio tom]

In data Fri, 16 Dec 2005 04:19:37 +0100, Michael Mauch  
<michael.mauch@gmx.de> ha scritto:

> What's the output of "rfcomm" now?

linux:/home/giovanni # rfcomm
rfcomm0: 00:0A:28:0C:D4:EF channel 1 clean

> That's all ok if "rfcomm" shows:

>  rfcomm0: 00:0A:28:0C:D4:EF channel 1 clean

> before you use wvdial.

So, I use it and I obtain:

linux:/home/giovanni # wvdial
--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/rfcomm0: Connection refused
--> Cannot open /dev/rfcomm0: Connection refused
--> Cannot open /dev/rfcomm0: Permission denied
linux:/home/giovanni #

> Are you sure that the channel number 1 is correct? It's different on
> each device. Did you lookup this channel on your device with "sdptool
> browse 00:0A:28:0C:D4:EF" or (if that doesn't work) with "sdptool
> records 00:0A:28:0C:D4:EF"?
> Look for the "Service Name" and the "Channel" lines. I don't know for  
> which
> service name you should look, on my phone it's called "SSA" (I don't
> know if these names come from the phone or from bluez). If you can't
> figure out the suitable channel, post the output of "sdptool records
> 00:0A:28:0C:D4:EF".

linux:/home/giovanni # sdptool browse 00:0A:28:0C:D4:EF
Browsing 00:0A:28:0C:D4:EF ...
Service RecHandle: 0x0
Service Class ID List:
   "SDP Server" (0x1000)
Protocol Descriptor List:
   "L2CAP" (0x0100)
   "SDP" (0x0001)
Profile Descriptor List:
   "SDP Server" (0x1000)
     Version: 0x0100

Service Name: Dial-up networking Gateway
Service Description: Dial-up networking Gateway
Service Provider: Motorola
Service RecHandle: 0x10001
Service Class ID List:
   "Dialup Networking" (0x1103)
Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 1
Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6465
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x6974
   encoding:    0x6a
   base_offset: 0xd806
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd809
   code_ISO639: 0x7472
   encoding:    0x6a
   base_offset: 0xd80c
   code_ISO639: 0x656c
   encoding:    0x6a
   base_offset: 0xd80f
Profile Descriptor List:
   "Dialup Networking" (0x1103)
     Version: 0x0100


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users