Linux bluetooth development
 help / color / mirror / Atom feed
From: Steffen Becker <steffen.becker@tu-ilmenau.de>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Encrypting problem while sending data via bluetooth
Date: Thu, 15 Mar 2012 09:59:55 +0100	[thread overview]
Message-ID: <4F61AF8B.3020300@tu-ilmenau.de> (raw)
In-Reply-To: <1331747344.14217.105.camel@aeonflux>

Thank you very much, this helped me!
Now everything looks fine on the screen of the "PC2".

But now i got another problem regarding to this:
I use a third PC with the "BPA500" (it's for bluetooth sniffing).
When i use again the command

PC1: # echo "test" > /dev/rfcomm0

then the BPA500 software says:
"100% Payload/CRC Errors"
and it can't go after "start_encrypt_req" (that's the last Opcode in the 
Link Management Protocol).

That's why i still think i have an encryption problem.
But the manpage only shows me how to ENable the encryption.

So i hope somebody can help me a second time.

Regards,
Steffen


Am 14.03.2012 18:49, schrieb Marcel Holtmann:
> Hi Steffan,
>
>> At first: Sorry for my bad english, it's not my native language. So i
>> wrote my problem in german and english.
>>
>> My problem refers to bluez. I didn't got useful hits on Google, IRC
>> didnt help and the only answer i got in a forum was: "there are not many
>> people who are familiar with that". So i hope you can help me.
>>
>> My problem:
>> After installing the latest bluez, i connected two gentoo-PC's (v2.1.6)
>> via two bluetooth-dongles (BT3.0).
>> PC2:# rfcomm listen 0 1
>> PC1:# rfcomm connect 0<bluetooth-adress>  1
>> This works fine.
>>
>> But now, when i try to send some data:
>> PC2:# cat /dev/rfcomm0
>> PC1:# echo "test">  /dev/rfcomm0
>> it looks like this on the screen of PC2:
>> "^J^J^J^J^^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^test^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J^J"
> it has nothing to do with encryption. These are TTY terminal settings.
> That is why rfcomm tool has a -r (raw TTY mode) switch. And that switch
> is documented in manpage.
>
> Regards
>
> Marcel
>
>



  reply	other threads:[~2012-03-15  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 14:59 Encrypting problem while sending data via bluetooth Steffen Becker
2012-03-14 17:49 ` Marcel Holtmann
2012-03-15  8:59   ` Steffen Becker [this message]
     [not found]     ` <CAHBqpz8=MoK9LFMJp1N8K7iv98hCwG3nU47vh9eyNN+AbunLmA@mail.gmail.com>
2012-03-15 11:08       ` james.steele
2012-03-15 11:46         ` Andrei Emeltchenko
2012-03-19  8:49         ` Steffen Becker
2012-03-15 11:27     ` Vijaykumar Dadmode

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F61AF8B.3020300@tu-ilmenau.de \
    --to=steffen.becker@tu-ilmenau.de \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox