*) route - fixed cause of crashes when handling multipath routes;
*) route - fixed limit on maximum active IPv6 route count,
was causing issues with more than 2000 active routes;
*) ipsec - added command kill-connections under remote-peers;
*) ipsec - fix responder side phase2 negotiation problem
which prevented more than one Windows7 host to initiate SA;
*) fixed vrrp - interface was invalid after undoing remove;
*) winbox - added more detailed /interface ethernet stats;
*) winbox - added ability to send e-mail;
*) winbox - added missing ‘set-metric’ parameter
in ‘Routing/Prefix List’;
*) wireless - 802.11 dynamic distance fix;
*) fixed problem - packages could not be uninstalled if disk was full;
*) fixed problem - some of the RouterBOARDS did not reboot properly sometimes;
*) fixed problem - VLANs on bridge interface did not work;
*) ssh - client supports public key authentication;
On MT official site is written:
x86 does not currently support Nv2 (requires RouterBOARD hardware)
x86 may be supported in the future
I’ll upgade 1 link and watch it for a few days first.
Glad it’s released, would love to roll out NV2 on a few areas, already have the SXT’s lined up and a few installed.
I upgraded an RB running 4.16 to 5.0 that had the NV2 package installed and when the router came back up it didn’t have any wireless package enabled and lost all the wireless settings. Is there any way around this issue?
I lucked out in this case because it was the local side that I upgraded, but it could have resulted in a frustrating truckroll.
Seems there is some issue with the ethernet switch functionality on my RB1100
Trunk in on ether1, vlan100 out on ether2
Works with 4.17, stopped when upgrading to 5.0.
I had to return to 4.17 due to customer need, but i’ll make a support file to morrow.
I also had the missing wireless package on a few, it seems to be random, even if upgrading from normal wireless package.
But out of 100, maybe 2 or 3 did this. (When previously upgrading from 4.xx to 5.0rcxx)
Doubt if it is reproducable as it rarely, but sadly, happens sometimes from 4 to 5, regardless of wireless-nv2 or not.
Updated two rb433’s forming a remote link;
packages: advanced-tools, dhcp, routerboard, routing, system and wireless.
upgraded firmware.
So far so good. Link is running in 5Ghz 10Mhz channel Management protection enabled and 802.11 protocol with set data rates.
Switched link to run with nv2 protocol; so far so good. No probs.
Second unit is also AP, AP running in 2,4Ghz normal 802.11 + WPA PSK/WPA2PSK: No issue so far.
Link is just upgrade in the middle of the night and adjacent network don’t see effect of nv2.
Lets wait what the day will bring… fingers crossed..
Winbox still not more user friendly like requested several times by several users.
Is it not too late (more versions of 5.x to come ) to make winbox more userfriendly?
Why can’t we change window size and content (in wireless registration for instance) and format in such way it also comes back after a reboot in the same way?
Why can’t we open a window in winbox twice? Sometimes you want to put the windows registration column and the access list column side by side to see what is a discrepancy for instance. Now you have to swap between these or you have to open two sessions to the router.
I asked this before and it was promised to take it with develoment of new ROS family. This was in the days of early ros4rc’s…
) to make winbox more userfriendly?