|
List Info
Thread: pairing PC and phone
|
|
| pairing PC and phone |
|
2006-08-22 13:45:00 |
Hello guys
I'm tring to get my FreeBSD-6.1-STABLE to transfer files
with my NOKIA 6021 phone
here is what I do:
# kldload ng_ubt
# /etc/rc.bluetooth start ubt0
BD_ADDR: 11:11:11:11:11:11
Features: 0xbf 0xfe 0x8d 0x78 0x8 0x18 00 00
<3-Slot> <5-Slot> <Encryption> <Slot
offset>
<Timing accuracy> <Switch> <Sniff mode>
<RSSI>
<Channel quality> <SCO link> <HV2 packets>
<HV3 packets>
<u-law log> <A-law log> <CVSD> <Power
control>
<Transparent SCO data> <Unknown2.7>
Max. ACL packet size: 678 bytes
Number of ACL packets: 8
Max. SCO packet size: 48 bytes
Number of SCO packets: 10
# hccontrol -n ubt0hci inquiry
Inquiry result, num_responses=1
Inquiry result #0
BD_ADDR: 00:17:b0:53:55:29
Page Scan Rep. Mode: 0x2
Page Scan Period Mode: 0x2
Page Scan Mode: 00
Class: 52:02:04
Clock offset: 0x458
Inquiry complete. Status: No error [00]
# hccontrol -n ubt0hci remote_name_request 00:17:b0:53:55:29
0 0 0
BD_ADDR: 00:17:b0:53:55:29
Name: Tilifon
everything looks fine
this is my config
# cat /etc/bluetooth/hcsecd.conf
device {
bdaddr 00:00:00:00:00:00;
name "Default entry";
key nokey;
pin nopin;
}
device {
bdaddr 00:17:b0:53:55:29;
name "Tilifon";
key nokey;
pin "nopin";
}
so I run the hcsecd daemon
and I try:
# obexapp -c -a 00:17:b0:53:55:29 -C 1
my phone tells me that some device want to pair with it
I chose accept
and the phone is prompting me for passcode...
I enter something and it sasy "pairing failed"
and the obexapp exits
how to deal with this passcode ?
how to tell the obexapp to use some passcode ?
I've also tried this:
# hccontrol -n ubt0hci write_authentication_enable 1
# sdpcontrol -a 00:17:b0:53:55:29 browse
and it prompts me for passcode again
and the result is the same: "pairing failed"
than I've tried this:
# hccontrol -n ubt0hci write_authentication_enable 0
# sdpcontrol -a 00:17:b0:53:55:29 browse
Record Handle: 0x00010078
Service Class ID List:
Dial-Up Networking (0x1103)
Generic Networking (0x1201)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
1
Bluetooth Profile Descriptor List:
Dial-Up Networking (0x1103) ver. 1.0
Record Handle: 0x00010079
Service Class ID List:
Serial Port (0x1101)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
15
Record Handle: 0x0001007a
Service Class ID List:
Serial Port (0x1101)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
3
Record Handle: 0x0001007b
Service Class ID List:
Handsfree Audio Gateway (0x111f)
Generic Audio (0x1203)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
13
Bluetooth Profile Descriptor List:
Handsfree (0x111e) ver. 1.1
Record Handle: 0x0001007c
Service Class ID List:
Headset Audio Gateway (0x1112)
Generic Audio (0x1203)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
12
Bluetooth Profile Descriptor List:
Headset (0x1108) ver. 1.0
Record Handle: 0x00010081
Service Class ID List:
SIM Access (0x112d)
Generic Telephony (0x1204)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
4
Bluetooth Profile Descriptor List:
SIM Access (0x112d) ver. 1.0
Record Handle: 0x00010083
Service Class ID List:
OBEX Object Push (0x1105)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
9
OBEX (0x0008)
Bluetooth Profile Descriptor List:
OBEX Object Push (0x1105) ver. 1.0
Record Handle: 0x00010084
Service Class ID List:
OBEX File Transfer (0x1106)
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
10
OBEX (0x0008)
Bluetooth Profile Descriptor List:
OBEX File Transfer (0x1106) ver. 1.0
Record Handle: 0x00010086
Service Class ID List:
0x00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
L2CAP (0x0100)
RFCOMM (0x0003)
Protocol specific parameter #1: u/int8/bool
11
OBEX (0x0008)
and again with obex, but still the same...
can I anyone help me please
thank you 
------------------------------------------------------------
-----
http://ide.li/ - портал за
българите по света. Статии, новини, форуми, снимки,
информация.
_______________________________________________
freebsd-bluetooth freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-blu
etooth
To unsubscribe, send any mail to
"freebsd-bluetooth-unsubscribefreebsd.org"
|
|
| pairing PC and phone |
|
2006-08-22 17:12:15 |
Mario,
[...]
> # cat /etc/bluetooth/hcsecd.conf
> device {
> bdaddr 00:00:00:00:00:00;
> name "Default entry";
> key nokey;
> pin nopin;
> }
>
> device {
> bdaddr 00:17:b0:53:55:29;
> name "Tilifon";
> key nokey;
> pin "nopin";
> }
you need to specify pin code, for example
pin "1234";
> so I run the hcsecd daemon
>
> and I try:
> # obexapp -c -a 00:17:b0:53:55:29 -C 1
>
> my phone tells me that some device want to pair with it
> I chose accept
> and the phone is prompting me for passcode...
> I enter something and it sasy "pairing
failed"
when phone prompts, you need to enter the same pin code you
have put
into /etc/bluetooth/hcsecd.conf, i.e. for example above you
need to
enter 1234 on the phone.
thanks,
max
_______________________________________________
freebsd-bluetoothfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-blu
etooth
To unsubscribe, send any mail to
"freebsd-bluetooth-unsubscribefreebsd.org"
|
|
| pairing PC and phone |
|
2006-08-23 05:30:25 |
Hello,
put some "passcode" into the pin option (now you
have "nopin") in the
/etc/bluetooth/hcsecd.conf . Then use it in pairing process.
It is a good idea to setup an obex server. Here are some
notes:
http://wiki.botka.homeunix.org/bin/view/Main/BlueTooth
HTH.
Cheers,
-vlado
On Tue, 22 Aug 2006, Mario Pavlov wrote:
> Hello guys
> I'm tring to get my FreeBSD-6.1-STABLE to transfer
files with my NOKIA 6021 phone
>
> here is what I do:
>
> # kldload ng_ubt
>
> # /etc/rc.bluetooth start ubt0
> BD_ADDR: 11:11:11:11:11:11
> Features: 0xbf 0xfe 0x8d 0x78 0x8 0x18 00 00
> <3-Slot> <5-Slot> <Encryption>
<Slot offset>
> <Timing accuracy> <Switch> <Sniff
mode> <RSSI>
> <Channel quality> <SCO link> <HV2
packets> <HV3 packets>
> <u-law log> <A-law log> <CVSD>
<Power control>
> <Transparent SCO data> <Unknown2.7>
> Max. ACL packet size: 678 bytes
> Number of ACL packets: 8
> Max. SCO packet size: 48 bytes
> Number of SCO packets: 10
>
> # hccontrol -n ubt0hci inquiry
> Inquiry result, num_responses=1
> Inquiry result #0
> BD_ADDR: 00:17:b0:53:55:29
> Page Scan Rep. Mode: 0x2
> Page Scan Period Mode: 0x2
> Page Scan Mode: 00
> Class: 52:02:04
> Clock offset: 0x458
> Inquiry complete. Status: No error [00]
>
> # hccontrol -n ubt0hci remote_name_request
00:17:b0:53:55:29 0 0 0
> BD_ADDR: 00:17:b0:53:55:29
> Name: Tilifon
>
> everything looks fine
> this is my config
>
> # cat /etc/bluetooth/hcsecd.conf
> device {
> bdaddr 00:00:00:00:00:00;
> name "Default entry";
> key nokey;
> pin nopin;
> }
>
> device {
> bdaddr 00:17:b0:53:55:29;
> name "Tilifon";
> key nokey;
> pin "nopin";
> }
>
> so I run the hcsecd daemon
>
> and I try:
> # obexapp -c -a 00:17:b0:53:55:29 -C 1
>
> my phone tells me that some device want to pair with it
> I chose accept
> and the phone is prompting me for passcode...
> I enter something and it sasy "pairing
failed"
> and the obexapp exits
> how to deal with this passcode ?
> how to tell the obexapp to use some passcode ?
>
> I've also tried this:
> # hccontrol -n ubt0hci write_authentication_enable 1
> # sdpcontrol -a 00:17:b0:53:55:29 browse
> and it prompts me for passcode again
> and the result is the same: "pairing
failed"
>
> than I've tried this:
> # hccontrol -n ubt0hci write_authentication_enable 0
> # sdpcontrol -a 00:17:b0:53:55:29 browse
>
> Record Handle: 0x00010078
> Service Class ID List:
> Dial-Up Networking (0x1103)
> Generic Networking (0x1201)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 1
> Bluetooth Profile Descriptor List:
> Dial-Up Networking (0x1103) ver. 1.0
>
> Record Handle: 0x00010079
> Service Class ID List:
> Serial Port (0x1101)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 15
>
> Record Handle: 0x0001007a
> Service Class ID List:
> Serial Port (0x1101)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 3
>
> Record Handle: 0x0001007b
> Service Class ID List:
> Handsfree Audio Gateway (0x111f)
> Generic Audio (0x1203)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 13
> Bluetooth Profile Descriptor List:
> Handsfree (0x111e) ver. 1.1
>
> Record Handle: 0x0001007c
> Service Class ID List:
> Headset Audio Gateway (0x1112)
> Generic Audio (0x1203)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 12
> Bluetooth Profile Descriptor List:
> Headset (0x1108) ver. 1.0
>
> Record Handle: 0x00010081
> Service Class ID List:
> SIM Access (0x112d)
> Generic Telephony (0x1204)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 4
> Bluetooth Profile Descriptor List:
> SIM Access (0x112d) ver. 1.0
>
> Record Handle: 0x00010083
> Service Class ID List:
> OBEX Object Push (0x1105)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 9
> OBEX (0x0008)
> Bluetooth Profile Descriptor List:
> OBEX Object Push (0x1105) ver. 1.0
>
> Record Handle: 0x00010084
> Service Class ID List:
> OBEX File Transfer (0x1106)
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 10
> OBEX (0x0008)
> Bluetooth Profile Descriptor List:
> OBEX File Transfer (0x1106) ver. 1.0
>
> Record Handle: 0x00010086
> Service Class ID List:
> 0x00000002-0000-1000-8000-0002ee000002
> Protocol Descriptor List:
> L2CAP (0x0100)
> RFCOMM (0x0003)
> Protocol specific parameter #1:
u/int8/bool 11
> OBEX (0x0008)
>
> and again with obex, but still the same...
>
> can I anyone help me please
> thank you
>
>
>
>
------------------------------------------------------------
-----
> http://ide.li/ - ?????? ??
????????? ?? ?????. ??????, ??????, ??????, ??????,
??????????.
> _______________________________________________
> freebsd-bluetoothfreebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-blu
etooth
> To unsubscribe, send any mail to
"freebsd-bluetooth-unsubscribefreebsd.org"
>
>
_______________________________________________
freebsd-bluetoothfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-blu
etooth
To unsubscribe, send any mail to
"freebsd-bluetooth-unsubscribefreebsd.org"
|
|
| pairing PC and phone |
|
2006-08-23 17:20:22 |
Vladimir,
> put some "passcode" into the pin option
(now you have "nopin") in the
> /etc/bluetooth/hcsecd.conf . Then use it in pairing
process.
>
> It is a good idea to setup an obex server. Here are
some notes:
> http://wiki.botka.homeunix.org/bin/view/Main/BlueTooth
please take no offense, but this kind of notes are not very
helpful.
this is what i call "linux howto-style"
documentation. all it (usually)
does is provides list of some commands to execute without
giving any
background information. it may work for some users, however,
when
someone's environment is not exactly the same it does not
work and
leaves no clue to what might be going wrong and how to fix
it.
personally, i've seen quite a few wiki's/howto's/etc.
related to freebsd
and bluetooth, however none of them gives all the
information.
so, it would be very nice if someone wrote a document
describing
bluetooth basics, i.e.
- concept of baseband (physical/radio) link
- concept of logical links, i.e. l2cap and rfcomm
- concept of l2cap psm and rfcomm channel
- what is pairing, how it works exactly and why one needs it
- concept of bluetooth services/profiles
- concept of bluetooth service discovery
thanks,
max
_______________________________________________
freebsd-bluetoothfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-blu
etooth
To unsubscribe, send any mail to
"freebsd-bluetooth-unsubscribefreebsd.org"
|
|
[1-4]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|