From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<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: Wed, 9 Dec 2009 07:34:11 +0100 [thread overview]
Message-ID: <20091209063411.GJ29768@lunn.ch> (raw)
In-Reply-To: <391345.99048.qm@web111612.mail.gq1.yahoo.com>
On Tue, Dec 08, 2009 at 08:24:01PM -0800, 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 ?
One option is IPv6 and link local addresses. These are derived from
the MAC address, plus duplicate address detection, to ensure the IP
address is unique. http://tools.ietf.org/html/rfc4862
Another option is zeroconf, http://en.wikipedia.org/wiki/Zeroconf,
http://tools.ietf.org/html/rfc3927.
Another option is statically configure all the boxes with a unique IP
address from a well know subnet. It is often worth remembering that a
truly ad-hoc, truly "peer only" mesh network is used within some sort
of organization. The organization can impose management rules.
Andrew
next prev parent reply other threads:[~2009-12-09 6:34 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 [this message]
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
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=20091209063411.GJ29768@lunn.ch \
--to=andrew@lunn.ch \
--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