Seems so not ready for prime time… Again there are huge timeouts lack of ability to log in with winbox and on and on. If this continues to the actual 3.0, then it won’t be our CPE platform… Still drops out when 5.8 bandwidth test goes over about 8mb/s from the ap. This was the same problem that Ubiquity finally fixed with their latest release of firmware on the LS5. Same driver? Put the ntp package on a 133c and disconnect it from it’s time source and the system is unuseable…
It gets so slow and 100% cpu that it’s unusable. I could run without the ntp package, but even without that, it will not transfer data continuously above 10mb/s without dropping down to 1-2mb/s and testing to 2-3mb/s to outside testing locations i.e. nitro.ucsc.edu…
Something is really wrong with the wireless side of things. The ntp problem has been there with all 3.x betas…
for now i recommend you to leave the NTP package disables (since it uses the most of the free memory) - we are looking for solution how to improve it. Also I recommend you to disable the routing package and also advanced-tools package.
I removed routing and advanced-tools. That does keep the box more responsive. BUT the AP->CPE throughput still is trashed. Anytime the AP transmits more than 10mb/s the cpe throughput falls to nothing. That’s UDP, and TCP there isn’t more than 3mb/s down from the ap. This is trivially reproduceable. It looks exactly like the LS5 from Ubiquity looked like before their latest rev. I’m guessing buffer overrun. Without this fixed there is no use using 3.0 for any kind of fast link…