I have two Celeron 1.5ghz systems running 2.9.41 with SR5 cards shooting 3 miles. I have a -58 signal on each side. I am running with Nstreme and polling enabled. The issue is the low CCQ and dropping pings with slow response times.

If I reboot both sides at the same time, the CCQ numbers bounce all over from 70% to 90%, and I drop about 4% of my pings across the link.

If I reboot only one side, then the CCQ numbers are 100/100 on both sides, and everything is happy. (0% dropped pings)

I have another identical setup going 28 miles (with -65 signals) that does exactly the same thing running 2.9.38.

It would seem there is a bug in the MT wireless code?

I have two Celeron 1.5ghz systems running 2.9.41 with SR5 cards shooting 3 miles. I have a -58 signal on each side. I am running with Nstreme and polling enabled. The issue is the low CCQ and dropping pings with slow response times.

If I reboot both sides at the same time, the CCQ numbers bounce all over from 70% to 90%, and I drop about 4% of my pings across the link.

If I reboot only one side, then the CCQ numbers are 100/100 on both sides, and everything is happy. (0% dropped pings)

I have another identical setup going 28 miles (with -65 signals) that does exactly the same thing running 2.9.38.

It would seem there is a bug in the MT wireless code?

The same happened to us, and we have upgraded to 2.9.42. We will do testing on this release hoping the upgrade will help :/

Anyway, I will also try to reboot on one side to see if that helps.

If somebody has more comments...

Question: does it have any preference on the side that you must reboot? Did you investigate on this ?

Another question: does it show a lower bandwidth when it does not work, like for example half of the value in the normal situation? We have this kind of problem: 3Mbit/s full duplex instead of 8/9Mbit/s full duplex

Thank you

It does not matter which side we reboot, but we can only reboot one.

We still get full-speed, less the 3-4% packet loss we see on the link.

This is happening on two completely seperate links. Exact same problem.

I have sent a supout file to support a week ago.