linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bluez-users] BD hardware address problem
@ 2006-07-16 22:10 Łukasz Hejnak
  2006-07-16 22:20 ` Marcel Holtmann
  0 siblings, 1 reply; 5+ messages in thread
From: Łukasz Hejnak @ 2006-07-16 22:10 UTC (permalink / raw)
  To: Bluetooth

Hi
I've been trying to make a bluetooth link between two computers, a 
windows run laptop and my linux box - using two bluetooth usb dongles

The devices see each other (hcitool inq) but I can't get them connected 
using pand:
Jul 16 18:55:20 szift pand[5200]: Connecting to 11:11:11:11:11:11
Jul 16 18:55:20 szift pand[5200]: Connect to 11:11:11:11:11:11 failed. 
No route to host(113)

I think the problem is quite obvious: they both have been assigned the 
same bd address: 11:11:11:11:11:11
whatever I try, both devices still have the same bd addresses leading 
even to a situation like this (when connected to the same PC):

root@szift:/home/szift#hciconfig -a
hci0:   Type: USB
         BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
         UP RUNNING PSCAN ISCAN AUTH ENCRYPT
         RX bytes:2511835 acl:13393 sco:0 events:8268 errors:0
         TX bytes:693525 acl:8233 sco:0 commands:25 errors:0
         Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
         Packet type: DM1 DH1 HV1
         Link policy: RSWITCH HOLD SNIFF PARK
         Link mode: SLAVE ACCEPT
         Class: 0x3e0100
         Service Classes: Networking, Rendering, Capturing
         Device Class: Computer, Uncategorized
         HCI Ver: 1.2 (0x2) HCI Rev: 0x1fe LMP Ver: 1.2 (0x2) LMP 
Subver: 0x1fe
         Manufacturer: Integrated System Solution Corp. (57)

hci1:   Type: USB
         BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
         UP RUNNING PSCAN ISCAN AUTH ENCRYPT
         RX bytes:118 acl:0 sco:0 events:15 errors:0
         TX bytes:312 acl:0 sco:0 commands:15 errors:0
         Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
         Packet type: DM1 DH1 HV1
         Link policy: RSWITCH HOLD SNIFF PARK
         Link mode: SLAVE ACCEPT
         Class: 0x3e0100
         Service Classes: Networking, Rendering, Capturing
         Device Class: Computer, Uncategorized
         HCI Ver: 1.2 (0x2) HCI Rev: 0x1fe LMP Ver: 1.2 (0x2) LMP 
Subver: 0x1fe
         Manufacturer: Integrated System Solution Corp. (57)


So I guess no wonder why pand didn't know which device I've been talking 
about when I typed 11:11:11...

Apart from this, both devices work fine.
I tested them with my nokia 6310i to get a gprs connection and it works.

So my question is:
is there anything I can do to change those bd addresses?
or is there any other way to get the connection up and going?

*My target is to share an EDGE link from the windows machine via these 
bluetooth adapters to my linux box*

I use bluez libs/utils 2.25 with a 2.6.16 kernel
The windows is a XP home with the drivers that were shipped together 
with the dongles (that side also works fine with the phone).

--
Best wishes
Lukasz 'Szift' Hejnak


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] BD hardware address problem
  2006-07-16 22:10 [Bluez-users] BD hardware address problem Łukasz Hejnak
@ 2006-07-16 22:20 ` Marcel Holtmann
  2006-07-16 23:02   ` Łukasz Hejnak
  0 siblings, 1 reply; 5+ messages in thread
From: Marcel Holtmann @ 2006-07-16 22:20 UTC (permalink / raw)
  To: BlueZ users

Hi Lukasz,

> I've been trying to make a bluetooth link between two computers, a 
> windows run laptop and my linux box - using two bluetooth usb dongles
> 
> The devices see each other (hcitool inq) but I can't get them connected 
> using pand:
> Jul 16 18:55:20 szift pand[5200]: Connecting to 11:11:11:11:11:11
> Jul 16 18:55:20 szift pand[5200]: Connect to 11:11:11:11:11:11 failed. 
> No route to host(113)
> 
> I think the problem is quite obvious: they both have been assigned the 
> same bd address: 11:11:11:11:11:11
> whatever I try, both devices still have the same bd addresses leading 
> even to a situation like this (when connected to the same PC):

this is a known problem and it is these stupid ISSC dongles where the
manufacturer doesn't assigned unique addresses to each dongle. You can
try to use bdaddr from CVS to set your own address.

Regards

Marcel




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] BD hardware address problem
  2006-07-16 22:20 ` Marcel Holtmann
