MikroTik RouterOS version 5.0beta2 released!

RouterOS General
1

What’s new in 5.0beta2 (2010-Apr-30 08:44):

*) added wireless distance setting, removed ack-timeout;
*) improved 802.11 operation for outdoor distances;
*) fixed sstp on x86;
*) console - removed ‘delay’ argument from ‘/system scheduler add’ command;
*) console - remove ‘comment=“”’ values from export;
*) console - updated ‘/system script job’:

  • also show active login sessions here;
  • new read-only property ‘type’ with values “command”, “login”
    or “api-login” for running commands and either kind of login sessions;
  • new optional read-only property ‘parent’ with id of the job that
    has spawned this one;
    *) console - changed “started” property of ‘/system script job’ to use
    local time;
    *) console - new property ‘type’ in ‘/system script job’
    *) console - added ‘/port remote-access export’ command;
    *) console - fixed bug that caused “cannot set …” error when using
    some properties in ‘find’ commands;
    *) show old software id in export file header;
    *) api - can supply password to ‘/system/upgrade/upgrade-package-source/add’;
    *) api - ‘print’ command was not showing values of some properties
    such as ‘servers’ in “/ip/dns”;
    *) api - fixed api login sessions not dissapearing from ‘/user active’ after
    termination;
    *) ‘/user active’ now lists type of api connections as ‘api’;
    *) added support for hardware watchdog on RB1000 & RB800;
    *) added support for ASIX AX88xxx based USB Ethernet Adapters on RB4xx;
    *) fixed problem - ipv6 traffic was not bridged if ipv6 package was not enabled;
    *) fixed getting interface stats in dude;
    *) fixed metarouter stability problem on RB400s & RB750s;
    *) fixed metarouter - it didn’t work on RB1000 with 2Gb;
    *) fixed metarouter - it locked up on RB800;
    *) fixed problem - SFQ queues did not work on interfaces (wireless) if none
    of simple or tree queues were added;
    *) fixed RB800 temperature;
    *) fixed problem - WinBox crashed while opening VAP interface;
    *) dhcp server - fixed possible inactive dhcp server in case of many
    dhcp leases with address-pool enabled;
    *) dhcp server - show non-printable option 82 agent-circuit-id and
    agent-remote-id values in hexadecimal notation
    (in the same way as client-id is shown);

http://www.mikrotik.com/download/routeros-ALL-5.0beta2.torrent




Important note:

Beware that 5.0beta2 version is still beta version, and may contain bugs,
therefore should be used on non-critical systems at first. Any issues found
(including crashes, lockups, degradation of performance) should be reported to
support@mikrotik.com, accompanied by supout.rif file.

As of version 5.0beta2 wireless interface “ack-timeout” setting has been
replaced by “distance” setting. Not only distance setting should make
configuration easier, but additionally should improve long link performance,
especially 11n performance. Distance setting does not apply to nstreme
mode.

“distance” can be:

  • indoors - standard 802.11
  • 1…1000 - approximate distance in km
  • dynamic - to be detected automatically upon registration, the same way as
    ack-timeout=dynamic before.

Default value of “distance” setting for fresh installs and upgraded systems is
“dynamic”, no matter what previous value of “ack-timeout” was. Therefore after
upgrading it is strongly recommended to check what is the dynamic distance
estimate.

It is normal for dynamically estimated distance to be off by a few km from
actual distance and also change from card to card. It is always possible to
change over to static distance setting and find the value that provides the
best performance.

If dynamic distance estimate is erratic: obvious huge difference from actual
distance (>3km), significantly different distance estimate in multiple
registrations between the same devices, it is advised to change over to static
distance setting.

In order to get the benefits of this feature, all devices in wireless network
must be upgraded.

In point-to-multipoint networks, the value of AP distance setting should
reflect the distance to the furthest client.

New wireless features in the new 5.0beta2
2

*) improved 802.11 operation for outdoor distances;

Does this refer to the ack-timeout change, or are there improvements in nstreme as well? For N?

3

If dynamic distance estimate is erratic: obvious huge difference from actual
distance (>3km), significantly different distance estimate in multiple
registrations between the same devices, it is advised to change over to static
distance setting.

Where do you see the current estimated distance?

4

usually it’s two different changes if they are two different lines in changelog, however soon you will see lots of other wireless improvements, this is only the beginning

