You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tl;dr without VLAN, Babeld currently cannot run on ethernet
When instructing Babeld to run on the plain interfaces, without any VLAN, it fails to run on LAN ethernet ports.
The reason is that they lack an IPv6 Link Local address, and they cannot have it as they are included in br-lan bridge.
So, just in the case of Babeld witout VLAN, we should run it directly over the br-lan bridge.
The problem is that Batman-adv interface is also into the bridge and to have hello packets of Babeld running into Batman-adv would completely break Babeld topology estimation.
So some firewall rules like the ones in lime-proto-bmx6 here will have to be used.
The text was updated successfully, but these errors were encountered:
Do you think that this solution would be too complex to be active by default?
I mean, there is some interest (see #581) to remove the default VLAN from Babeld, do you think it is still worth, now that we discovered this complication?
Thanks @ilario for pointing this out! If it was working good in 17.06 its ok for me using the firewall, I don't know what complications could arise. @G10h4ck ?
Blocks #581 attempt of solution in #631
tl;dr without VLAN, Babeld currently cannot run on ethernet
When instructing Babeld to run on the plain interfaces, without any VLAN, it fails to run on LAN ethernet ports.
The reason is that they lack an IPv6 Link Local address, and they cannot have it as they are included in
br-lan
bridge.So, just in the case of Babeld witout VLAN, we should run it directly over the br-lan bridge.
The problem is that Batman-adv interface is also into the bridge and to have hello packets of Babeld running into Batman-adv would completely break Babeld topology estimation.
So some firewall rules like the ones in lime-proto-bmx6 here will have to be used.
The text was updated successfully, but these errors were encountered: