[Battlemesh] Network configuration and address plan for Battlemesh v9

Antonio Quartulli antonio at meshcoding.com
Tue Aug 11 15:17:01 CEST 2015



On 11/08/15 15:13, Henning Rogge wrote:
> On Tue, Aug 11, 2015 at 2:42 PM, Antonio Quartulli
> <antonio at meshcoding.com> wrote:
>> Hi Henning,
>>
>> for the batman-adv bits:
>> ...
> 
> Thank you for the feedback... so this would be okay?
> 
> 
> 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/16
> bridge DHCP-server:
>        pool: 172.17.<id>.2 to 172.17.<id>.100
>        subnet mask: 172.17.0.0/16
> 
> activate batman gateway feature (to prevent DHCP-server from
> connecting over bat0)

yeah, looks good to me, except for those /32 IPs on the bridge - they do
not hurt, but what are they good for?


Cheers,


-- 
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/a2eec5de/attachment-0001.sig>


More information about the Battlemesh mailing list