*) routing-test - changes that are aimed at increasing perfomance and
reducing memory usage:
limit number of outstanding bgp updates, sending feeds to many peers
uses bounded amount of memory;
*) fixed bug - telephony was crashing whenever voice-port was changed;
*) ups - fixed: program was becoming unresponsive when serial ups was
configured but was not connected;
*) support for full frequency list of Atheros chips;
*) user manager - password not revealed on sign-up;
Speaking of updates, it seems there really is an improvement in wireless performance w/the 3.06 and later beta software (either that or a bunch of favorable coincidences in our testing). Any chance this will appear in the 2.9.x series? If beta for 3.x is anticipated to go on for a long time it would be nice to see the putative wireless improvements appear in the production branch.
Hai people
just finished update ROS, x86 as centralized AAA and RBs as wirelessly, userman as radius server is more fast and, for unwire system very...very...very.. quick assossiating..... and much ... much stable.
specialy thanks Mikrotik and Teams for
regsrds Hasbullah.com
Upgrading one system (office router here) I ran into a problem.
Probably just some quirk, but just to warn others or to give a hint what to check for.
I upgraded from 2.9.41 to 2.9.43. The router had the routeros-all-in-one package on it, with several packages enabled, among them the PPP and the wireless package).
After the upgrade (which took unusually long in that case) the router came up again, and was on 2.9.43. But nothing worked.
While checking I noticed the router was in the following state:
the upgrade package file still was on the router (routeros-x86-2.9.43.npk) - a sign that the upgrade hasn’t been properly done.
the package list showed the routeros-x86 package, but the only “sub-package” (shown indented in WinBox) was the system package.
Consequently most things in the config were “not there” (for example a PPPoE client - no ppp package was there…).
I was not able to make a supout of that state, as the supout command (WinBox and terminal) just returned without an error and without creating a supout file.
After another reboot the upgrade seems to have worked ok - the package file in the file are has vanished, and “/system packages print” shows all desired packages.
BUT the config for most things was lost (like the PPPoE client). Restoring the backup I made immediately before the upgrade worked, though, so everything was back running quite quickly.
So:
DO make backups - this is really a good habit
Anyone did notice a similar behaviour?
This would have been much more painful if it had happened on a remote router…
I had a similar issue upgrading a pc based MT, but I thought it was because I was going from 2.8.xx to 2.9.43 in one big step. I re-uploaded routeros-x86-2.9.43.npk and rebooted, it then installed the extra packages on that second reboot.
Yah, it works by rebooting immediately after I upgrade. Thank you Balimore.
I just was wondering why can’t my RouterOS sustanin the system time after rebooting? The system clock resets itself to Jan/01/2000. I’m sure it’s not the Millenium bug
They don’t keep the time because they don’t have a battery to maintain a clock circuit. Having you own NTP server is easier and more consistent for time.
:
