Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Anyone else seeing tremendous WISP slowdowns on UBNT 5.5.10 (versus 5.5.6)?

13 views
Skip to first unread message

Winston_Smith

unread,
Sep 22, 2015, 2:45:20 AM9/22/15
to
Anyone else seeing tremendous WISP slowdowns on UBNT 5.5.10 (versus 5.5.6)?

We have a neighborhood setup in the Santa Cruz mountains, where we have
been debugging a radio slowdown problem for weeks.

We replaced the router, the cables, the radio, etc., and just today,
we figured out, almost by accident, that simply updating the Ubiquiti
firmware from 5.5.10 to 5.6.2 (which we did a while ago), was what
seems to have caused the appreciable bandwidth slowdown.

Has anyone else out there seen a huge slowdown in speeds when you
"updated" your Ubuquiti firmware from 5.5.10 to 5.6.2?

Any idea why?

GlowingBlueMist

unread,
Sep 22, 2015, 12:38:09 PM9/22/15
to
Not your brand of hardware/software but I have seen similar on DD-WRT
upgrades. It took a reset to default settings, a boot, and hand
reloading of the parameters in use plus a final boot and things came
back up to speed.

I think it was too much leftover stuff from that or prior upgrades that
needed to be cleared out of memory after the final upgrade that was
needed. A pain having to put the configuration back in manually but for
me anyway it did the trick.

Winston_Smith

unread,
Sep 22, 2015, 12:58:33 PM9/22/15
to
On Tue, 22 Sep 2015 11:37:58 -0500, GlowingBlueMist wrote:

> Not your brand of hardware/software but I have seen similar on DD-WRT
> upgrades. It took a reset to default settings, a boot, and hand
> reloading of the parameters in use plus a final boot and things came
> back up to speed.
>
> I think it was too much leftover stuff from that or prior upgrades that
> needed to be cleared out of memory after the final upgrade that was
> needed. A pain having to put the configuration back in manually but for
> me anyway it did the trick.

Googling, I found on the ubnt forum that this is a nascent problem, which
is just emerging, which appears to be related to new statistics software
that Ubiquiti added to the latest release (which is, apparently, buggy).

More to come, I'm sure...

0 new messages