It seems that MT has done a good job with this candidate release. DNS problem resolved. Wireless and Hotspot perform faultlessly so far. Winbox connection through both IP and MAC levels is stable. Ethernet and wireless connections also seem faster.
This is for my routerOS in x86. I have not upgraded my mini boards yet. I am looking forward to a rock-solid release of V.3 with excellent wireless and hotspot performance because, as normis commented earlier in some other post sometime ago, MT staff won't work seriously on usernan's new features until this is achieved.

This release is worse than rc6.

Associations on a B radio (XR2) went from excellent to completely unusable -- links that were at 60% are now showing up at 80%, and connection quality dropped from better than 70% down to below 20%.

I upgraded because the hotspot just would not do RADIUS authentication in RC6. It didn't even bother trying to send packets out to my server. Up until that point in the login process, hotspot works fine. But without that, i's useless to me. And now with the link quality problem, I can't even test whether RADIUS is fixed. I'm using the same config that works fine on 2.9 routers (rb532's).

As far as I'm concerned, this is no where near a proper release candidate. The fact that they're up to RC9 is indicative enough that 3.0 is not anywhere near ready for release. Unfortunately we're stuck with it on RB333's.

The crappy radio signal seems to be related to having a virtual AP interface enabled. With that enabled, all associations to the physical interface degraded severely. After disabling it, things went back to normal.

Yes, i confirm this problem in rb532 too, but i need vap enabled. Back to rc7.

Looks like I should hang on to the older version for my mini boards at this time and wait for more confirmation. (all my rb153 are still on 2.9.x.x and I did bother upgrade them to v3 as they are quite stable). The reason I use v3 for my x86 is I want to use the userman features which my mini boards can't handle with little memory. Well I am still happy that CR9 rids of the DNS problem in my x86 unit.

Hi!

RC8 looks quite good long-distance 5Ghz links. Still problems with 2,4Ghz AP mode (RB333).

Since this RC8 works OK, I've decided no RC9 upgrade right now. Waiting for more experience.


I power up one of my RB333 with RC9, and test it. I came back with results.


Rgds

Zsolt

RC9 is running smoothly on my RB333, RB532 and X86. The Ethernet interface and the usermanager problems have been resolved.

The only problem here is the poor wireless performance with vap enabled. The ccq is not stable and the latency is high.

about problwm with VAP, please make the support output file from routers where you have problems and send to support@mikrotik.com.
Does that problem arise when you have lot of clients connected to that VAP?

No, maximum 3 in vap and lot of clients connected to normal interface. I will send the supout.

Supout send. One more problem: if disable the master interface some clients in vap don't come back, need reset the router.

I need to use two of my rb333 for two open wireless access points w/r52 cards. With simple NAT between wireless interface and ethernet and simple open AP 2.4ghz only (no hotspot, no logging in, no pppoe nothing) can I expect the two APs to run for 10 days?

I have a project I need to provide coverage to a football field for 10 days.... I want to use what I have in hand instead of buying more stuff for a week long project. I plan on putting 2 APs there so if one dies the other still runs (both RB333 w/r52 and rc9 unless someone tells me to use different rc...)

Thanks,
Scott

can I expect the two APs to run for 10 days?

as long as they are protected from weather, and have power for the whole time, you can probably expect it to run for the next 5 years...