From: Troy Benjegerdes <hozer@hozed.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] "Distributed" DHCP vs gateway
Date: Sat, 6 Aug 2011 09:56:08 -0500 [thread overview]
Message-ID: <20110806145555.GD20928@excalibur.hozed.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1108060959150.9094@localhost6.localdomain6>
On Sat, Aug 06, 2011 at 10:19:28AM -0400, Ryan Hughes wrote:
> So, I had a crazy idea the other day:
>
> Normally, when I talk to people about mesh networks, they assume
> that there is some central authority assigning IP addresses to nodes
> intelligently.
>
> I was thinking, though, that I'd rather have it so that every node
> could have the same firmware, and you'd just throw the node up and
> it'd negotiate everything for itself, including its IP address.
Why reinvent the wheel? I would argue that using IPv6 stateless autoconfig
http://en.wikipedia.org/wiki/IPv6#Stateless_address_autoconfiguration_.28SLAAC.29
and then working to provide a mechanism to support 'legacy' IPv4-only
clients would be a beter solution than a lot of the hoops we have to
jump through to support distributed dhcp cleanly.
My thought is every node runs radvd (ipv6 equivalent of dhcpd), and any
ipv4 traffic will get tunneled over the v6 mesh network to the closest
exit node with upstream IPv4 net access, which is where the DHCP server
would run.
next prev parent reply other threads:[~2011-08-06 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 14:19 [B.A.T.M.A.N.] "Distributed" DHCP vs gateway Ryan Hughes
2011-08-06 14:56 ` Troy Benjegerdes [this message]
2011-08-06 17:20 ` Ryan Jud Hughes
2011-08-15 21:15 ` Donald Gordon
2011-08-07 13:25 ` Marek Lindner
2011-08-08 19:15 ` The Doctor
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=20110806145555.GD20928@excalibur.hozed.org \
--to=hozer@hozed.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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