On Thursday, 8 June 2023 22:38:23 CEST mark.mundy@draeger.com wrote:
What is the best way to figure out why 2 nodes that are connected on a WMN can see each other through 'batctl n', but 'batman ping' fails with the message "Error - mac address of the ping destination could not be resolved and is not a bat-host name"?
Please use either the actual mac address of the remote or the IP which is configured on the bat0 (which is also reachable directly by your host). batman-adv is not the IP subsystem and will therefore not be able to resolve any non-direct neighbors (over bat0).
Node at eth1 - 10.1.1.1, wlan0 mac ether 04:f0:21:59:38:c9 root@jammy-newport:~# batctl n [B.A.T.M.A.N. adv 2021.3, MainIF/MAC: wlan0/04:f0:21:59:38:c9 (bat0/72:85:90:2a:95:06 BATMAN_IV)] IF Neighbor last-seen wlan0 c4:4b:d1:90:02:90 0.500s root@jammy-newport:~# batctl ping 10.2.1.1 Error - mac address of the ping destination could not be resolved and is not a bat-host name: 10.2.1.1
Node at eth1 - 10.2.1.1, wlan0 mac ether c4:4b:d1:90:02:90 root@focal-newport:~# batctl n [B.A.T.M.A.N. adv 2021.3, MainIF/MAC: wlan0/c4:4b:d1:90:02:90 (bat0/6e:87:15:7e:f3:14 BATMAN_IV)] IF Neighbor last-seen wlan0 04:f0:21:59:38:c9 0.708s root@focal-newport:~# batctl ping 10.1.1.1 Error - mac address of the ping destination could not be resolved and is not a bat-host name: 10.1.1.1
My intention is to be able to reach a computer on the far side of the WMN connected to eth1 10.2.1.1 from my host computer connected to the same network on eth1 10.1.1.1. It should look something like this. network -> eth1 10.1.1.1 -> wlan0 -> bat0 (inet 10.1.1.4) -> BATMAN -> bat0 (inet 10.2.1.4) -> wlan0 -> eth1 10.2.1.1 -> non-BATMAN computer
My intention is to have eth1 10.1.1.1 connected to the main network as an interface for bat0 able to communicate over bat0. On the other end, eth1 10.2.1.1 The interfaces for eth1 and wlan0 show as active for both computers.
Reach how? With IP routing? It is not the task of batman-adv to perform IP routing (it is on the wrong layer).
On Thursday, 8 June 2023 22:38:23 CEST mark.mundy@draeger.com wrote:
allow hotplug eth1 auto eth1 iface eth1 inet static address 10.1.1.1 netmask 255.0.0.0 gateway 10.0.0.1 # dns-nameservers 1.1.1.1 8.8.8.8 8.8.4.4
allow hotplug bat0 auto bat0 iface bat0 inet static address 10.1.1.4 netmask 255.0.0.0
The IP configuration is weird. You have two IP addresses (bat0+ethX) which are overlapping (10.0.0.0/8). This cannot work.
If it should be a transparent bridge between mesh without IP routing then please add bat0+eth1 in the same bridge. And then configure the IP address on top of the bridge.
Kind regards, Sven