When having a Mesh (802.11s) network and using guest networks for Wifi with own bridges and/or vlans do the Mesh nodes also need these bridges and/or vlans or only the main router ?
Guest networks and VLANs have to be configured on all devices that act as Access Points. Mesh (802.11s) is self-organizing wireless backhaul that takes the place of wired Ethernet to connect to the rest of the routing infrastructure (the external router in a simple residential setup).
To use vlan on 80211s you need either batman, gre, or vxlan in addition.
Yeah I thougt so; with other mesh solutions (also with this actually) you can more delegate which accesspoint accepts what.
Yeah batman is really used because of your mesh design; vxlan is just an extention of VLAN witin VLAN.
It's possible to run a small mesh without any of that - the trade off is greater simplicity for less (perceived) reliability. For my three node home network simple has been more than reliable enough.
Nope.
Vxlan is vxlan and vlan in vlan is 8021q.
Indeed, always reliable here, Batman should be usable after 3-5 nodes.
VLAN standard is specified in the IEEE 802.1Q standard by IEEE. VXLAN standard is specified in the RFC 7438 by IETF . VXLAN encapsulates the VLAN tagged packet with four outer headers to transmit the packet in IP based network.
Dude save yourself this slop.
Vxlan is vxlan. And yes it can transport 8021q frames but I can also encapsulate any Ethernet frame. That's the point of a tunnel. Vxlan is plain layer3 while vlan are layer2.
Maybe you better say you are not right; you are putting everything on top of your earlier statement to try to save yourself. Easy way of being wrong by saying buzzwords without clearing things out directly.
You are in your slob; stay away from this topic.
You come around with a wrong and too short answer.
You have clearly no experience with any encapsulation method and vxlan in particular.
Do yourself a favor and consult the Wikipedia and the rfc.
Vxlan is a layer3 protocol using udp to encapsulate a generic Ethernet frame. That's it.
People making such claims aren't much worth themselves; I was just referencing about the backhaul implementation as it differs a lot as I only do large backbones and such.
Good luck with your small routes in life 
Unfortunately for you, @_bernd is correct.
From the vxlan man page:
NAME
vxlan— Virtual eXtensible Local Area Network tunnel interfaceSYNOPSIS
pseudo-device vxlanDESCRIPTION
The
vxlanpseudo-device provides interfaces for tunnelling or overlaying Ethernet networks on top of IPv4 and IPv6 networks using the Virtual eXtensible Local Area Network (VXLAN) protocol.VXLAN datagrams consist of an Ethernet payload encapsulated by an 8-byte VXLAN header, which in turn is encapsulated by UDP and IP headers. Different VXLAN tunnels or overlays between the same VXLAN Tunnel Endpoints (VTEPs) can be distinguished by an optional 24-bit Virtual Network Identifier (VNI).
VXLAN protocol is defined in RFC7348, so you are incorrect again.
From the RFC7348 document:
"Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks"
This looks like part of an AI answer, taken out of context by you to suit your erroneous story.
Your question that gave this as an answer probably went something like this -
di-direct: How does vxlan carry a vlan packet?
ai: VXLAN encapsulates the VLAN tagged packet with four outer headers to transmit the packet in [an] IP based network.
I will echo back to you your last sentiment:
If you want to be correct doesn't know that you mean how it works by yourself; these super correct people that want to be correct in a discussion where it doesn't have any value just want to be right.
Real people carry on because they have better things to do and know enough by half a word; doesn't seem you haven't also.
People that echo don't ever look into a mirror: maybe you should try and you see another "friend".