Underlay VXLAN network (trying to use only IPv6 LL)

I'm testing different network ways to configure the underlay network for VXLAN.

Actually I have tested just making a mesh network with layer3 and using it to introduce VXLANs. I have tested with just two and it works as expected.

Where I'm now is setting multiple paths to that network. I have successfully tested a bridge device where I set the mesh layer 2, and a lan port layer 2, and then I set the layer 3 IPv6 LL just only over the bridge. Need to test it more time but it seems a reliable way because when two nodes gets connected over ethernet they stop using the mesh network to communicate between them. I have at the moment only one concern, that is I haven't enabled STP but seems to be working. As said I need to test it more time as a loop should be there and this should not work without STP. Actually I have found that both routes are being used at the same time so enabling STP is advisable.

Another thing I'm planning is instead in doing a simple bridge to use bounding to avoid the need for STP and let the bonding device to manage the traffic through the wire when is connected and over the mesh when is not.

I have never use bounding but it seems a very reliable way to manage this.

Update: I could see that both routes are used at the same time without STP, actually I don't understand why it doesn't collapse but the best bet is to enable STP. Actually without STP when disconnecting the wire the net doesn't go down, with STP as expected and as STP time parameters it takes a little time to route within one or another. I have now to test about path cost but for mi idea to only use LuCI seems that that won't be possible. Anyway it seems that wire is always preferred when both links are up but I don't know if that is hardware dependant or anything else, both nodes are actually so near for each other the the reported bandwidth should be even more than my 1 Gbps ethernet.

At least at this moment many systems have troubles with VLAN + STP.

I have just updated the OP, actually this isn't the same, the STP is in the underlay network for the VXLAN. But thanks for the hint because is something I have also to test multipath with VLAN.

Edit: Thanks again, I have take a little look for the PR you linked and it seem is now solved upstream but still pending to a backport to be applied in OpenWrt. If went to test first the VLAN multipath instead the VXLAN I will get mad about it or wrongly supposed that is not possible.

I still prefer the VLAN way at least for domestic usage because of performance, I still don't truly know if in a more crowded environment like hotel or malls could have issues with VLAN because of broadcast traffic and that's why I test both VLAN and VXLAN way.

I think it doesn't deserve to test if with bonding is possible, I have test STP before and after installing ustp and with it the path changes are fast.

I have tested both using VXLAN just to be a tunnel for VLANS and pure VXLAN with multiple of them and no VLAN at all, I works great. STP is needed yes or yes despite the network seems to not collapse, at least not fast, I think because is just a IPv6 Link Local underlay.

I have also test doing with pure VLAN and as expected with the issues pointed by @timur.davletshin it has no effect at all and packets stay appearing with the same source in destiny between paths and the network collapse so fast. I will stall VLAN STP for another thread till the fixes get backported.

I have found one issue. When there are just 2 nodes the cable makes to use the cable instead the mesh between them, but, when a 3rd node that is only part of the mesh network get powered on, the wire route between the first to the second change to blocked and the mesh forwarding state.

Need to look more at this.

Solved by not setting a ethernet port in the only wireless connected node into the VXLAN underlay network. I wish if it could be possible to leave it configured to be used when someone connects a cable but it seems STP doesn't like it.

This makes the second node to only arrive the third through the first. I think a better approach could be babel instead stp but I think it requires to set independent layer 3 for every possible route being the opposite to find a simple OpenWrt solution.