I know that nstreme automatically adjust ACK timeouts to stabilize long links, but that nstreme is not yet ready to do that with “n” links. Has anyone tried manually adjusting ACK to get long links working? Does the ACK timeout adjustment parameter even work with N? Any idea what we should adjust it to (ie: set X * km where X is the number of microseconds)?
Randy
We have recently deployed a 35km link using R5N’s.
They tested at 110Mbit aggregate in a bench test, and we left the config the same.
When deployed we get a maximum of 20mbit, barely as good as a pure 5Ghz A link.
Would dearly like to know some tweaks to improve this links performance, i believe timing is the cause of the severe drop in performance.
What you’re seeing is about par for the course.
If you can find it, drop back to 4.0beta3 and give that a try with nstreme on. That worked pretty well for us, everything since has been a step backwards.
Here are some good settings specifically for 4.0beta3.
Thanks for all the tips on getting these working better. We’ve followed many of them, here are the ones that seem to have helped us so far:
- No WDS
- Short preamble
- No Periodic calibration
- Nstreme on, but CSMA not disabled
- Nstreme best fit
- Play with power levels until we get best results. Seems pretty picky on this.
- Be sure the routerboard firmware (not just RouterOS) is the latest revision ( /system routerboard print and /system routerboard upgrade)
George