From: The Doctor <drwho@virtadpt.net>
To: Juliusz Chroboczek <jch@pps.jussieu.fr>
Cc: b.a.t.m.a.n@open-mesh.net,
Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>,
babel-users@lists.alioth.debian.org
Subject: Re: [B.A.T.M.A.N.] Battlemesh-like experiment in Washington, DC
Date: Mon, 08 Aug 2011 15:05:11 -0400 [thread overview]
Message-ID: <4E403367.4060701@virtadpt.net> (raw)
In-Reply-To: <7ibown8v2j.fsf@lanthane.pps.jussieu.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/21/2011 12:20 PM, Juliusz Chroboczek wrote:
I am sorry this reply has been so delayed, work has been rough lately.
> Oh yeah, there should be no problem in a layer 2 mesh, if the mesh
> implements broadcast (or hacks in some ad hoc smarts related to DHCP).
> AHCP is only needed in a layer 3 mesh.
We also have a solution worked out for layer 3 meshes. We will be using
DHCP to configure clients, and our control panel application can
pseudo-randomly choose RFC-1918 IP addresses for mesh interfaces if the
user selects it. AHCP is still an option for configuring other mesh
nodes, we have not yet implemented that.
- --
The Doctor [412/724/301/703]
PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: http://drwho.virtadpt.net/
"Take back, take back, take back the dancefloor!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5AM2cACgkQO9j/K4B7F8ERngCePSd8L2smWq5phMwX3ryy8ZFV
j9AAnjcCwcJuq+kcfOlyb8caXYLlUupn
=/kkF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-08 19:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 13:42 [B.A.T.M.A.N.] Battlemesh-like experiment in Washington, DC Juliusz Chroboczek
2011-07-16 15:34 ` Marek Lindner
2011-07-18 17:41 ` The Doctor
2011-07-20 17:25 ` The Doctor
2011-07-20 18:55 ` Juliusz Chroboczek
2011-07-21 14:35 ` The Doctor
2011-07-21 16:20 ` Juliusz Chroboczek
2011-08-08 19:05 ` The Doctor [this message]
2011-08-09 11:35 ` [B.A.T.M.A.N.] [Battlemesh] " Mitar
2011-08-09 16:51 ` The Doctor
2011-08-09 20:13 ` Juliusz Chroboczek
2011-08-10 16:31 ` The Doctor
2011-08-09 21:04 ` Mitar
2011-08-10 16:38 ` The Doctor
2011-08-10 16:53 ` Mitar
2011-08-10 17:47 ` [B.A.T.M.A.N.] [Babel-users] " haxwithaxe
2011-08-10 21:54 ` Mitar
[not found] ` <CAEVTcgUMYVjHbNnP8wBBsGEtAoH+BNW3G1vBoktDoOPMDcsoQw@mail.gmail.com>
2011-08-10 16:53 ` [B.A.T.M.A.N.] " 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=4E403367.4060701@virtadpt.net \
--to=drwho@virtadpt.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=b.a.t.m.a.n@open-mesh.net \
--cc=babel-users@lists.alioth.debian.org \
--cc=battlemesh@ml.ninux.org \
--cc=jch@pps.jussieu.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.