public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Gus Wirth <gwirth79@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.net
Subject: Re: [B.A.T.M.A.N.] general theory question RE: dhcp on a peer only mesh
Date: Tue, 08 Dec 2009 22:36:52 -0800	[thread overview]
Message-ID: <4B1F4584.6000802@gmail.com> (raw)
In-Reply-To: <391345.99048.qm@web111612.mail.gq1.yahoo.com>

On 12/08/2009 08:24 PM, George Sanders wrote:
>
>
> This is not a BATMAN specific question, but I see very clueful
> chatter here and would appreciate any comments.
>
> My question is:
>
> Who provides IP addresses in a truly ad-hoc, truly "peer only" mesh
> network ?
>
> That is, if I create a pool of clients, and have no centralized
> authority of any kind - every node is a peer, and is simply a client
> talking to other clients, how does anyone get an IP address ?
>
> This assumes that there is no connection to the proper Internet and
> that this is simply a small pool of clients arranged to perform peer
> to peer networking.  But again, if it is an IP network ... how would
> you get IPs properly ?
>
> If you guess ahead of time, you will either be on different IP
> networks/subnets, or you will collide your addresses.
>
> If you have no DHCP servers, that won't work ...
>
> The only thing I can think of is that _everyone_ is a DHCP server and
> you somehow manage timing so as to decide who should get an address
> from whom ...
>
> Please do point me to any writings or information related to this.

Take a look at RFC3927. Also article on Wikipedia about Avahi 
<http://en.wikipedia.org/wiki/Avahi_%28software%29>

Gus

  parent reply	other threads:[~2009-12-09  6:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09  4:24 [B.A.T.M.A.N.] general theory question RE: dhcp on a peer only mesh George Sanders
2009-12-09  6:34 ` Andrew Lunn
2009-12-09 20:35   ` George Sanders
2009-12-09 20:42     ` elektra
2009-12-10  8:58       ` Bastian Bittorf
2009-12-11  5:44       ` George Sanders
2009-12-11 11:35         ` elektra
2009-12-16 17:05           ` Jon Roland
2009-12-16 18:43             ` Andrew Lunn
2009-12-16 21:55               ` Jon Roland
2009-12-16 22:37                 ` L. Aaron Kaplan
2009-12-11 13:33         ` Linus Lüssing
2009-12-10  9:59     ` Benjamin Henrion
2009-12-10 13:44       ` Bastian Bittorf
2009-12-09  6:36 ` Gus Wirth [this message]
2009-12-31  1:44 ` Juliusz Chroboczek

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=4B1F4584.6000802@gmail.com \
    --to=gwirth79@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.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