From: Marco Pracucci <development@pracucci.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] ioctl: setting link mode and link policy
Date: Thu, 31 Aug 2006 16:42:05 +0000 [thread overview]
Message-ID: <44F7115D.6080700@pracucci.com> (raw)
In-Reply-To: <1157041796.4026.133.camel@aeonflux.holtmann.net>
Hi Marcel,
>> I would like to set a "global" link mode and link policy that will be
>> the default for every connection. Something similar to hcid.
>>
> what do you expect from doing this? It is not a good idea to change it
> globally except you know exactly what you are doing. Changes these
> settings can have implications you might not be aware of. So what is
> your purpose on changing them?
>
I would become master on incoming connections and I would deny role
switch on outgoing connections. If I'm not wrong, I should set MASTER as
link mode and disable role switch from link policy. However, I can't use
hcid, so I would do this from a custom application.
Is it possible?
Thanks,
Marco
-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-08-31 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 13:59 [Bluez-devel] ioctl: setting link mode and link policy Marco Pracucci
2006-08-31 12:18 ` Peter Wippich
2006-08-31 15:15 ` Marco Pracucci
2006-08-31 16:29 ` Marcel Holtmann
2006-08-31 16:42 ` Marco Pracucci [this message]
2006-08-31 19:23 ` Marcel Holtmann
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=44F7115D.6080700@pracucci.com \
--to=development@pracucci.com \
--cc=bluez-devel@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