i have done it too the results are the same, i already mention, the older running link is performing fantastically at same distance..with normal 5GHZ turbo. and in this older link when i run btest on the RB itself, then its easily push 36 Mbps in one direction with a problem.you are running bandwidth test on the groove itself? this is the problem. bandwidth test generates a lot of random data, this impacts the CPU and you don't get any speed. correct way to test is:
[powerful pc] --> [grove] -- [groove] ---> [powerful pc]
i have already done all possible settings without any results. i have pour my 7 years experience into this link. enabling HT above/below downgrade the through put upto 3-4 Mbps. only in one direction. surprisingly when i configure these groove to traditional 5GHz 20 MHz then it give 14-15 Mbps in one direction and when i try to use NV2 or nstream on AP and leave the protocol mode to any in client side then the link wont connect even.please upgrade to v5.6
Try using advanced rate-selection in the Data-rates tab (do that on both AP and station).
Enable the 20/40Mhz HT Above(Below) channel width to use 40mhz option cince you were using 5ghz-turbo in old setup.
Make sure you use the same frequencies.
Try disabling adaptive noise-immunity on both ends.
Try enabling Nv2 or Nstreme protocol to get more speed as with regular 802.11 with WDS you will not get the max speed.
i dont know why, its a mere 6 km link but it appears to be 60 km link. one more thing the link only connect only on frequencies which are marked as bold in drop down list of frequencies. if i try to connect on any other frequency then also link dont connect... this is first time i m seeing this.your signal is -50/-50, how can the link "not connect"?? either your nv2 settings were wrong, or some other reason. upgrade to v5.6 where we have more detailed logs, and make a supout.rif file when it doesn't connect
this is not a problem as long as the scan list setting is configured in the client.Just noticed you have "no_country_set" and superchannel in frequency mode
yes, this is strange. try to set something there, on both ends. For example on client side "any" and on the AP side try out 802.11, then test with nstreme and also with nv2.also wireless protocol is not specified