5

Are you looking to replace nstreme with TDMA, or supplement Nstreme with TDMA?

/int wireless set 0 ?
…
tdma-additional-txrxguard
tdma-debug
tdma-override-rate
tdma-override-size

My first try with non-nstreme N on a long link (35km) didn’t work out at all. I would get a sporadic ping across the link for a second or two then nothing more. Tried dynamic as well as 34km, 35km, 36km, etc…

Working well with nstreme, using wds, one chain, enabled only MCS 0-5 and no A/G rates.

6

Looking forward to testing out beta2 on all my long PtPs over the weekend.

7

:open_mouth:

For example?
Give us a preview..

8

Another 7.5km link with N, non-nstreme and vpls was working fair under 4.5. Now under 5.0b2, much better. It calculated the distance at 9km. Tried 7 and 8, but 9 seemed to give best CCQ - now in the high 90’s vs 70-80’s before.

Wonder if the new distance settings don’t work with WDS?

Also wonder if this is already using TDMA? :slight_smile:

On my long link it’s working better than before with Nstreme as well.

9

torrent is broken … no seeds or something.

10

wahooooo… my first success at fixing the broken torrent download. I got all the files in place and I think I am seeding it now.

11

v5b1 and v5b2 RB450G issues: http://forum.mikrotik.com/t/downgrade-back-to-4-x/37249/12

Another issue I have: the Supout creation is taking too long now…

P.S. I down+upgraded anyway, from v5b2 backup usermanager, then to v4.9, then back to v5b2, restore userman db. Seems working.

Supout still taking too long to create or it will not make it at all.

P.S. 2. So I’m loggin out and loggin in with WinBox. CPU is still at 100%. So the supout creatiion process has crashed. Please dev team, catch those exceptions, could you please ? Thanks.

12

I have test 5.0b2 in a 411A whit sr71-15.
I think is little better than 4.6. 1 or 2 more Mbit in tcp passth, CCQ is egual than 4.6 version.
A little bug, in wlan interface windows at Status tab → Routes Os version not show correct version.

13

bug in ping windows,
the scrolling is not working and some time there is a wrong report of the percentage of the packet sent.

About wireless and N it is still needed WDS to have the best performance ever.
Using nstreme+N it is not working as good as nstreme+N+wds

regards
Ros

14

Bug in scripting:

The following code no longer works and returns the error message “Script Error: cannot compare if string is less than string”:

:if ([/system resource get version] < "4.6") do={
  :log error "This script is not supported on the installed ROS version.";
  :log error "Please install ROS v4.6 or higher.";
  :set failedtests "1";
}

This works on ROS 4.x.

15

This is because it contains the word beta, which is not numeric. It should work fine for final v5.x

16

hmm, reading all these post about bugs I am eager to see beta3 coming!

17

maybe they are adding a TDMA type protocol… sometimes no answer, is the answer :wink:

e.g. once N was released, it was stated by Mikrotik that Nstreme was not designed for N. And ever since, they have been pretty much silent on the matter. I took this as “we are working on TDMA but dont want everyone bugging us” which seems to have been the case. But, it’s not in the release notes yet, so officially it doesn’t exist!

18

Testing on RB411U with R52n

  • when creating ap bridge with virtual APs, when you use SSID on the main wlan1 interface every connection to VAP causes reboot
  • when connected do RB411’s VAP, cannot access the RB411 (no icmp, no winbox); no firewall rules are defined on this box;

Above happens on 4.9 as well (currently investigating)

19

PPPoE on RB450G causes problems. I think it drops clients from time to time and does not reply to them in time. If this happens again I will downgrade to v5 beta 1 and see what happens. Could this be due to the RB450G CPU goes to 100% with 45Mbit of PPPoE traffic ? could be.

Too bad I can’t downgrade to 4.9 without me having to do a lot of reworking in the User Manager.

20

One side 3.30 other side 5.0beta2 both side R52 cards 5Ghz turbo mode x86 routers, one side ap bridge other station wds. Enable nstreme on 5.0beta2 when other side connected router hang up, need to disconnect power to work again.
Combination R52 card, x86 router and nstreme don’t work :frowning: .
Without nstreme work.
Other link but some older no name atheros 5211 card with nstreme enabled work normal.
Disconnect antenna go back to 4.9 and now is ok.