Am Dienstag 06 Juli 2010, 22:15:45 schrieb Marek Lindner:
It requires each gateway to have a DHCP server running. The clients will select their gateway and relay the dhcp requests via unicast to the selected gateway only. You only need to activate the gateway / client mode and have a dhcp server running.
Okay I did this but I have some questions left:
Does the DHCP server on the gateway need to distribute IP-Adresses? If so I think they have to be distributet on the batman interface right?
Does the Batman advanced interface on the clients need to request an IP-Adress from the DHCP server or can I also set a static IP adress?
If the clients need to request an IP adress from the DHCP server, where is the difference between requesting an IP without Batman advanced and with Batman advanced? Does Batman advanced say from wich server to request the IP or which default route to choose?
**If so why do you mix Layer 2 and Layer 3 now?
If you don't want to mix layer2 / layer3 then just don't use this feature. It is disabled per default. If you have a better idea how to handle multiple gateways in a layer2 mesh we are very open to your suggestions. :)
Sry for this question we just discussed this on the last community meeting and somebody wondered if this is the most beautiful way. Maybe it´s not but you are right there is no other way.
Unfortunately, we did not get around finishing it to the point that we feel comfortable with releasing this feature. I think the trunk is quite stable but still lacks some things. E.g. blacklisting / whitelisting gateways, IPv6, etc.
Okay but it will likely be usable without crashing right?
Last but not least: How can I configure batman advanced in /etc/config/batman-adv to enable gw server/client mode?
Greetings Clemens