From: Laurent BARBIER <lbarbier@kameleon-media.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] slave - slave talk in a piconet
Date: Thu, 03 Jan 2008 15:53:57 +0100 [thread overview]
Message-ID: <477CF705.1090006@kameleon-media.com> (raw)
In-Reply-To: <359782e70801030510p5abedbe4m6d7e129d8a5b0692@mail.gmail.com>
When you wan't to make B talk to C all need to be forward from and to A. =
Something like brctl do the job quite sufficiently.
Have a look there : http://bluez.sourceforge.net/contrib/HOWTO-PAN
section "Ethernet Bridging"
Laurent
bsd user a =E9crit :
> So, B or C has no knowledge about each other when they are slaves of =
> master A, right? Then, can I say if B want to talk with C, they need =
> higher level protocol support, such as telnet, ftp. And, all data =
> exchange will be forwarded by Master A. right?
>
> Thanks!
>
> On Jan 3, 2008 9:07 AM, guoyun <guoyun@techfaith.cn =
> <mailto:guoyun@techfaith.cn>> wrote:
>
> Hi, Brad
>
> > hey
> >
> > > If there is a piconet that has 2 slave B,C, the master is A.
> Does B
> > > know the existence of C? can B talk to C directly without
> > A(master)'s intervention?
> >
> > if they did talk to each other directly, one would have to be
> > master and you'd have a scatternet.
>
> one bluetooth could be in two or more piconet, but it just can
> play as slave _not_ master for the bluetooth clock.
>
> Please refer to Core SPEC. chapter 4.1. Piconet topology.
>
> BRs
> Yun
>
>
> ---------------------------------------------------------------------=
----
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> <mailto:Bluez-users@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bluez-users
> <https://lists.sourceforge.net/lists/listinfo/bluez-users>
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
> =
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-01-03 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 5:08 [Bluez-users] slave - slave talk in a piconet bsd user
2008-01-02 18:40 ` Brad Midgley
2008-01-03 1:07 ` guoyun
2008-01-03 13:10 ` bsd user
2008-01-03 14:53 ` Laurent BARBIER [this message]
2008-01-03 15:57 ` bsd user
2008-01-12 16:31 ` bsd user
2008-01-14 15:51 ` [Bluez-devel] Fwd: " bsd user
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=477CF705.1090006@kameleon-media.com \
--to=lbarbier@kameleon-media.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