I just made my first order of the wAP AC (both white and black) and noticed there isn’t a real topic about the unit yet.
Hopefully we can all share our experience with the unit and maybe answer questions for others. I will be doing so as soon as my order comes in. Any tests anyone wants to see except the usual (Wireless throughput, CAPsMAN throughput)? I will also try to do a video about the unit and it’s exterior.
I’m expecting performance to be very similar (at least in Wireless and CAPsMAN situations) to the recently released hAP AC since they share a CPU and wireless chip (2.4Ghz in the wAP AC has one chain less). If so, that would make the wAP AC a very nice unit for a great price!
–update
As a tryout I made a sort of unboxing and first look at video about the wAP AC instead of a blog post. I might also do a blog post but since the performance (At least at 5Ghz) is 100% identical to the hAP AC, there isn’t much use in re-doing all the benchmarks. You can find the video here:
Let me know what you think! As I said, this is a first try at something like this, so be kind.
I received my batch today and did a quick test upgrading it to RouterOS v6.35 and connecting it to my CAPsMAN and replacing my current hAP AC. All seems well so far, all the clients automatically connected to the new AP and as far as I can tell this quickly performance/range/etc. is quite similar.
In CAPsMAN mode with a hAP AC connecting to it as a client (with my desktop wired into it) I still achieve a maximum of about 30MB/sec ~ 32MB/sec which is because of CAPsMAN tunneling filling up the CPU. Exactly the same as with the hAP AC (which uses the same CPU at the same frequency). So all is well there (if you have a problem with this run CAPsMAN in local breakout mode to remove this limit).
I should have some time this weekend to do more extensive testing!
Yes, this was using RouterOS v6.35 with wireless-rep. I have been doing my video (Instead of a blog post this time, blog post may still follow) and I have been using one for the past day now. Stability and performance seems to match the hAP AC perfectly.
As a tryout instead of a blog post I made a sort of unbox and first look video about the wAP AC, take a look let me know what you think! https://youtu.be/hME1gsUbFTE
I discovered this too - we just received ours from Mikrotik and I was dead keen to try them out, only to think the first one was DOA LOL. I did exactly the same as you and set them up in CAP mode but they still only partially worked - until I checked the packages and saw wireless-fp was the default package. Changed to wireless-cm2 and the Capsman controller found and configured it ok.
I’ve seen some instability on 2.4 Ghz so doing some more tests to make sure its not interference or config
With an iPhone 6 using 5G AC and Speedtest.Net I maxed out at 50/50Mbps - which is currently all I can get from my provider - upgrading to 200 Mbps Fibre as we speak and will retest. Pretty happy with that so far…
Mikrotik confirmed to me last night wireless-cm2 would be the default on the next batch which is something.
No doubt wireless-rep will become the only package at some point but hopefully they make the package upgrades work better than when they dropped the wireless.npk file
I agree, I’m happy to see the hEX PoE coming, but look forward to CRS line getting similar 802.3af/at POE support. Ideally, something that competes well with things like https://www.ubnt.com/edgemax/edgeswitch/ (24/48 port, STP, LACP, etc).
Yes, I have also tested all the different options using Active and Passive POE hardware I have lying around and I can confirm that it accepts a wide Passive input voltage range and also fully supports Active POE! Very nice and usable in lots of different scenarios!
The one I’m using daily is powered by a Passive 24v Gigabit Ubiquiti injector, also works fine.
as i’ve go a runnig CAPsMan in my network
- we just received ours from Mikrotik and I was dead keen to try them out, only to think the first one was DOA LOL. I did exactly the same as you and set them up in CAP mode but they still only partially worked - until I checked the packages and saw wireless-fp was the default package. Changed to wireless-cm2 and the Capsman controller found and configured it ok.