Hello everyone.
I have three mesh nodes. Node A don’t see node C. A can't communicate with C directly, but it can commuticate with C via node B, which is between A and C. The path is A - B - C.
On node A, I can run the command 'batctl ping MAC' to node B and node C successfully. When i try the normal layer 3 ping [ping IP] it’s ok to node B for node C doesn't work. Maybe i have a wrong configuration at layer 3.
My configurations:
/etc/config/network
config interface 'lan' option ifname 'eth0.1' option type 'bridge' option proto 'static' option ipaddr '192.168.0.1' option netmask ‘255.255.255.0'
config interface 'mesh' option ifname 'adhoc0' option mtu '1528' option proto 'static' option mesh 'bat0' option ipaddr '192.168.11.1' option netmask ‘255.255.255.0'
/etc/config/wireless
config wifi-iface option device 'radio0' option ifname 'adhoc0' option network 'mesh' option mode 'adhoc' option ssid 'batman-mesh' option encryption 'none' option bssid '02:CA:FE:CA:CA:40’
/etc/config/batman-adv
config mesh 'bat0' option interfaces 'adhoc0' option 'aggregated_ogms' option ‘ap_isolation' [..]
root@OpenWrt:~# batctl if adhoc0: active
the difference between nodes is the ip address for interface lan(192.168.0.1, 192.168.2.1, 192.168.3.1) and mesh (192.168.11.1, 192.168.11.2, 192.168.11.3)
What i need to setup to can ping from node A to C?
Best Regards.
Hi,
Am 2015-06-17 21:50, schrieb Carlos Meralto:
My configurations: [...]
a batman interface is being set up, but left unconfigured.
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.
BTW, ping6 should work already with the link local IPv6 addresses of the bat0 interfaces, I guess.
-hwh
2015-06-17 21:34 GMT+01:00 Hans-Werner Hilse hw@haveyouseenthiscat.de:
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?
Hi,
Am 2015-06-17 23:09, schrieb Carlos Meralto:
2015-06-17 21:34 GMT+01:00 Hans-Werner Hilse hw@haveyouseenthiscat.de:
a batman interface is being set up, but left unconfigured.
Why you say that has not been configured?
Because you configure the adhoc network, but a setup for bat0 is nowhere to be seen. Yes, bat0 is set as the mesh network on the adhoc net. But this is *not* the same as a config for bat0. Setting up mesh networking on adhoc will leave the adhoc net in place and does not change anything about that. There only is an additional interface that will use the adhoc network, too.
So - why do you think it has been configured? I'm just guessing above.
What I want is to have an IP that allows me to ping from node A to node C. So join adhoc0 the bridge?
If you really just want to ping from A to C (which I find a use case that sound more academic than practical), it is enough to configure an address for bat0. Or, as I said, use IPv6, which does link-level autoconfig on bat0.
If however you want to use this to bridge things attached to the LAN interface of the devices, I advise to attach it to the bridge (except if this creates a loop - you said nothing about the topology outside the devices).
-hwh
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 carlosmeralto@gmail.com:
2015-06-17 21:34 GMT+01:00 Hans-Werner Hilse hw@haveyouseenthiscat.de:
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?
b.a.t.m.a.n@lists.open-mesh.org
-
Carlos Meralto -
Hans-Werner Hilse