@ 2006-07-16 23:02   ` Łukasz Hejnak
  2006-07-17  0:09     ` ?ukasz Hejnak
  0 siblings, 1 reply; 5+ messages in thread
From: Łukasz Hejnak @ 2006-07-16 23:02 UTC (permalink / raw)
  To: BlueZ users


>> I've been trying to make a bluetooth link between two computers, a 
>> windows run laptop and my linux box - using two bluetooth usb dongles
>> I think the problem is quite obvious: they both have been assigned the 
>> same bd address: 11:11:11:11:11:11
>> whatever I try, both devices still have the same bd addresses leading 
>> even to a situation like this (when connected to the same PC):
> 
> this is a known problem and it is these stupid ISSC dongles where the
> manufacturer doesn't assigned unique addresses to each dongle. You can
> try to use bdaddr from CVS to set your own address.

Hi, thanks for the fast reply, but unluckily that didn't help

szift@szift:~/blue/utils/test$./bdaddr -i hci0 22:22:22:22:22:22
Manufacturer:   Integrated System Solution Corp. (57)
Device address: 11:11:11:11:11:11
New BD address: 22:22:22:22:22:22

Can't write new address

But if I could give You any debug data that could be usefull, just let 
me know

and btw. Your web-based cvs viewer is down - I had to check the cvs 
history and guess to get the right module name ;]

--
Best wishes
Lukasz 'Szift' Hejnak


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] BD hardware address problem
  2006-07-16 23:02   ` Łukasz Hejnak
@ 2006-07-17  0:09     ` ?ukasz Hejnak
  2006-07-17  6:28       ` Marcel Holtmann
  0 siblings, 1 reply; 5+ messages in thread
From: ?ukasz Hejnak @ 2006-07-17  0:09 UTC (permalink / raw)
  To: BlueZ users

?ukasz Hejnak napisa?(a):
>>> I've been trying to make a bluetooth link between two computers, a 
>>> windows run laptop and my linux box - using two bluetooth usb dongles
>>> I think the problem is quite obvious: they both have been assigned the 
>>> same bd address: 11:11:11:11:11:11
>> this is a known problem and it is these stupid ISSC dongles where the
>> manufacturer doesn't assigned unique addresses to each dongle. You can
>> try to use bdaddr from CVS to set your own address.

> Can't write new address

of course it couldn't, I wasn't root ;]
after executing this set of commands
bdaddr -r -i hci0 22:22:22:22:22:22
hciconfig hci0 down
hciconfig hci0 up
I got the device up and going with the new address and the rest of my 
config, then I fired up:
pand -c 11:11:11:11:11:11
but now it ends with:
Connect to 11:11:11:11:11:11 failed. Protocol error(71)
and I'm stuck again ;]

--
Best wishes
Lukasz 'Szift' Hejnak


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] BD hardware address problem
  2006-07-17  0:09     ` ?ukasz Hejnak
@ 2006-07-17  6:28       ` Marcel Holtmann
  0 siblings, 0 replies; 5+ messages in thread
From: Marcel Holtmann @ 2006-07-17  6:28 UTC (permalink / raw)
  To: BlueZ users

Hi Lukasz,

> >>> I've been trying to make a bluetooth link between two computers, a 
> >>> windows run laptop and my linux box - using two bluetooth usb dongles
> >>> I think the problem is quite obvious: they both have been assigned the 
> >>> same bd address: 11:11:11:11:11:11
> >> this is a known problem and it is these stupid ISSC dongles where the
> >> manufacturer doesn't assigned unique addresses to each dongle. You can
> >> try to use bdaddr from CVS to set your own address.
> 
> > Can't write new address
> 
> of course it couldn't, I wasn't root ;]
> after executing this set of commands
> bdaddr -r -i hci0 22:22:22:22:22:22
> hciconfig hci0 down
> hciconfig hci0 up
> I got the device up and going with the new address and the rest of my 
> config, then I fired up:
> pand -c 11:11:11:11:11:11
> but now it ends with:
> Connect to 11:11:11:11:11:11 failed. Protocol error(71)
> and I'm stuck again ;]

use a valid BD_ADDR and not an address that will be a broadcast address
in the Ethernet range. Also run "hcidump -X -V" to see what is really
going on.

Regards

Marcel




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-07-17  6:28 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-16 22:10 [Bluez-users] BD hardware address problem Łukasz Hejnak
2006-07-16 22:20 ` Marcel Holtmann
2006-07-16 23:02   ` Łukasz Hejnak
2006-07-17  0:09     ` ?ukasz Hejnak
2006-07-17  6:28       ` Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).