[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] encryptions problem ?

Hi Matthias,

I've just experienced the same behaviour with a different (Ubicom 
ipBlue) Bluetooth stack where my Motorola card (IBM, Motorola and 
Toshiba are all essentially the same) stopped in the same way on one of 
my laptops.  Fortunately I found that the same card still worked fine in 
another laptop and a 3Com card worked in both.

I'm not entirely sure which setting needed to be changed to clear the 
problem, but here's what I now have set in the Bluetooth Neighbourhood 
Properties on both laptops - both are now working fine again:


Trust Relationship: "Prompt before accepting link establishment"

"Apply to all devices".


Security Mode: "No security"

Connectability Mode: "Connectable mode"

Discoverability Mode: "General discoverable mode"


Bluetooth Bonding: "Bondable mode"

Default Bluetooth Bonding Expiration: "Bonding is never expired"

"Apply to all devices"

Hope this helps,

Matthias Fuchs wrote:
> Hi,
> again, in general everything works fine :-)
> But when I try to connect to my OpenBT device through the DUP profile 
> from my IBM PCMCIA card (BT spec 1.1) connecting fails. Connecting to a 
> serial port works fine, also SDP and so on is fine.
> I gave a glance to the log files and noticed an ENCRYPTION CHANGE EVENT 
> on my OpenBT device. This is the last that happens before the client 
> throws the "connection failed" message.
> I have a simple security manager and the ..._USE_SECURITY_MANAGER define 
> ist defined. My current sec_man implementation does not do anything when 
> receiving a sec_man_event with the ENCRYPTION_CHANGE event.
> Does it have something to do ?
> As I understood, when a device receives the above evenet, encryption is 
> correctly setup and therefore I do not have to do anything upon 
> receiving this event, am I right ?
> Is there a simple way to tell the client side, that I do not want any 
> encryption ? I did not find anything in the spec about this.
> By the way, I can rember that DUP was working fine again the IBM card 
> some time ago. I am not really sure if it is a problem with my Ericsson 
> modules. I changed from the ROK101008 to ROK101007.
> Any hints ?
> By the way: There's a little "cut-copy-paste-typo" in hci.c:
>     if(r_val[0]) {
>            get_err_msg(r_val[0]));
>            result_param = -r_val[0];
>            }
>      break;
> Matthias

To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com