public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
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: Fri, 11 Dec 2009 14:33:54 +0100	[thread overview]
Message-ID: <20091211133353.GA2708@Linus-Debian> (raw)
In-Reply-To: <375210.41936.qm@web111602.mail.gq1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

Hi George,

if you are really talking about "and is simply a client talking to other clients" as you said before, then IPv6 autoconf is the way to go as Andrew mentioned before.
> Are any freifunk networks purely peer-to-peer, without any "server" or "core" nodes ?
> 
> That is, are any freifunk networks using ipv6 autoconf, or zeroconf ?
Here in Lübeck we are currently experimenting with such an IPv6-mesh-only network. Because of BTM-Adv a completely adhoc ip-assignment is possible as long as your mac adresses in your network are unique (as they should be). If it were just for communications inside of the mesh without any routing from this mesh to hosts outside of the mesh, you can even use the automatically assigned link-local adresses - this is working out of the box in most current operating systems.

So basically our intention is to not have the mesh network as an uplink directly to the internet but more as a dedicated metropolitan area network, a switched "LAN". In this MAN everyone shall be free to set up VPNs for their internet gateway / to their home network. Of course this is a trade-off about usability on the other hand as setting up a VPN is not a trivial task for "common" people... but don't know what your specific goal is. Could you expain your intention a little further maybe?

We were also running in some trouble with those link-local adresses, not all applications seem to support this properly. Therefore we were assigning additional ipv6 unique local addresses with the help of radvd (and limited this to the local wifi/ethernet clients on one router with the help of ebtables). (this should also be possible with dhcpv6 instead of using radvd though, I guess)


I'm not aware of any routing protocol supporting dynamic, decentral ipv4+6 internet gatewaying over a ipv6-only mesh network yet. Though there are discussions about how this could be achieved on the BATMAN-Adv side as well. I'm also curious about what the Berlin Freifunk guys are up to with NIIT, gotta have a look at the workshop/discussion during the 26c3. Has anyone heard of IVI (or totd) yet? I think this should make routing packets between the ipv4 and ipv6 stack possible.

Cheers, Linus

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-12-11 13:33 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 [this message]
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=20091211133353.GA2708@Linus-Debian \
    --to=linus.luessing@web.de \
    --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