Hi!
2012/4/14 Nicolás Echániz nicoechaniz@codigosur.org:
I'm curious as to why those nodes wouldn't use the same IP address space as the net if they will be announcing their routes to the mesh anyway.
Probably they will use the same IP address space, but we want to route those subnets not bridge them. This is the main difference.
One thing to be aware of is that when a home network (on a different subnet) is connected to the batman mesh you get some side-effects, like for example an in-house router responding to DHCP requests...
If we do routing between home network and mesh network, no.
Also, our routers will not run DHCP itself. (Probably DHCP will be run inside home networks. But as I said, we would like to only route there, not bridge.)
One other suggestion, for VPN is to take a look at Tinc; it has a routing (or router?) mode which might be useful in your case.
No, it is an user-space daemon. Context switches between user-space and kernel-space kills much of the performance on those cheap routers. We are currently using OpenVPN and I doubt Tinc will improve much in this aspect. Or am I mistaken?
Mitar