Return-Path: Message-ID: From: Robert Wlaschin To: "'Marcel Holtmann'" Cc: "'bluez-devel@lists.sourceforge.net'" Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm Date: Wed, 5 Oct 2005 11:38:07 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5C9DB.EDB79760" List-ID: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C5C9DB.EDB79760 Content-Type: text/plain; charset="iso-8859-1" Marcel, Thanks, that seems to get rid of the Authentication error. I seem to be able to issue commands through microcom now. I appreciate the help. Is there a recommended way to verify the linkkey isn't incorrect? Thanks, Robert -----Original Message----- From: Marcel Holtmann [mailto:marcel@holtmann.org] Sent: Wednesday, October 05, 2005 10:54 AM To: Robert Wlaschin Cc: 'bluez-devel@lists.sourceforge.net' Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm Hi Robert, > much for the help thus far. Yes the rfcomm0 device is created: > This is the output from rfcomm; rfcomm0: 00:A0:96:0D:3B:80 channel 1 > closed, I have also seen it report [tty-attached] when I am attempting > to read/write/connect, but it says 'config' not 'open' > > So, I saw this error message: > > > HCI Event: Connect Complete (0x03) plen 11 > status 0x05 handle 41 bdaddr 00:A0:96:0D:3B:80 type ACL encrypt > 0x00 > Error: Authentication Failure this means that you provide the wrong link key. Delete all your link keys or set the device into pairing mode. > So I did this: hciconfig hci0 auth, but I still got the same error, so > I followed with this: hciconfig hci0 encrypt, but I still seem to be > getting the error message. This is a misconception. What activated security mode 3 and this is not helpful at all. Regards Marcel ------_=_NextPart_001_01C5C9DB.EDB79760 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [Bluez-devel] Cannot send through serial device = rfcomm

Marcel,

Thanks, that seems to get rid of the Authentication = error.  I seem to be able to issue commands through microcom = now.

I appreciate the help.  Is there a recommended = way to verify the linkkey isn't incorrect?

Thanks,
Robert

-----Original Message-----
From: Marcel Holtmann [mailto:marcel@holtmann.org]
Sent: Wednesday, October 05, 2005 10:54 AM
To: Robert Wlaschin
Cc: 'bluez-devel@lists.sourceforge.net'
Subject: RE: [Bluez-devel] Cannot send through = serial device rfcomm


Hi Robert,

> much for the help thus far.  Yes the = rfcomm0 device is created:
> This is the output from rfcomm; rfcomm0: = 00:A0:96:0D:3B:80 channel 1
> closed, I have also seen it report = [tty-attached] when I am attempting
> to read/write/connect, but it says 'config' not = 'open'
>
> So, I saw this error message:
>
> > HCI Event: Connect Complete (0x03) plen 11 =
>     status 0x05 handle 41 = bdaddr 00:A0:96:0D:3B:80 type ACL encrypt
> 0x00
>     Error: Authentication = Failure

this means that you provide the wrong link key. = Delete all your link
keys or set the device into pairing mode.

> So I did this: hciconfig hci0 auth, but I still = got the same error, so
> I followed with this: hciconfig hci0 encrypt, = but I still seem to be
> getting the error message.

This is a misconception. What activated security mode = 3 and this is not
helpful at all.

Regards

Marcel

------_=_NextPart_001_01C5C9DB.EDB79760--