I came across a thread previously on this same issue with respect to openwrt.
I tried to change the routing algo following tweaking section of batman wiki as soon as loading the batman_adv module.
I am able to see BATMAN_V under availabile algorithms but available for next instance of batx. I understand it has to be done before this bat0 interface is created, but I am doing this before bringing up bat0 using ifconfig
batctl 2016.4 batman-adv 2016.4
On Freitag, 17. Februar 2017 04:25:25 CET leftbydefault@riseup.net wrote:
I came across a thread previously on this same issue with respect to openwrt.
I tried to change the routing algo following tweaking section of batman wiki as soon as loading the batman_adv module.
I am able to see BATMAN_V under availabile algorithms but available for next instance of batx. I understand it has to be done before this bat0 interface is created, but I am doing this before bringing up bat0 using ifconfig
Mo, it "ifconfig xxxx up" is way to late. It the module has to switched to BATMAN_V before the batX interface is created (this is before the setup function of the netdev is executed in the kernel).
Kind regards, Sven
b.a.t.m.a.n@lists.open-mesh.org
-
leftbydefault＠riseup.net -
Sven Eckelmann