I have no easy way of giving feedback on your website, so forgive me for doing it like this. Related to your website's mesh networking article #1
seemebreakthis
started this conversation in
General
Replies: 2 comments 3 replies
-
thanks for the heads up, @seemebreakthis . could please share your network configuration file and openwrt version used? it's been a while since I last edited the mesh guide and as you pointed out, I might have to do it now. |
Beta Was this translation helpful? Give feedback.
3 replies
-
also, in the future, you can send me an email instead (see my contacts). it's all good though. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sorry, this isn't related to rpi-button-box at all.
In your website https://cgomesu.com/blog/Mesh-networking-openwrt-batman/ , there is a lot of useful info and I basically followed your guide to set up my batman mesh which runs really smoothly. I'd like to bring your attention however to the VLAN setup which has changed drastically for the recent Openwrt versions.
In https://openwrt.org/docs/guide-user/base-system/basic-networking#switch_configuration_dsabridge-vlan, it says "As of OpenWrt 21.02, swconfig is being phased out and is being replaced with DSA". With this comes a new approach of setting up VLAN, and mesh ports are also impacted by this update.
It is actually a more intuitive approach in my opinion, and I figured everything out pretty quickly without even searching for any info. Basically this is all you have to do (in LuCI's new "device VLAN Bridge VLAN filtering" page):
All tagged VLAN data will flow through the bat0 port to other mesh nodes. At the other mesh bridges you basically do the same thing so tagged VLAN data will flow through the mesh backhaul to the other (bridged) networks.
So basically there is no longer any concept of bat0.1, bat0.2 etc. bat0 is treated like a physical ethernet port in a sense. Since data that reaches the bat0 port already has tagged VLAN information (because you are never attaching any network client directly to bat0), you just need to select which VLAN data you need to carry through the mesh backhaul, and in my case above, both VLAN 1,2 are tagged meaning both VLANS will flow through the mesh to/from other nodes.
That's it ! And for the network interfaces (usually one per VLAN), you just need to attach the appropriate bridge VLAN device (br-lan.1, br-lan.2, etc) to each interface. No longer do you need to attach any bat0.1, bat0.2, etc there.
Beta Was this translation helpful? Give feedback.
All reactions