I solved all my NV2 AP disconnects by improving each AP antenna enclosure shielding from each other this has reduced the signal pickup from the other AP's and stopped NV2 disconnects,Hello.
Still is there problem that causes disconnects on links with NV2 !!
A lot of solved with MK support.
Links have good signal (-50 - 60), good CCQ but still disconnect, not responding. Problem persist in all version 5.x (also in 5.14)
It happens on 200meters links (with a sextant), but also on the 9 km links with high-quality parabolic antenas.
This is reflected in the single 802.11N but also in the N 2x2. If on the same link is NV2 disabled, there is NO problem with disconnect.
Have anyone same problems? Thank you
This NV2 link works on channel 5680. There is NO network on same chanel. See scan...I solved all my NV2 AP disconnects by improving each AP antenna enclosure shielding from each other this has reduced the signal pickup from the other AP's and stopped NV2 disconnects,
http://forum.mikrotik.com/viewtopic.php ... it=rx%2Ftx
Never had NV2 disconnects with grids but I moved them as far apart from the AP's on the mast,
When you scan from each antenna what is the pickup signal level from this scan of other nearby units,
I also hope!I have the same problem (perfect db -53 to -60, not noise, etc.) ... I'm looking for 5.15 every day with the hope of a fix...
Have you tried moving this effected antenna to another nearby location (even on a temporary mast) and checking.Dear MT team.
How do we report this problem? Via email no answer from support.
I have generated supout.rif after disconnect with 5.15rc1(12.April) and still disconnect.
It's not a problem "one link".Have you tried moving this effected antenna to another nearby location (even on a temporary mast) and checking.
Is this happening on just one mast with ptp's + ptmp's AP's or several masts, also when you updated OS version have you updated firmwareIt's not a problem "one link".Have you tried moving this effected antenna to another nearby location (even on a temporary mast) and checking.
The problem occurs in most links (PTP) and a large number of sector antenas (Point To Multipoint)
there have been made multiple Nv2 stability improvements since v5.8.In my opinion you are all wasting your time trying to find a fix - we have done extensive field testing and have found the ONLY successful NV2 installations are way out in the country where there is NO other RF - we have concluded that NV2 is extremely susceptible to even the slightest of interference. Having said that we gave up testing at ROS 5.8 so it is possible they have improved it since then.
As for NV2 improvements since 5.8, if they are worth trying, why are they not documented in change log...
A very interesting comment can I ask have you got a 5-6 GHz spectrum usage graph to support this theory, I certainly haven’t wasted my time in fixing my NV2 disconnects as it’s now working perfectly.In my opinion you are all wasting your time trying to find a fix - we have done extensive field testing and have found the ONLY successful NV2 installations are way out in the country where there is NO other RF - we have concluded that NV2 is extremely susceptible to even the slightest of interference. Having said that we gave up testing at ROS 5.8 so it is possible they have improved it since then.
I mentioned this before, why cannot MT just grey out any wireless setting not used when NV2 protocol is selected.to my best knowledge the hw-retries are ignored by NV2 (and nstreme too)...Have you tried to increase hw-retries? What data-rates have you selected?
VAP does not work with NV2 protocol, which is a pity.Hi I have the following problem.
I have put all clients in the NV2 Nstream 802.11 protocol. Then when AP is still in any protocol clients can still connect to the VAP on the distribution, but as soon as I change the AP to NV2 protocol all clients disconnect. Clients only register when AP is back to any protocol.
Can anyone please help in this regard? Maybe I'm doing something wrong.
Thank you. Good to hear this message.we will try to do some more testing with 2x2 on Nv2 protocol.
For other that has problems with disconnection, you also use 2x2, or it is also happening for one stream operations?
send to supportplease provide us support output file in a new support ticket about this router.
We need support output file from this AP and as well from those 6 clients.
distance is from 34meters to about 500metersLooking at the signals (tx/rx) from registered clients from -36 upwards, what distance is these clients from the AP.
Also fourth client down -52/-65 after 5.30 minutes rx/tx rate of 6Mbps should be higher
You working with this setup in N 2x2 ?Try to setup connection without QAM-64 and is much better now.
See settings in attachment (must disable MCS 5-7, and MCS 13-15 - on basic rates too).
rate selection algorithm: advanced
You say mostly shielded can I ask have you shielded the SXT as this is the first item to start with and there is two methods external or internal, I have attached two pictures one for external shielding for a Sextant and my own internal shielding of a SXT using first 25mm copper strip painted over with conductive paint and earthed back to the board, which before shielding was picking up signals from AP’s from the rear of the SXT but after screening they were not.................... Setup is in (mostly shielded (6m underground)) laboratory, both clients are SXTs. I also saw a post about lowering the TX power on wiki, tried that, didn't help (not even a tiny bit)
You probably know where I'm going - from this view it really totally looks like a hardware problem (on ~30% of new wireless cards!). Please tell me it's not :].................................
Hello. We have still problems on P2MP links. It is 802.11N with NV2
clients who have ROS 5.9 are most stable then clients with 5.19.
Any client when is downgraded to 5.9 - then have good uptime and little disconnect.
With 5.18 and 5.19 a lot of problems with disconnect
Have anybody the same problem?