RouterOS v4.5 released

What’s new in 4.5:

*) fixed Nstreme issues with bridged traffic
*) ipsec - added blowfish, twofish, and camellia encryption algorithms;
*) fixed static route removing;
*) fixed DHCP client compatibility with some DHCP servers;
*) added static multi-cast route support;
*) fixed temperature monitor on RB800 and RB450G;
*) user manager - payment bug fix - now able to buy
credits without extend price specified;

Download: http://www.mikrotik.com/download/routeros-ALL-4.5.torrent

Just downloaded, tried to upgrade without success.

02:00:00 system,error broken package routeros-mipsle-4.5.npk
02:00:03 system,info router rebooted

RB532A.

re-download, probably download was interrupted. use torrent, it has internal error checking mechanism

Is the NSTREME BIG BUG fixed???

BR

Strange… downloaded 5 times from different mirrors, every time same situation. Downloaded from torrent, works. Thanks :slight_smile:

Has the CSPF problem been fixed? Confirmed by me and mplsguy?

http://forum.mikrotik.com/t/te-tunnel-path/33821/1

huh, neither of two NetFlow ‘fixes’ is mentioned %)

and one of them is actually not fixed :frowning: maybe, friday would be a better day for the release?..

Normis - is the nstreme working fine and do not disconnecting? Many people waiting for this bug improvement.

What is *fixed static route removing bug ?

Please MT team give more info about it. I

http://forum.mikrotik.com/t/routing-changes-lost-after-reboot/34566/1

see my post here:
http://forum.mikrotik.com/t/problem-with-nstreme-on-4-1/32260/26

if anyone has sent us a recent supout.rif file with this issue, we will try to fix it. but nobody has, ergo there is no widespread problem with nstreme. only configuration issues.

I have updated to v4.5 because of a strange issue that may related to this route bug.

I see IPs in my ARP table that are not existing. I have deleted those IPs in v4.4 and removed their route. When I check Ip route, the routes are OK but in my ARP table, I still have IPs from the very same IP segment previously deleted.

When I try to ping those IPs, I get timeout all around the network. But ARPs are there on my main router.

Am I missing something ?

most probably you are receiving packets and they are MACs are registered in ARP, but your routing table does not have information where these IPs are.

After upgrade some of our NSTREME links started to disconnect too. I found out that after the upgrade the hw-retries was set to 4. After I increased it to 8 (on both ends of line) the problem disappeared (on multiple links). So I didn’t thouht that there is a bug in NSTREME but that the Mikrotiks are too optimistic when they lowered the hw-retries…

Hardware Retries was already lowered to 4 in ROS as early as version 3.18 and that didn’t cause any problems. I remember this was done to fix a problem with Ubiquiti XR2 and XR5 cards disconnecting. Before that, the default was 16.

Tom

hw-retries setting for the nstreme were not used in the v3.x
Only starting with v3.x wireless-test packages the hw-retries settings were used.

16? now 15 is the maximum :slight_smile:

Hardware Retries was already lowered to 4 in ROS as early as version 3.18 and that didn’t cause any problems. I remember this was done to fix a problem with Ubiquiti XR2 and XR5 cards disconnecting. Before that, the default was 16.

The maximum was 15, not 16.

FACE the REALITY .The problem is : all here use MikroTik is production envirnoment, we can not maintain a problematic link in production only for MK research… we need offer a GOOD QUALITY production link, bacause this, all people with the problem has been downgraded to 3.30. My suggestion is the MK TEAM mount a link with any spec showed here in forum by many many many users with the related problem ( use search button ) and CHECK AND FIX the NSTREAM problem…

BR

We have many Nstreme links installed, that are run with actual traffic and actual users. We don’t have such problems, and nor does the majority of RouterOS users. We have no real support requests at this time. If you have issues, please make a proper support request, with as much details as you can give us, and we will try to replicate the problem, and solve it.