29 Jul
2013
29 Jul
'13
12:50 a.m.
Hi!
Local mesh should use batman-adv for simpler approach
to the user and goodies
like clients roaming, then those local meshes talk each other with BMX6
installed on gateways,
See. This point I don't understand. How exactly will this work. Let's
have a concrete example. We have two gateways in the network, one
default towards the Internet and one towards another mesh:
Internet
.
.
.
[gateway 1]
|
------------ ------------
| | | |
| mesh 1 |------[gateway 2]------| mesh 2 |
| | | |
------------ ------------
Mesh 1 is using (let's say we use IPv4) 10.1/16 and mesh 2 10.2/16.
When I connect with my laptop to mesh 1 I get with DHCP IP from 10.1/16
and for default gateway IP of gateway 1. Now, how can my laptop know
that for 10.2/16 it should route towards IP of gateway 2?
And moreover, why is there even a node for a wireless routing protocol
for this peering between mesh 1 and mesh 2? Wouldn't any routing
protocol (like BGP) be quit the same: nor BGP nor BMX6 would know
anything about underlying link quality *below* the Batman.
BMX6 will do the tunnelling too with double gain
1) You don't need to configure the vpn
So you mean tunnels are done automatically between all nodes in the
mesh? In a way similar to n2n (http://www.ntop.org/products/n2n/)?
2) BMX6 known exactly the real topology of tunnels so
can take better decision
in respect to other routing protocols that run on top of VPNs
This really just depends on how you configure your VPN. Even when we
were using OpenVPN, we just configured it so that all VPN tunnels were
not bridged together. This is the important step. If you have:
[node A]----[VPN server]----[node B]
L3 (or L2) routing protocol should not think that there is a direct link
between node A and node B. We were able to configure OpenVPN and n2n in
this way, so I am not sure this is a big problem with VPN solutions.
( If i undestood good tunnel made with tunnel digger
doesn't suffer
this problem because are just tunnel not VPN )
Yes, Tunneldigger rocks. :-) But from other reasons. You should
experience how it traverses NATs and firewalls and setups two-way
bandwidth limiting. :-)
(I think "tunnels" and "VPNs" are not the best defined terms here. I
am
not 100% sure what you meant here by them. But I assume with VPN you
mean something which combines all VPN clients into one big L2 network.)
Any way i think we should stop duplicatin work...
we have N map server, N firmware, N monitoring protocols and so on...
I agree completely. :-) We just have to agree on what we want to build
together. And for that such discussion (even if they consume a lot of
time) are important. We have to first understand each other.
If we can join forces this would be a big gain and so
we can have forces to
develop other kind of things too, just to trhow an example serverless
decentralized secure communication platform to use in the mesh...
You know that I am and always have been a big proponent of joining
forces. And this is why I am trying and taking time to understand what
is this new idea of combining Batman and BMX. I just don't get it.
Mitar
--
http://mitar.tnode.com/
https://twitter.com/mitar_m