From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: b.a.t.m.a.n@lists.open-mesh.net
Cc: George Sanders <gosand1982-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Subject: Re: [B.A.T.M.A.N.] general theory question RE: dhcp on a peer only mesh
Date: Thu, 31 Dec 2009 02:44:52 +0100 [thread overview]
Message-ID: <87eimbyl0r.fsf@trurl.pps.jussieu.fr> (raw)
In-Reply-To: <391345.99048.qm@web111612.mail.gq1.yahoo.com> (George Sanders's message of "Tue, 8 Dec 2009 20:24:01 -0800 (PST)")
> Who provides IP addresses in a truly ad-hoc, truly "peer only" mesh
> network ?
Nobody, as far as I know.
You may want to have a look at AHCP[1], however. When configured for
IPv6 only, it gets configuration information (such as the IPv6 prefix
and the name server address) from central servers, but behaves in
a completely stateless manner -- there is no information stored in the
servers.
In IPv4, however, it uses leases, just like DHCP, so it needs to store
state in the servers.
> Please do point me to any writings or information related to this.
Search for draft-bernardos-manet-autoconf-survey.
Juliusz
[1] http://www.pps.jussieu.fr/~jch/software/ahcp/
prev parent reply other threads:[~2009-12-31 1:44 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
2009-12-31 1:44 ` Juliusz Chroboczek [this message]
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=87eimbyl0r.fsf@trurl.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--cc=gosand1982-/E1597aS9LQAvxtiuMwx3w@public.gmane.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