Hey,
yep, bmxd/batman0.3 and batman-adv are both not compatible to each other.
You should know that batman-adv does not have special gateway support like the layer 3 batman versions. It can be considered as a big switch where every node is one virtual hop away. You can therefore configure it like your home LAN: install DHCP on your router, and that's it. If you have multiple gateways, you might consider multiple DHCP servers, or something else ... depending on your scenario. :)
regards, Simon
On Sun, Nov 16, 2008 at 11:30:06PM +0700, Outback Dingo wrote:
ok lastly, it seems possible its very similiar config to bmxd which is what has been running, though layer 3, im trying to get layer 2 kernel routing going originally i used batgat but yet it was problematic, so its safe to say i could go batman-adv and drop bmxd? as i belive one is not compatible with the other in the mesh
On Sun, Nov 16, 2008 at 11:26 PM, Marek Lindner lindner_marek@yahoo.dewrote:
On Monday 17 November 2008 00:06:37 Outback Dingo wrote:
any good docs on configuring batman-adv for atheros ?
We are writing it but it takes time. :-)
Here the short intro:
Batman advanced is not aware of the Atheros driver. On every hardware it runs in the same way.
Load the module -> modprobe batman-adv-core
In /proc/net/batman-adv/ you will find the files to tweak batman. E.g. give it a device to operate on -> echo eth0 > /proc/net/batman-adv/interface
deactivate batman-adv -> echo "" > /proc/net/batman-adv/interface
The other files in that folder should be self explanatory. If not come back and ask us.
Regards, Marek
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n