I have the problem with station WDS links more than standard station. It seems like the WDS links disconnect all within a seconds of each other then sometimes will reconnect within a few seconds and other times they will have a hard time reconnecting and won’t even show the AP they are supposed to be connecting to in the wireless debug log.
It does happen on non WDS links also but not nearly as often. I have played around with NV2 settings but nothing really seems to help with the problem. This is a pretty noisy area in 2.4Ghz but the clients have good Signal strengths and good CCQ when moving data and I don’t see the disconnect issues when running Nstreme or 802.11.
For example I have four clients within 100 yds of each other two are set up as station WDS and the other two as stations, all with almost identical signal strengths and quality. The two WDS clients will disconnect within seconds of each other while the station clients remain connected. This is a pretty noisy area for 2.4 but I am able to push ~14Mbps the all these clients individually. But the disconnects are a huge Pain, reminds me of the “extensive data loss” problems that have plagued MT for years now.
I know there are others having these same issues, has anyone found a cure for it yet?
I opened a ticket yesterday and sent in support files but have not heard anything back yet. The current ticket number is 2011052366000116
Hi, I confirm I have the same problem in the 5 GHz band. The standard 802.11 or NST works without problems. I was expecting great strength NV2 using P2MP. When using NV2 frequently appears in the log Lost Connection Control frame timeout
and the Lost connection, medium-access timeout. I used different settings - no change.
there are a few improvements in v5.3 in this area, maybe it could help. we have not been able to reproduce this kind of issue in our testing, but the fix could help.
There are a lot of people who seem to be having the same issue. It happens on every AP I convert to NV2 it doesn’t seem like it would be super hard to reproduce as long as you are testing in a real world outdoor noisy environment.
I upgraded an AP and a few of the clients having issues from 5.2 to 5.3 and it made no difference at all, in fact it is a bit worse and we now have ethernet port flapping issues.
we don’t need it anymore, problem has been identified and fixed in v5.4 which is already available to those interested. when we complete testing, we will release it.
Chad, on these disconnection nv2 links, do you use nv2 security?
I have the feeling it makes a difference in busy spectrum with other nv2 channels around.
I have tried both with and without security, it doesn’t seem to make a difference in my case. I have reverted back to Nstreme for now.
If MT can’t reproduce what so many users are seeing and having problems with I don’t have much hope of them fixing it anytime soon. I am contemplating just making the switch to UBNT and being done with the headaches.
Probably you’re up for migraines in that case.
I am in the process of removing all ubnt stuff from my network. Apart from the lack of options compared to ROS, some product lines are not half as reliable as MT stuff.
But my main issue I had was in a mixed network where nv2 can’t be used (nor the airmax, remember that you have to change all units into ubnt!) the ubnt units had much more issues with disconnects than the ROS radios.
Some other measures I took to reduce the disconnect I had on my (5G) networks:
Go for 10Mhz bandwidth channels.
Separate as much as possible the available channels. It seems nv2 just needs more ´space´ to work than legacy modes
Fixed conn rates. Set CPE’s to default and let the AP pick only one or two rates. Makes the network much more stable.
I found that with NV2 channel spacing preferably would be better than 20Mhz, ideal is at least 40Mhz.
Off course that is in 2,4G band not even possible. To my opinion this is also the reason most disconnect issues with NV2 still around are from 2.4Ghz network users.
Oh, by the way, I have one short range link (15 mtrs!) between two NS-loco’s with airmax enabled. I had many disconnects with these as well. Only when I removed the airmax (=tdma, like nv2) link became more stable.
But since competitor with ubnt-Airmax based network and several AP’s is overshooting this link the disconnects never really disappeared. This while their signal levels where much lower off course and the closest freq. still some 20Mhz away from my centre freq. Only until I started to use an indoor channel nobody else uses the link stabilized.
My opinion is that TDMA is more aggressive in interferences towards other radio links. AP in NV2 mode is just transmitting at full power all the time, even in idle conditions. Where legacy AP radio only transmits in full power when data needs to be move.
Also, in MT ROS I just have more tools to cope with it.
Hence my prediction …