RouterOS v3.1 Released - Wireless disconnection issue solved

RouterOS v3.1 has a fix for wireless disconnection problem, that was happening after upgrade from v2.9 to v3.0. All that had those issues, please upgrade to RouterOS v3.1.

What's new in 3.1:

*) fixed wireless reassociation issue;
*) added support for Novatel Wireless Merlin XU870;
*) added support for nForce Ethernet cards;
*) fixed bug - user manager database in-use counter was wrong
     for database size over 21 MB;
*) console - fixed parsing of alphabetical operators ('and', 'or', 'in') in
    expression context, this also fixes default configuration revert script;
*) fixed TKIP on RB300 and RB600;
*) fixed ipv6 firewall connection-state matcher;
*) improved WinBox connection speed & memory usage;
*) report correct tcp-state for firewall connections;
*) fixed ppp user names in ip accounting;
*) fixed via vt6122 (rb600 ether3) driver: multicast packet receiving
   did not work properly;
*) user manager - voucher template supports kb/mb/gb for
    download/upload/transfer limit values;
*) added ":led user-led=[yes|no]" command for RB100/RB400/RB500 series;

What exactly ws the problem that is observed? I have a disconnect problem but am not sure of it is the one resolved here…

I am asking about the wireless disconnection problem.

The problem I had was something about a key update problem…

x86 version of 3.1 appears to be an invalid torrent file. The other versions download OK.

I tested and it works fine with this one:
http://www.mikrotik.com/download/routeros-x86-3.1.torrent

No luck here. μTorrent says its an invalid torrent file but the Mips torrents worked OK…

X86 not working for me either with Azureus..

-Gerard

MD5 of this attached file is: fe412e573d5122c5efe9825327b67684
does it match?
routeros-x86-3.1.torrent (5.52 KB)
md5sums-1.2.zip (28.1 KB)

The file from the forum works fine..

I compared the md5’s on 3 computers I downloaded the .torrent on last week and they all matched each other but did not match the forum file. I then redownloaded the .torrent from the website and it works fine now too..

All I can think is that the proxy you use was serving an incomplete version of the x86 torrent for a while.

Thanks,
Gerard

yes, it probably was cached somewhere with some missing bits. that’s why we made an MD5 section on the download page now - you can check if the sum matches, and so make sure that the download is not corrupted or messed with.

I’ve had some problems when moving (dragging) firewall rules on 3.0 in Winbox - their settings revert to a default of ‘prerouting’ and ‘passthrough’.

I seem to remember this was an issue in an earlier RC release - has this been addressed in 3.1?

let us know how to reproduce this. does it happen all the time? in our experimentations there are no such issues

OK - create 1 new firewall rule (mine are in mangle) and apply/ok.

Create 2nd rule before moving the first, and it will glitch when you ok it - when it recovers, the rule defaults to prerouting and ‘accept’.

Its now that strange things happen - if you select both rules and try to drag them together, it sometimes works, sometimes doesn’t and sometimes defaults the settings.

Trying to replicate a fixed method of this is very frustrating. I create a rule, move it, it gets ‘stuck’, then might jump into place. If I log out then in again, it doesn’t always take my edits.

After trying this, the router PC has become unresponsive but still passing traffic… :frowning:

System is AMD 1.8GHz 768Mb RAM, v3.1 x86