Hi again.
Before some more research i found a solution...
The ip needs to be setup on bat0 and not on adhoc0.
So the final configuration:
config interface 'mesh'
option ifname 'adhoc0'
option mtu '1528'
option proto 'batadv'
option mesh 'bat0'
And run this commands to attribute a IP on bat0 interface:
uci set network.bat0=interface
uci set network.bat0.ifname=bat0
uci set network.bat0.proto=static
uci set network.bat0.mtu=1500
uci set network.bat0.ipaddr=NODE-IP
uci set network.bat0.netmask=NETMASK
uci set batman-adv.bat0.interfaces="adhoc0"
uci commit
reboot & exit
Thanks Hans-Werner ;) and and hopefully help someone with the same problem
2015-06-17 22:09 GMT+01:00 Carlos Meralto <[email protected]>:
> 2015-06-17 21:34 GMT+01:00 Hans-Werner Hilse <[email protected]>:
>> a batman interface is being set up, but left unconfigured.
>
> Why you say that has not been configured?
>
>> On the other hand, you set up IP adresses for the adhoc network, which
>> probably isn't needed and the point where the confusion arises.
>>
>> What you probably want to do is to add bat0 to the bridge's interfaces, and
>> maybe get rid of the IPv4 addresses on the adhoc interface, too (not that
>> they matter, though).
>>
>> Of course, when you do not want to bridge the LAN interfaces, you need
>> another way to setup IP addresses for bat0.
>
> What I want is to have an IP that allows me to ping from node A to
> node C. So join adhoc0 the bridge?
