So far no dice on a 100km link with just one chain on R52N’s. Just can’t get it to let me pass traffic. It shows a -67 rssi, with low noise, but only trains at 6M and I can’t get traffic to pass. 8’ dish on one side, 4’ on the other in case you’re wondering.
I suspect ACK isn’t working right as the current-ack-timeout floats between 165-300, should be longer.
Any other tips for getting this link up? We’re about ready to swap out to R5H’s, but I hate to…
Thanks,
Randy
ACK cannot hold on such long links. That is why nstreme exists. But we need to wait for it.
Perseverance pays off. 
I ended up being able to get to the far side with a very slow unstable connection, and made some changes.
I ended up on single chain 802.11n with nstreme and it seems to be working well. Will try with more traffic later today. I set the far side to 5GHZ-a/n so I can fall back to A if I need to.
Anyone know if the 802.11n nstreme “issues” are with N in general, or just with multiple chains? Or is it an issue where nstreme can’t keep up with the higher speeds?
thanks,
Randy
you have a lot of guts… 100 Km…
i think you are pushing N to the extreme.
try A cards and use Nstreme dual, it will probably give you more than N at that distance.
Steven
I did end up deploying it with A for now, anxiously awaiting the time I can upgrade the link to N with a software upgrade