public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Schmidt <schmidt@nue.et-inf.uni-siegen.de>
To: topsyturvy@nemo.student.utwente.nl
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] BT_ADDR Address Resolution
Date: Thu, 24 Jun 2004 21:43:55 +0200	[thread overview]
Message-ID: <40DB2EFB.6060000@nue.et-inf.uni-siegen.de> (raw)
In-Reply-To: <E1BdWwI-0003pn-Dn@sc8-sf-list2.sourceforge.net>

Hi Assed,

If BlueZ hasn't introduced a mechanism of its own recently, there is no 
dedicated BueZ IP address assignment mechanism. Of course, you may use 
DHCP if a suitable server is available.

The Bluetooth PAN specification ("Personal Area Networking Profile 
v1.0") recommends the "Zero Configuration Networking (Zeroconf)" 
standard (http://www.zeroconf.org/) with 
draft-ietf-zeroconf-ipv4-linklocal-02.txt (or actually one of its 
successors) as instant ("zero configuration") IP address assignment 
algorithm. The code for UNIX (called 'zcip') used to be available at 
http://zeroconf.sourceforge.net/?selected=zcip, but currently there seem 
to be intellectual property problems with it (see explanation on web 
page), so that the code has been removed. Actually it creates an IP 
address out of the 169.254/16 address range with a mathematical 
transform that is seeded by the network adapter's MAC address. It 
queries for potential collisions via AR, and defends an assigned IP 
address against subsequent collisions via ARP.


Hope this helps,

Michael


> Does anyone know how IP addresses in the Bluez PAN get resolved to 
> BT_ADDRs that will be used by BNEP? Is there an ARP broadcast (i.e. query 
> like slave -> master -> broadcast to all slaves) or some sort of proxy ARP
> mechanism at master (e.g. query from slave->master and then a reply 
> master->slave).
> 
> 
> Thanks,
> Assed

-- 
=================================================
Michael Schmidt
-------------------------------------------------
Institute for Data Communications Systems
University of Siegen, Germany
-------------------------------------------------
http:   www.nue.et-inf.uni-siegen.de
e-mail: schmidt@nue.et-inf.uni-siegen.de
mobile: +49 179 7810214
=================================================


-------------------------------------------------------
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 19:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1BdWwI-0003pn-Dn@sc8-sf-list2.sourceforge.net>
2004-06-24 19:43 ` Michael Schmidt [this message]
2004-06-24 10:09 [Bluez-users] Slaves in Sniff mode 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

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=40DB2EFB.6060000@nue.et-inf.uni-siegen.de \
    --to=schmidt@nue.et-inf.uni-siegen.de \
    --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