From: Florian Philipp <lists@binarywings.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: PAN with bluez-utils-3
Date: Thu, 02 Apr 2009 08:02:41 +0200 [thread overview]
Message-ID: <49D45501.8030606@binarywings.net> (raw)
In-Reply-To: <49D30FD8.9020506@binarywings.net>
Florian Philipp schrieb:
> Luiz Augusto von Dentz schrieb:
>> Hi Florian,
>>
>> On Tue, Mar 31, 2009 at 8:29 AM, Florian Philipp <lists@binarywings.net> wrote:
>>> So my question is: Does anyone have a working set of configuration files
>>> for newer bluez-utils? Preferably something related to the roles GN or NAP.
> [...]
>> To act like a server you don't need to do anything for panu, for gn we
>> normally create a bridge called pan0 where all client are added, nap
>> is especial because of the routing stuff so you/your system need to
>> configure a bridge properly and make network.conf to use it (by
>> default this should be pan1).
>>
>> Now if you got any problem you could please provide a more detailed
>> info of it, if it is a bug we will be happy to fix it.
>>
>> Thanks,
>>
>
> Thanks for your answer! I don't think it's bug but merely lack of
> understanding on my part. Therefore I'll go into detail now:
>
> Here I have a Gentoo system which shall act as the GN. Its hcid.conf
> looks like this:"
> options {
> autoinit yes;
> security auto;
> pairing multi;
> passkey "123456";
> }
> device {
> name "BlueZ (%d) at %h";
> class 0x020100;
> iscan enable; pscan enable;
> lm master;
> lp rswitch,hold,sniff,park;
> }
> "
>
> Its network.conf would then look like this (?):"
> [General]
>
> [PANU Role]
> Autostart=false
>
> [GN Role]
> Interface=blue0
> Autostart=true
>
> [NAP Role]
> Autostart=false
> "
>
> The init-script executes the following command:
> /usr/sbin/hcid -s -f /etc/bluetooth/hcid.conf
>
> What's wrong with this? When I test it with Windows clients, they fiind
> the device but it doesn't appear to have PAN functionality.
>
I'd also be happy about a response like 'It should work'. Then I could
start searching for unlogical explanations.
next prev parent reply other threads:[~2009-04-02 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 11:29 PAN with bluez-utils-3 Florian Philipp
2009-03-31 13:44 ` Luiz Augusto von Dentz
2009-04-01 6:55 ` Florian Philipp
2009-04-02 6:02 ` Florian Philipp [this message]
2009-04-02 17:28 ` Luiz Augusto von Dentz
2009-04-15 14:44 ` Florian Philipp
2009-04-16 8:49 ` CreatDevice signal should be emitted at function create_stored_device_from_profiles() in src/adapter.c Xu, Martin
2009-04-16 13:31 ` [connman] " Luiz Augusto von Dentz
2009-04-17 0:43 ` Xu, Martin
2009-04-17 1:47 ` Xu, Martin
2009-04-17 12:46 ` Luiz Augusto von Dentz
2009-04-17 13:04 ` Bastien Nocera
2009-04-17 13:08 ` Johan Hedberg
2009-04-20 0:57 ` Xu, Martin
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=49D45501.8030606@binarywings.net \
--to=lists@binarywings.net \
--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