[Battlemesh] Network configuration and address plan for Battlemesh v9

Antonio Quartulli antonio at meshcoding.com
Tue Aug 11 14:42:36 CEST 2015

Hi Henning,

for the batman-adv bits:

On 11/08/15 12:54, Henning Rogge wrote:
> batman-adv:
> -----------
> no addresses on:                eth0.1, eth0.2,  wlan0, wlan1, bat0
> bat0 mesh interfaces:           eth0.2, wlan0, wlan1
> bridged interfaces:             bat0, eth0.1
> bridge addresses:
>         172.17.<id>.201/32, 172.17.<id>.202/32, 172.17.<id>.203/32
>         172.17.<id>.1/24 or 172.17.<id>.1/16 ?

Given that the mesh is just one big broadcast domain I think that it is
better to use /16 and have each node hand out IPs belonging to a given
portion (i.e. its own /24 - exactly as described below).

> bridge DHCP-server:
>         pool: 172.17.<id>.2 to 172.17.<id>.100
>         subnet mask: 172.17.<id>.0/24

given what I suggested above, this should still be

>         route: via 172.17.<id>.1

this is not required because the entire /16 is covered by the netmask.

This way each node will hand out IPs within its portion
(172.17.<id>.2-100) but at the same time the entire mesh will be within
the same /16 and everybody will be able to talk to everybody else
without having static routes in place.

> activate batman gateway feature (to prevent DHCP-server from
> connecting over bat0)

agreed (assuming that each node is running its own DHCP server).


Antonio Quartulli

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20150811/92f437a4/attachment-0001.sig>

More information about the Battlemesh mailing list