Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] scanning possible, but no l2ping?
Date: Sat, 29 Jan 2005 04:50:55 +0100	[thread overview]
Message-ID: <1106970655.10735.2.camel@pegasus> (raw)
In-Reply-To: <41FB066B.3080904@coriand.com>

Hi Franz,

> Securty Mode 3 is not safty, isn't it ;) My problem is, I need a f***
> connection between Watch and computer for a special live-demo in a
> closed lab.

the security mode 3 is not more safe than security mode 2.

> And the next problem is that pairing doesn't work with the watch, so I
> turned everything off. So all I need is just a connection to send tcp
> packages - I don't care about the secury.

You must switch "auth" and "encrypt" off on _both_ sides. If one device
is in security mode 3 than the other must follow. This is how security
mode 1 is definied in the specification.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-01-29  3:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29  3:25 [Bluez-users] scanning possible, but no l2ping? Franz Coriand
2005-01-29  3:33 ` Marcel Holtmann
2005-01-29  3:43   ` Franz Coriand
2005-01-29  3:50     ` Marcel Holtmann [this message]
2005-01-29  4:40       ` Franz Coriand

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=1106970655.10735.2.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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