Hi Francesco,
On Monday, September 17, 2018 3:44:53 PM CEST Francesco Salvatore [fabbricadigitale] wrote:
LAN to mesh.
That certainly looks like an announce frame. Do you see any other frames
in
between, like claim frames?
Announces are also sent after a couple of claim frames upon a request (check batadv_bla_answer_request). We actually had a bug where inconsistencies among the BLA tables could happen, but that was fixed before 2017.3 ...
BLA traffic seems regular. This (https://mega.nz/#!9ZkmharA!S9mFxvpnnnseu_l8H7MPfoZ7X1Ef0lNrJLVQOpgTg4w) is a dump of the broadcast traffic captured from LAN ports of four gateway (on two separate VLANs). As you can see loop starts at packet 2660. The four gateways are: . 00:0f:00:68:97:e4 (Bridge IP 10.140.0.61) . 00:0f:00:68:9f:4b (Bridge IP 10.140.0.17) . 00:0f:00:68:96:66 (Bridge IP 10.140.16.19) . 00:0f:00:55:3c:dc (Bridge IP 10.140.16.61)
Hmm. There are already other packets looping in the beginning. There are some ARP requests which are repeated 4 times (packets 39 and following). Are those MACs on the network?
I don't really know what's going on from staring on this dump. You may want to remove components which are not vital and check if it's still happening. For example, you may want to connect the Raspis with a simple switch first (if you don't already do that). But the loop is already present before that announce loop, it seems - BLA would normally avoid repetitions.
BATMAN has a grace period to allow broadcasts from the LAN only after 1 minute of operation. This is done to make sure that the mesh is properly established and other gateways and their claims are detected before
traffic is
allowed on it, at least potentially looping traffic. Therefore, you should
make
sure (e.g. in your firmware or setup scripts) that the LAN is operational
once
batman is brought op.
If the mesh isn't fully established or it's actually split due to
different
channels or similar, then you may run in an unresolved limitation of
BLA:
https://www.open-mesh.org/projects/batman-adv/wiki/Bridge-loop-%3E > avoidance-II#Limitations
For this reason we have the loop detect packets. If a loop is detected, an uevent is sent to userspace, and the firmware should react appropiately,
e.g.
by shutting down batman-adv.
We start gateways with this script placed in rc.local
sudo pkill wpa_supplicant sudo modprobe batman-adv sudo ip link set wlan0 down sleep 2s sudo iwconfig wlan0 mode ad-hoc sudo iwconfig wlan0 essid mesh-network sudo iwconfig wlan0 ap any sudo iwconfig wlan0 channel 44 sudo ip link set wlan0 up sudo batctl if add wlan0 sleep 1s sudo ip addr flush dev eth0 sudo ip link add name br-lan type bridge sudo ip link set dev eth0 master br-lan sudo ip link set dev bat0 master br-lan sudo ip link set up dev br-lan sudo batctl bl 1 sudo batctl gw server
As far as I can see the bridge interface gets IP/connectivity from LAN a few seconds after the script quits. Are there steps correct or there are possible timing issues? We're using the same essid/channel for all originators
It would be good to do "batctl bl 1" before adding bat0 to the bridge, otherwise you are not protected. Other than that, it looks fine to me.
Am I wrong or "batctl bl 1" is redundant? As far as I can see, according to batctl, BLA is turned on by default in gw mode.
Hm you are right, it's probably enabled by default. That should be independent of the gateway feature though.
Cheers, Simon