Is the latest rc7 stable enough for a production system? The old configuration how is converted to 2.9 format? Any rules in mangle,firewall,queues how will change after upgrade? What I am trying to say, after upgrade from the latest stable to 2.9 rc7 all settings from the old version work ok on the new one?
I would appreciate any comment from users that upgraded from a stable version to RC
We upgraded a production secondary site from 2.28.26 to 2.9rc5 or 6 a few weeks back. Most rules and stuff came across, except where the new features changed things too much… policy routing will somewhat disappear but should be resetup using the new format anyhow. firewall rules all seemed to come across - but should be double checked. If its mission critical i’d wait, if you can tolerate a few minutes of downtime while you convert things over then go for it. Keep in mind we are not using any wireless - only routing, firewalling and nat functions.
I can live with that to manually change/add some rules, but how about wireless (prism+atheros), bgp, ppp, nat, routing, any serious bugs?
I am also afraid if there are any chance, during the upgrade process, the system locks up or fail. Is the upgrade plug 'n play (just upload the required package) ? At this time is difficult to attach a monitor if any user intervention is needed during upgrade.
I really need the new features but I want to be sure that the system will run stable.
We’ve stress-tested RC7 with wireless in two modes
P2P radio bridge, on 600MHz platform, 65Mbps of traffic spooled constantly through it
AP in indoor environment, WEP / MAC authentication.
Both are fine. The AP’s have been “up” with no problems or resets for months with successive RC’s on them, and the P2P bridges for days at a time in lab conditions (we had an office reorg, so there was disruption).
Both cases are with Atheros cards, a mix of CM6, R52.
Security on wireless changed when upgrading from earlier 2.9 betas and 2.8, so if you have wireless customers hung off an AP you might need to change a few things.
Cannot comment on BGP, PPP, NAT, Routing or other L3 features.
Ok it works the normal package only if I set preamble to long. That way I can connect with another prism on mikrotik 2.8.28. If I use prism as AP clients must set long preamble. There was no preamble option on 2.8 and every client could connect whatever the preamble setting was.