From: "menno van der klein" <jongerenchaos@zonnet.nl>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluez 4.XX pincode authorisation HOW can i use it??
Date: Fri, 17 Oct 2008 22:06:02 +0200 (CEST) [thread overview]
Message-ID: <12941.83.160.35.87.1224273962.squirrel@webmail.xs4all.nl> (raw)
Great it works well!! Thank you very much for your help!
> Johan Hedberg wrote:
>> Hi,
>>
>> If you want to pair devices from the command line you can e.g. use the
>> simple-agent python script (in the test subdirectory of bluez):
>> ./simple-agent hci0 <remote address>
>> It will ask you for the pin on stdin.
>>
>> Johan
>
> Thank you Johan that helped a lot with one of my devices,
>
> python .simple-agent.py hci0 00:1A:80:AB:0A:B1
>
> the simple-agent script can be found at the bluez git in its testing
> directory: git://git.kernel.org/pub/scm/bluetooth/bluez.git
>
> Best regards,
>
> Jelle
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
Met vriendelijke groet,
Menno van der Klein
CreditFUN Media
T: 020-8005157
M: 06-28927919
E: Menno@creditfun.nl
Disclaimer
De informatie verzonden in dit e-mail bericht is uitsluitend bestemd voor
de geadresseerde. Gebruik van deze informatie door anderen dan de
geadresseerde is verboden. Openbaarmaking, vermenigvuldiging, verspreiding
en/of verstrekking van deze informatie aan derden is niet toegestaan.
Hoewel bij de verzending van dit e-mail bericht de nodige zorgvuldigheid
wordt betracht, is een juiste en volledige overdracht van dit e-mail
bericht niet te garanderen. Aan dit e-mail bericht en/of meegezonden
bestanden kunnen geen rechten worden ontleend. Daarnaast kan CreditFUN
Media,of aan haar gelieerde ondernemingen, niet aansprakelijk gehouden
worden voor de gevolgen van eventuele fouten en/of onvolledigheid van de
in het e-mail bericht opgenomen gegevens.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-10-17 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 20:06 menno van der klein [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-16 19:58 [Bluez-users] Bluez 4.XX pincode authorisation HOW can i use it?? menno van der klein
2008-10-16 21:15 ` Jelle de Jong
2008-10-16 21:34 ` Johan Hedberg
2008-10-16 22:20 ` Jelle de Jong
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=12941.83.160.35.87.1224273962.squirrel@webmail.xs4all.nl \
--to=jongerenchaos@zonnet.nl \
--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