From: "Claudio Takahasi" <cktakahasi@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] restricting inquiry responses
Date: Wed, 13 Sep 2006 09:48:46 -0300 [thread overview]
Message-ID: <e1effdeb0609130548h1a6dea73vef4a6a8dc8b08d5e@mail.gmail.com> (raw)
In-Reply-To: <e1effdeb0609130523g204fff2fk80a0786e92f81d89@mail.gmail.com>
On 9/13/06, Claudio Takahasi <cktakahasi@gmail.com> wrote:
> On 9/12/06, Loreno Oliveira <lorenooliveira@gmail.com> wrote:
> > Hi there,
> >
> > I have different base stations that permanently try to find out new mobile
> > devices on their coverage areas. Once discovered and paired with some BS, I
> > need this device to be able to not answer to that BS inquiries.
> >
> > Is there a solution for this??
> >
> > Regards,
> >
> > Loreno
> _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> Hi Loreno,
>
> You can use the a D-Bus method to switch the device to "Connectable"
> mode. The adapter interface supports the following discoverable modes:
> discoverable: PSCAN ISCAN
> connectable: PSCAN
> off: NOSCAN
>
> Use the gbluezconf(test app) to setup this mode:
> http://www.maemo.org.br/cktakahasi/gbluezconf/gbluezconf-00.32.tar.gz
>
> Or dbus-send:
> $dbus-send --system --type=method_call --print-reply --dest=org.bluez
> /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:0
> $dbus-send --system --type=method_call --print-reply --dest=org.bluez
> /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable
>
> The default discoverable timeout is 180sec. Setting it to 0 +
> discoverable mode to "discoverable" the device will be always visible.
> Setting the discoverable timeout to X + mode to discoverable, the mode
> will be changed automatically to connectable mode after X seconds.
>
>
> BR,
> Claudio.
> --
> ---------------------------------------------------------
> Claudio Takahasi
> Instituto Nokia de Tecnologia - INdT
>
Hi Loreno,
Sorry, I misunderstood your question. It's not possible "not answer"
to a specific BS inquiries.
BR,
Claudio.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-09-13 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 16:41 [Bluez-users] restricting inquiry responses Loreno Oliveira
2006-09-13 12:23 ` Claudio Takahasi
2006-09-13 12:48 ` Claudio Takahasi [this message]
2006-09-13 12:56 ` Loreno Oliveira
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=e1effdeb0609130548h1a6dea73vef4a6a8dc8b08d5e@mail.gmail.com \
--to=cktakahasi@gmail.com \
--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