OK, I don't know what the problem is, so I'll just explain what I did.

AP is running ver 2.9.48 on 112 board, Ubiquiti SR5 radio. Client is running ver 3 RC9, on board 133c, R52 radio. 5Ghz band, 5180 MHz

It *feels* slow, if you do a ping you see many time outs.

So, we downgrade the client to 2.9.48 remotely (he's 120 Km away, so I really don't what to drive there) and live is beautiful again, it *feels* much faster, says the client and no time outs at all when pinging.

So, with 2.9.48, it works not with 3 RC9, WHY??? Are there any default parameters that change from one version to another? Any setting that I could change on the ver 3 RC9 that would make it perform as the 2.9.48? (on the wireless links I would assume.

Jorge

With rc9 did you look at CPU?

I would remove any unneeded packages and see how it goes.

And why are you using an RB112 as an AP when MikroTik explicitly tells you it's designed for use as a CPE device because of it's low horsepower?

That's simple, because I bougth 6 RB 333 to be used as AP, but they give me so many problems that I rather use the 112.

I'm 99% sure that it's a software/config problem, because I can only use ver 3 x on the 333s. Using 2.9 gives me no problems on any hardware, this is the reason I'm writing in this forum!

For now, I'm buying 532s only to replace the 333s, with high hopes that this issue posted before is fixed, or that least someone tells me a way around it.

Maybe there is no way around it, maybe I'm the only one in the world that has a 100 Km link working fine on 112s with 2.9 but has erratic behavoir after upgrading to 3 RCx on RB 333s... and that is why nobody has noticed this...

The other 333s that I have seem to work fine on short links, say less than 10 Km, but above that, forget it.

Jorge

BTW.

Only the very basic is enabled: advanced-tools, dhcp, routerboard,security, system and wireless.

on the CPU issue, I did check the CPU, with v3 it was between 2 and 6%, but every 5 or 10 secs it jumped to 100% then back to between 2 and 6%

After the downgrade, cpu load stays at 0 to 4%.

Jorge.