Really mikrotik, in the past you do a good job. But that AX Units are useless.
- no NV2
- no WISP AP (Like MantBox AX)
- QuickSet is a horror on AX, you need to put anyhting manually
When you will fix this?
Use case please
- no WISP AP (Like MantBox AX)
Please elaborate?
- QuickSet is a horror on AX, you need to put anyhting manually
QuickSet is horror on any device…just use command line.
When you will fix this?
Have you filed a ticket on these items?
https://help.mikrotik.com/servicedesk/servicedesk/customer/user/login?destination=portals
For what?
NV2 no longer exist and QuickSet is not for WISP.
To understand the need(s).
Nv2 is the only thing that make usable RouterOS devices for WISP.
Contrary to anything that someone who does NOT work as a WISP with MikroTik products might write,
the NV2 is the only reason why I did not replace the MikroTik devices with others to work with years ago.
Now in fact I do not use them anymore: I keep the existing park working, but I have replaced with something else where I need to expand or widen the coverage.
If to replace a panel with one in ax I then have to change all the clients because the panel does NOT go in Nv2 and the clients do not go in ax,
I might as well put something else, with a more concrete wifi support…
And if someone suggests putting the peripherals in n/ac on the ax and expecting the same results, they would do better not to write at all.
@erlinden : nv2 is very usefull for multiple clients on a AP. Better Loadbalancing. When only use 802.11 we had massiv lags or disconnects. nv2 worked well (learned that in a mikrotik training). WISP AP was before on any ominitik and mantbox. We used this for our customers wifi networks. We build huge networks. I used QuickSet over years, also commandline, both worked very well. We have many employees in company they know only how to use quickset. Worked perfectly on any device. (Switches, 2,4Ghz , 5Ghz, 60Ghz)
The problem is that we only get new AX Devices from our distributor, cause ac is only a few old stock items.
And then mikrotik is providing (datasheets) on some new devices with over 2gbit wifi power and only 1gbit interface? We used a lot mikrotik in the past, but now it looks like we should use Ubiquiti, cause they have 2.5 and 10 Gbit interfaces on some new wifi units.
I’ve got a few hundred nv2 outdoor APs on many towers and over a thousand nv2 5km+ to 20km remote clients.
Because Mikrotik is dropping nv2 & nstream on all newer AX devices , I think I am being forced migrate into another WISP wireless delivery platform to my customers.
sad sad sad tom
In fact, that’s what I wrote before… inside the house the ax products are valid, but outside they are like the ac ones without the nv2.
However many laboratory tests you can do, then in real life, and when it’s your job, it’s different.
Sounds like for every hapax3, they should release a hapNV3, likewise – ax4, NV4 
I tried testing a mANTBox ax 15s as the AP and an SXTsq-5axD as the CPE, but the results were quite poor. At a distance of 500 meters, the throughput is only between 2–10 Mbps. When there’s no traffic, pings are fine, but that’s about it. Has anyone else experienced this, or are we making mistakes with the manual configuration?
Just curious, did you replace with 802.11 devices or some other proprietary technology? If I understand you correctly, it's not that 802.11 is unusable for WISP, but it's MT+802.11 combination specifically.
802.11 can be horrible for a WISP.
The 802.11 wireless protocol is a listen b4 transmit ( wait for clear air-time ). This keeps wireless users from stomping on each other when transmitting to the AP. Example , a wireless device is uploading and a second wireless device wants to upload but it waits for clear air time then transmits. This happens fairly quickly - but - the AP can only receive from one wireless client at a time.
Note: Normal 802.11 protocol wireless devices have what is called "ACK-Timing -- Round-trip-wireless-flight-time" - where there is a timeout period for a reply to be received. Most/many 802.11 wireless devices have default ACK-Timing factory set for 30-feet to at max 300-feet. When an 802.11 wireless device is further than this setting , the wireless devices consider this an error and might retry a few times before giving up and just dropping the packet. Most WISPs have wireless customers much further and measured in the thousands of feet - or kilo meters ( thousands of meters ).
The Problem:
Let's say you have a good outdoor AP that is up high and all of your wireless clients can talk to it and the AP can reach many miles.
However , let's also let two wireless client customers connect to this AP - but - both wireless clients are distant from each other ( opposite sides of the AP - or just far apart ). The two customers with normal wireless protocol 802.11 can not hear if somebody else is already transmitting to the AP. So neither client knows if the other client is transmitting to the AP - so to both clients it appears as if there is clear empty air to transmit.
You end up with both remote wireless clients stomping on each others wireless transmission to the AP. The AP hears garbage.
Thus packets stop being transmitted - the entire wireless system slows down because of error retries.
NV2 protocol ( TDMA ) is the solution.
With nv2 , the nv2 AP informs each nv2 wireless client when it can transmit - aka a timed transmit window.
Example ( over simplified - but this is the concept of nv2 timing ) :
- nv2 wireless client #-1 can transmit when it is every second at .3 seconds and can transmit for a max of .2 seconds.
- nv2 wireless client #-2 can transmit when it is every second at .6 seconds and can transmit for a max of .2 seconds.
None of the nv2 clients to a nv2 AP ever stomp on another nv2 client.
In-fact , nobody ever stomps on any other to/from the nv2 AP.
** Note - another protocol to address and correct 802.11 collision problems is called nstream. But that is not what this topic is about.
So , nv2 is better and faster for a WISP verses 802.11.
Many WISP's have outdoor APs with dozens or hundreds of remote wireless clients. And - most of those remote clients can not hear if another client is transmitting - so 802.11 creates network problems and more problems as you keep adding 802.11 clients. With nv2 , there is never a problem with clients stomping on other nv2 clients to the same nv2 AP - ... all nv2 clients are happy 
*** Re this topic: Whats wrong with mikrotik and your AX Series?
What's wrong is limited or none of the newer faster Mikrotik AX APs can do nv2.
So to a WISP with a large nv2 client base, the new products can be useless and won't work with their already existing nv2 wireless network(s).
Example ; I have hundreds of nv2 APs and over a thousand nv2 wireless clients. I need nv2 !!!!!!!!!!!
Re: ... it's not that 802.11 is unusable ...
It is the problem. The protocol 802.11 just does NOT work as needed in a WISP network.
North Idaho Tom Jones
Have to agree with the OP. We didn’t read the spec’s properly when we bought a mANT-AX thinking we could run a mix of AC and AX clients over NV2. Wrong. Total waste of money. The only thing this unit is good for is an outdoor AP for mobile phones and laptops, and for that it’s a total overkill.
MK AX products are completely useless to WISP’s. Hell you can’t even do a decent wifi-wifi extender with the hAP ax range as you can’t do nstream either, so you end up having to use pseudo station bridge which limit’s your layer 2 traffic. 
You would think that the Mikrotik ax products on the Mikrotik web page and their documentation/specifications should clearly state :
- Does not support nv2 protocol
- Does not support nstream protcol
I also have ordered some thinking they supported nv2 - but nooooooooooo , now they are in the large metal round-file ( the big dumpster ).
Thanks for explaining the differences. I wasn’t questioning Nv2 (never used it myself), but curious what technology @rextended replaced it with, if not 802.11. Since Nv2 is MiktoTik’s proprietary protocol, and they effectively discontinued it, what else is there? Another proprietary solution?
They do have a page in the main documentation about Nv2 not being possible on AX devices, but I agree, it should be listed on specification page for each device.
https://help.mikrotik.com/docs/spaces/ROS/pages/1409138/Wireless#Wireless-New802.11axdevices
Just go to another vendor. If anyone has been deploying any new 5ghz MikroTik gear for use as an outdoor WISP device in the past 7 years, well you can only blame yourself…
MikroTik essentially got out of that market segment years ago and got left behind by every other vendor. I cannot fathom why anyone would bother. First and foremost there is no spectrum scanner and hasn’t been since their ‘N’ based devices. That alone should have made you jump ship to any other provider (except Mimosa, dear god…) I can’t fathom how anyone could operate a network so blindly, it’s an absolutely essential tool. And the speeds/range/reliability prior to wave2 have been absolutely appalling compared to the competition
Wave2 and AX have dramatically improved indoor wireless to the point where I consider it to be somewhat good, but they have not had a viable 5ghz outdoor product for many, many years. Surprised anyone would still be using MikroTik. 60ghz on the other hand… PTP is unbeatable value for short range links, PTMP still trash
Correct. Many years ago when nstreme was first released, we got excited and made a major push to switch most of our wireless PtMP network to use MikroTik AP and CPE with nstreme. But it had many problems, both related to stability and performance. Then NV2 came out, and we switched to that. It still did not perform acceptably. It became clear a long time ago that MikroTik was not investing any more time or energy into proprietary wireless MACs like nstreme and NV2, and however well they worked several years ago, they still work the “same” today (on supported hardware). No better, no worse. Similar to the Dude, if you want to keep running it you can (feature isn’t getting ripped out of newer ROS versions), but it’s not being updated, enhanced, fixed, or maintained in any way. Just on life support. It is very much no surprise that they did not bother to port it to the 802.11ax chipsets they use.
Even Ubiquiti’s old 802.11n-based AirMax M platform runs better than NV2. These days, we continue to use ROS for actual routing, and find it is also acceptable for residential WAPs (802.11). But not for wireless WAN.
Sine NV2 was not carried forward, and no “NV3” or similar next generation has been introduced, I would agree it is strange that they are releasing ax outdoor CPE models, though. I can’t imagine what possible use-case one would have for them.
Their administrators are still convinced that 802.11ac is better than nv2. (yes, ac, is wanted)
From the lab tests this truth is overwhelming.
But they are all office workers, no one has ever gone out to get their hands dirty working with their own products as WISP.
I do not advertise for third parties, out of respect for the forum that hosts us.
I have used, or rather I still use where I have now mounted it, the shitty products of Cambium Shittium, crappy interface and ridiculous functions.
They always make me regret RouterOS.
The most expensive panels always send a maximum of 270Mbit/s radio despite the initial promises of future software with which to send 1Gbit/s radio up to 250 clients.
Already with 60 clients it struggles. Then with the 90° panels a polarity often broken because the PCB is made of shit and bends…
Not to mention the structural defect of the “large panels” in which electrolysis corrodes the screws and lets water in…
And anyway after the Shittium clients there is always at least one hAPac² as a CPE…
I could tell MikroTik anything, but over the years I have not had a single failure not dependent on lightning on the electrical system or on the pylon…
As for the Wa60Ghz products from the well-known manufacturer… 800Mbit/s up to 6Km with a very small channel…
And the aforementioned 5GHz with its proprietary protocol sends a lot… 4096 QAM…
And I almost forgot…
The chipset inside the Shittium CPEs is the same inside the 5XHD.
Ux sends them to 4096QAM with its own software, while Shittium does not…
If only Ux and MikroTik would get together…
223 / 5.000
Hi Tom! I'm in the same situation as you. I have thousands of NV2 devices deployed, and this has led us to a dead end. I can't seem to find an acceptable WiFi 6 or 7 solution. What path have you taken? Ux, Shittium, Mim (5 gear discontinued)?