From: elektra <onelektra@gmx.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Maintainer of vis and batmand
Date: Thu, 10 Mar 2011 11:17:11 +0100 [thread overview]
Message-ID: <201103101117.11268.onelektra@gmx.net> (raw)
In-Reply-To: <20110310065858.GA12886@lunn.ch>
Hi all -
> An option would be to move to IPv6 and use stateless address
> autoconfiguration, where the MAC address is used to form part of the
> IPv6 address. You can then easily see from the IP address which device
> it is, assuming you know its MAC address.
the background of my thoughts was how far we can get with non-technical people just taking a
bunch of Mesh-Potatoes out of the box, connecting one of them to an existing LAN segment with
DHCP and Internet uplink. The setup should allow them to make calls amongst each other and
simplifying the gateway setup, so they can use the Internet and make international calls. The
MPs should also have a Accesspoint VAP.
This is an attempt of squaring the circle, of course...
Having said that batman-adv is pretty powerful with this regard. I just wanted to initiate some
public brainstorming about how to solve the problem of identifying each device for debugging
purposes when using DHCP.
Writing down each devices MAC address and using IPv6 is a feasible approach, but I figure it
would be not intuitive.
However Mareks suggestion of adding a alias IP (we have a Asterisk IVR extension that can do
this) is a valid suggestion.
The requirement to enter a IP via the phone keypad is not exactly zero configuration, but given
the enormous set of features that we can offer, it is pretty close. Thanks!
Cheers,
Elektra
prev parent reply other threads:[~2011-03-10 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 17:35 [B.A.T.M.A.N.] Maintainer of vis and batmand elektra
2011-03-09 22:41 ` Marek Lindner
2011-03-09 23:12 ` elektra
2011-03-10 0:53 ` Marek Lindner
2011-03-10 6:58 ` Andrew Lunn
2011-03-10 10:17 ` elektra [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=201103101117.11268.onelektra@gmx.net \
--to=onelektra@gmx.net \
--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