nv2 will always use 6Mbit data rate for protocol communication.
How much air time is used on an AP with 30 clients (NV2) when all clients have a 54Meg or faster connection speed for the "
nv2 will always use 6Mbit data rate for protocol communication" ?
I would think if you have an active busy NV2 AP talking to dozens of NV2 clients during Internet peak usage hours (where the NV2 AP is aproaching saturation) and all clients have 100+ meg wireless link connections , that dropping way way way down to 6Mbit for "
NV2 protocol communication" would be injecting pauses in a busy wireless network that could have a degrading effect on total wireless throughput.
I like to suggest that if possible & feasable , to have the "NV2 protocol communication" use what is at least in the Basic-Rates settings. Thus if everybody is running well at BASIC-Rates set to 24 Meg or even 54 Meg , then the time used for "NV2 protocol communication" would/could be much less and much faster - which should have an effect of faster AP-to-Client and Client-to-AP customer data stuff.
Sooo - the big question if if this is possible ... Just how much faster could an NV2 network run if "NV2 protocol communications" supported and worked with the configured Basic-Rates settings ???
North Idaho Tom Jones
My concen and guess is that Mikrotik is fully aware of this potential wireless limitation and are unable to have mgt protocol use higher bit rates or any switching could impact on mgt protocol functionality : maybe just maybe Mikrotik have set ROS functionality a higher priority than wireless performance : all of this is of course speculation but I keep asking myself why does other vendor's with a similar chipsets and much simpler OS have better wireless performance ?
Sent from my SM-A300FU using Tapatalk
It would be interesting if Mikrotik was to so this type of test:
- AP with many wireless clients
- Saturate the wireless traffic from the AP to all clients (then later reverse the direction and test again)
- Connect an oscilliscope to the AP antenna (or a seporate tuned antenna next-to/close-to the AP antenna). Or connect it to a test point to be able to see TX and RX traffic.
- Look at the oscilliscope for dead nothing-happening time periods.
- Then overlay those dead silent time-periods with a what is happening at that moment.
- Also ,,, overlay the time-periods of 6-Meg connection rates and see what is happening at that moment.
After the data is corelated , then have a wireless software programmer look at those time periods and attempt to make some wireless software changes in an attempt to reduce to a bare minimum all of the dead silent wireless TX & RX system where the wireless network is saturated.
As an old Electronics Engineer, I know getting a graph of TX & RX and dead silent periods should be fairly easy and simple to do.
However, It might require a good wireless software engineer to figure out what part of the wireless protocol/software was responsible for dead-air & 6-Meg rates and check/review/modify the wireless software code in attempts to acheive faster client throughput during wireless saturation.
Also - perform the same testing with a Point-to-Point (AP to Clinet) and perform the same procedures to improve customer wireless thorughput.
I am willing to bet , there is a superising amount of dead-air and 6-Meg connection rates , and other possible things that can be discovered and improved on to improbe throughput
North Idaho Tom Jones