Hi Ammo, you need a liferaft not an ax3 
Mine came in yesterday still have not had a chance to play…
I know nothing about how to setup its wifi, do I need this wifiwave 2 crapola…
If it’s the only AP, it works great. It was night and day on the Audience compared with “stock” drivers. Suspect be same on the ax3’s (which I’m waiting for)
Now I’m 100% sure you’re not going to like the “CAPsMAN for everyone” way you configure WifiWave2 drivers…
Normis explained a while ago that ax devices can only run wifiwave2 “crapola” … not supported by legacy driver at all.
So let’s brace ourselves while waiting for @anav to axe that ax3 
Is the ax hardware getting some MT legacy driver options, sooner than the ac hardware?
Release notes 7.7rc5:
*) wifiwave2 - added option to set per-client vlan-id in access list (only supported on 802.11ax interfaces) (CLI only);
hi bpwl there are many CLI only wifiwave doo dahs noted on the 7.7 release.
Do you have clear way ahead for a standard setup of one hap ax3 using these things…
I was hoping MT was going to make things clearer but it seems worse now LOL.
@anav, No idea how to do the “wifiwave2 cli only”, have no MT AX device yet. Just the release notes hint it’s different. Forum members said they didn’t find it.
It actually be good to know if QuickSet does something reasonable on the ax3. There just aren’t as many options in the WW2 drivers without the missing “4 address mode” (e.g. WDS, bridging modes, etc) .
Bumping thread cuz I want this to be visible to the staff. 
+1
Please implement station-bridge/ap-bridge and WDS in wifiwave2, making sure it is inter-operable over the air with the older driver too (at least in plain 802.11 if nstreme/nv2 are too difficult with the new code base).
The fully transparent bridge mode (without ugly “MAC address NAT” hacks) is an important feature with many good uses, from extending home WiFi networks to WISP PtMP setups. While not a true WiFi standard, it is standard enough that I have sometimes used “static mesh WDS” for connecting UBNT M5 series stations to MT APs (802.11 only as the proprietary TDMA protocols are not compatible, but WPA2-PSK AES encryption works fine, and connected stations appear as bridge ports so all features of the new bridge implementation can be used). Actually, it would be nice if ordinary WiFi stations could appear as bridge ports as well - then you don’t need a separate bridge implementation hidden inside the wireless driver in AP mode, just re-use the same existing fully-featured one that can do VLAN filtering, R/M/STP, bridge firewalling etc.
+1
I’ve been waiting for this feature for a long time too. Perhaps at some point mikrotik staff could hint at whether this is on the roadmap at all? I understand it’s difficult to commit to an implementation date, but if there is no intention of introducing this functionality to wifiwave2 it would be great to share this information with users.
https://help.mikrotik.com/docs/display/ROS/WifiWave2
Lost features
The following notable features of the bundled wireless package do not yet have equivalents in the wifiwave2 package
Station-bridging or other 4-address modes
Nstreme and Nv2 wireless protocols
Your only option left, change firmware to OpenWRT.
I do hope that isn’t the end of the story here. But “meshing” is the unique feature in the Audience… And yes it’s poor choice today: Wave2, no mesh, OR use the “old” wireless package and have a mesh…
I do have a couple hAPax3 I have been testing, so tried the VXLAN approach. The hard limit of 1500 MTU is still present which is still my personal biggest grip here. So this any alternative approaches will result in fragmentation. I’d actually be fine with some tunnel over wi-fi — but I don’t want MTU to get squashed by the 1500 MTU limit in wifiwave2.
Since I was also curious how well AX does in 2.4GHz, as these hAPax3 were my first AX devices. In theory it should perform a lot better with congestion than ac…so I created a PtMP link using the hAPax3’s “wifi2” interface that carried a VXLAN tunnel over the 2.4Ghz AX interface.
Summary is a VXLAN does work. And, yes, it does get unnecessarily fragmented but “works” nonetheless. Basically you (from a winbox POV):
- take wifi2 out of bridge on both
- one becomes get set to “station”, other remains “ap”
- set SSID “AX 2488 Mesh” on both (or whatever)
- assign 172.22.88.1/24 as IP for “wifi2” on ax3 “ap” (or whatever unique subnet you want)
- assigned 172.22.88.2/24 as IP for wifi2" on the “station” ax3
- create VXLAN interface using defaults on both
- hit “VTEP” button to link the VXLAN to the IP address of the far end Wi-Fi interface’s IP (e.g. on AP, 192.22.88.2… on one/more stations, the VTEP address is 192.22.88.1)
- add VXLAN to bridge as a port (and set PVID if vlan-filtering=yes) on both
FWIW, ZeroTier also works to bridge a network over Wi-Fi PtP/PtMP here too. The key is the Wi-Fi interfaces have to have routable L3 addresses, just like for EoIP or VXLAN, for the tunnel endpoints.
Add me to the list of people waiting on this functionality. I was just trying to set this up today with an ax2 I purchased to extend a network for radio equipment and ran into this limitation; I did not want to deal with the complexity of another network, but here we are.
Thanks for the writeup. I got things working between two Audiences for a customer, who wanted to take advantage of the greater bandwidth offered by the newer drivers.
It works. Thanks.
I have sucessfully briged two hAP AX3 routers to extend home network.
One remark is to check on brige ports and include VXLAN in LAN. This can save you a lot of time wondering why it doesn’t work.
I had issues with FW rule “Drop All Not Coming From LAN” as connections were dropped.
- DHCP was not working on station wifi clients due to this.
- manual IP set was also not working.
Add me to the list as well of those who hope that 4-address comes back. I have a WISP with hundreds of Audiences in production that I cant take advantage of wifiwave2 on due to this. I will try the VXLAN workaround, but I will not accept this as a solution. Due to the limited MTU and the complexity added by using VXLAN, it will probably never see the field until this is resolved. This is making it very difficult to maintain Mikrotik as a primary vendor for Client-side WIFI.
It’s actually the “wifi2” that need to go into the LAN interface-list (or tunnel subnet “172.22.88.0/24” needs to be allowed in the firewall) – that part may not have been listed 
.
But the VXLAN itself is bridged, so to the firewall the “inner” traffic comes from bridge/VLAN as the interface, not the VXLAN interface. But the “outer” VXLAN packets (with 172.22.88.0/24 address) come via wifi2 which should NOT be in the bridge (but does need to be allowed by firewall).
Thank you Amm0 for your work.
Question : is it possible to make this config with 3 audiences in serial ?
AP → STATION → STATION
No, station can only communicate with single AP (and not directly with other stations, even if they all connect to same AP). However, this might work: station ↔ AP ↔ station … Keep in mind, that from network infrastructure perspective AP doesn’t have to be in some certain spot. E.g. in your case, AP can be device without wired connection. In your case it only matters where the L2 tunnel (whatever variety you’re using) terminates, it has to terminate on devices which are connected to wired parts of network, in the topology mentioned at the beginning of this post this means the left and right station devices while device in the middle (AP) only serves as transport node (since 4-address mode is not available, you’ll actually have two IP segments, AP In the middle being part of both and it will route between both stations).
That’s what I was going to say. Both station use the “middle” as their VTEP address. VXLAN allows a one-to-many topology.