Hi Juliusz, Yes, I can see your point. However, I am just using 802.11s for the LAN traffic to gateways. Some of these 802.11s devices may themselves be gateways. Their own gateway may only be good as a fallback gateway for rest of the mesh, and just making a gateway node force a client's DHCP through its own gateway is not exactly the effect I want to achieve with a performance monitoring protocol. Besides, a gateway may come and go, and I may want to enforce this cost feature to determine best path out. I know this was solved using batman-adv on the pre-existent OpenMesh firmware, this dynamic announcement of gateways. I want to use babeld as kind of a higher layer of routing on top of a single instance of 802.11s on the router LAN to achieve the same effect.
Thank you for your consideration. On Wed, Mar 6, 2019 at 7:05 AM Juliusz Chroboczek <[email protected]> wrote: > > Yes, in this situation all neighbor stations enumerate. Everyone can > ping > > everyone via 802.11s mesh. > > You're running Babel over an 802.11s mesh? Why? > > Both Babel and 802.11s are routing protocols (more exactly, 802.11s > contains a routing protocol). Running both in the same mesh is redundant. > > > However, now that it is running on the wlan0 that is a bridge of wlan0-1 > > and wlan0, it just seems boring; I don't see those fancy routing tables, > > and I am not seeing that it is establishing the shortest route based on > > prevailing network conditions, I am see only metrics passed of 0, 128, > > and 65535. > > This is expected. The 802.11s mesh is doing its thing, and Babel sees the > mesh as a single hop. > > If 802.11s works for you, then please use that. If it doesn't, then > please tear down the 802.11s and use Babel. It is pointless to run both > 802.11s and Babel on the same network. > > -- Juliusz >
_______________________________________________ Babel-users mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users
