L3-only mesh (with only Babeld, no batman-adv / no anygw)

[AguTrachta]

We are exploring an L3-only mesh, uninstalling batman-adv and anygw, keeping only babeld, verifying that routers discover each otehr and exchange router; and a laptop connected to one router's LAN can reach the others via L3 forwarding.

Configuration

• As mentioned before, uninstall batman-adv and anygy.
• lime-node config:

config lime network
	option main_ipv4_address '10.%N1.%M5.1/24'
	option main_ipv6_address 'fd%N1:%N2%N3:%M5%M6::1/64'
	list protocols ieee80211s
	list protocols lan
	list protocols bmx6:13
	list protocols olsr:14
	list protocols olsr6:15
	list protocols olsr2:16
	list protocols babeld:17
	list protocols bmx7:18

Observations

There are routes between routers

root@LiMe-f89fab:~# ip r
10.13.159.0/24 dev br-lan scope link  src 10.13.159.1 
10.13.214.0/24 via 10.13.214.1 dev wlan1-mesh_17 onlink 

Where Babel is giving A a route toward B’s prefix (10.13.214.0/24 via 10.13.214.1), as expected.
But my laptop is not in A’s 10.13.x LAN, it’s on 192.168.1.0/24 (Ethernet) and 192.168.0.0/24 (Wi-Fi), with defaults pointing elsewhere, so traffic to 10.13.x doesn’t naturally go to A, if I add a temporary extra IP con A's br-lan and an on-link static route on the laptop the ping succeeds, but only with A.

[ilario]

	option main_ipv4_address '10.%N1.%M5.1/24'
	option main_ipv6_address 'fd%N1:%N2%N3:%M5%M6::1/64'

It's a very good idea to use %M in the addresses! We could use it also for replacing the %N1, so that the collisions are less likely.

But my laptop is not in A’s 10.13.x LAN, it’s on 192.168.1.0/24 (Ethernet) and 192.168.0.0/24 (Wi-Fi)

Maybe we still need some part of anygw code? We could split anygw in two parts: the DHCP part and the anygw IP part.
It is very weird that your laptop gets those IPs if they are not configured anywhere in the LibreMesh node. Do you have another laptop for confirming or can you check which IP do you get if you connect with a smartphone via WiFi?