public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: tOpSy TuRvY <topsyturvy@nemo.student.utwente.nl>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BT_ADDR Address Resolution
Date: Thu, 24 Jun 2004 14:54:10 +0200	[thread overview]
Message-ID: <1088081650.4296.63.camel@pegasus> (raw)
In-Reply-To: <Pine.BSO.4.58.0406241437430.23390@nemo.student.utwente.nl>

Hi Assed,

> > the Linux PAN is a point-to-point connection. If you want to build a NAP
> > or GN you must also use the Linux bridge. So this is not a PAN question,
> > this depends on how you configured your bridge.
> 
> You are right, it was a bridge question. I think it would be fair to 
> assume that the bridge is going to forward all broadcast traffic it 
> recieves on all the ports (except the one it came on).

depends on your bridge configuration ;)

> > No Bluetooth broadcast is used. Read the BNEP and PAN specifications.
> 
> Read those and tried to understand them. What I gathered is that there 
> will be one Bluetooth broadcast sent to each of the connected PANUs. i.e. 
> one Bluetooth broadcast sent on each bridge port, and that seems very 
> wasteful since just one bluetooth broadcast on any port would have been 
> recieved by all the PANUs right?

Bluetooth PAN is point-to-point. It is like that you replace the CAT-5
cable between your machine and the switch with a Bluetooth connection.
Everything else is then TCP/IP specific.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-06-24 12:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1BcqIi-0002cT-53@sc8-sf-list2.sourceforge.net>
2004-06-22 18:57 ` [Bluez-users] Max Number of PANUs supported in PAN tOpSy TuRvY
2004-06-22 21:30   ` Marcel Holtmann
2004-06-22 22:07     ` tOpSy TuRvY
2004-06-22 22:14       ` Marcel Holtmann
2004-06-23 11:23         ` [Bluez-users] Slaves in Sniff mode tOpSy TuRvY
2004-06-23 12:06           ` Peter Stephenson
2004-06-23 12:16           ` Marcel Holtmann
2004-06-23 12:58             ` tOpSy TuRvY
2004-06-23 13:30               ` Marcel Holtmann
2004-06-23 16:06               ` Peter Stephenson
2004-06-23 16:33                 ` Marcel Holtmann
2004-06-23 17:15                 ` tOpSy TuRvY
2004-06-23 17:41                   ` Peter Stephenson
2004-06-24  9:43                     ` tOpSy TuRvY
2004-06-24 10:09                       ` Peter Stephenson
2004-06-24 11:39                         ` [Bluez-users] BT_ADDR Address Resolution tOpSy TuRvY
2004-06-24 12:06                           ` Marcel Holtmann
2004-06-24 12:26                             ` tOpSy TuRvY
2004-06-24 12:31                               ` Marcel Holtmann
2004-06-24 12:46                                 ` tOpSy TuRvY
2004-06-24 12:54                                   ` Marcel Holtmann [this message]
2004-06-23 17:59                   ` [Bluez-users] Slaves in Sniff mode Marcel Holtmann
     [not found] <E1BdWwI-0003pn-Dn@sc8-sf-list2.sourceforge.net>
2004-06-24 19:43 ` [Bluez-users] BT_ADDR Address Resolution Michael Schmidt

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=1088081650.4296.63.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=topsyturvy@nemo.student.utwente.nl \
    /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