v6.46.5 [stable] is released!

Announcements
1

RouterOS version 6.46.5 has been released in public "stable" channel!

Before an upgrade:

  1. Remember to make backup/export files before an upgrade and save them on another storage device;
  2. Make sure the device will not lose power during upgrade process;
  3. Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.46.5 (2020-Apr-07 08:28):

Important note!!!

  • The Dude server must be updated to monitor v6.46.4+ and v6.47beta30+ RouterOS type devices.
  • The Dude client must be manually upgraded after upgrading The Dude server.
  • The Dude requires "winbox" policy instead of "dude" to monitor v6.46.4+ and v6.47beta30+ RouterOS type devices.

**MAJOR CHANGES IN v6.46.5:

!) user - enable "winbox" policy for groups with "dude" policy;
----------------------**

Changes in this release:

*) capsman - fixed "certificate" parameter updating on CAP;
*) console - prevent incorrect type interfaces appearing in command hints;
*) crs3xx - fixed interface statistics for CRS354-48G-4S+2Q+ and CRS354-48P-4S+2Q+ devices;
*) crs3xx - fixed traffic forwarding after disabling/enabling bridge hardware offloading for CRS354-48G-4S+2Q+ and CRS354-48P-4S+2Q+ devices;
*) crs3xx - improved SFP+ DAC cable initialization for CRS326-24S+2Q+ device;
*) discovery - do not send CDP and LLDP packets on interfaces that does not have MAC address;
*) dude - fixed connection to other RouterOS type devices through The Dude agents (introduced in v6.46.4);
*) ike1 - rekey phase 1 rekeying as responder for Windows initiators;
*) ipsec - improved system stability when handling fragmented packets;
*) led - added "dark-mode" functionality for CRS105-5S-FB;
*) lora - added IPv6 support for LoRa packet forwarder;
*) lora - added UTC timestamp for RX events in "rxpk" json;
*) lora - added value limits for "freq-off" parameter;
*) lora - properly update source address for packets when routing table is changed;
*) lte - fixed IP type selection from APN on RBSXTLTE3-7;
*) sniffer - fixed minor typo in "host" menu;
*) supout - added "gps" section to supout files;
*) supout - improved PoE-out information reporting;
*) system - improved kernel panic reporting in logs after reboot;
*) system - improved system stability when forwarding traffic from switch chip to CPU (introduced in v6.43);
*) traceroute - improved stability when invalid packet is received;
*) traffic-generator - improved statistics reporting;
*) w60g - improved stability after multiple disconnections;
*) winbox - added "Options" parameter support for DHCPv6 client and server;
*) winbox - added 160Mhz extension channel support for CAPsMAN;
*) winbox - added support for "Tools->WoL" menu;
*) winbox - allow setting "20/40/80/160Mhz-eeeeeeCe" channel under "Channel Width" parameter;
*) winbox - do not show "Revision" parameter under "System/RouterBOARD" menu on devices that have only one revision;
*) winbox - fixed "ARP" parameter inheritance from "CAPs Configuration" configuration;
*) winbox - fixed "Bands" parameter display for LTE interfaces;
*) winbox - fixed "DSCP" parameter value setting;
*) winbox - fixed "Frequency" and "Secondary Frequency" parameter inheritance from "CAPs Channel" configuration;
*) winbox - fixed "Passthr. MAC Address" parameter display "LTE APNs" menu;
*) winbox - fixed "Switch" menu on CRS354-48P-4S+2Q+;
*) winbox - fixed "dst-port" unsetting in "IP->Hotspot->Walled Garden" menu;
*) winbox - fixed automatic "IPv6->Firewall->Address List" table update;
*) winbox - made "none" the default value for "Security Profile" parameter when creating a new "Wirelees->Connect list" entry;
*) winbox - properly show "Hw. Offload Group" value for each interface under "Bridge->Ports" menu;
*) winbox - renamed "Memory used" to "HDD used" for HDD type under "Tools->Graphing->Resource Graphs";
*) winbox - show "System/RouterBOARD/Mode Button" on devices that have such feature;
*) wireless - added "U-NII-2" support for hAP ac2 and RBwAPGR series devices;
*) wireless - added "skip-dfs-channels" parameter;
*) wireless - fixed default "antenna-gain" setting on SXT 2 and LtAP series devices;
*) wireless - updated "bangladesh" regulatory domain information;
*) wireless - updated "indonesia4" regulatory domain information;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this particular RouterOS release.

v6.46.4 [stable] is released!
2

What devices are supported? *) winbox - allow setting “20/40/80/160Mhz-eeeeeeCe” channel under “Channel Width” parameter;

3

I would hope the 4011…I currently use 80 which is fine, but was hoping to push it a little more

4

I can’t choose the “bridge” interface for WoL.
I have scripts like:

/tool wol XX:XX:XX:XX:XX:XX interface=bridge-LAN

and it works perfectly.
WoL menu is not so useful if it does not appear in the menu obtained with the right key, for example, in DHCP Leases menu page.

5

winbox - added support for “Tools->WoL” menu;
WoL doesn’t work via winbox and Webfig, but it works via command line only.
When you press “Wake on LAN” button, the window just closes.

6

On hap ac2 and hap ac lite this is not

7

Where can I find this? I know there already is this option for CAPsMAN, I was hoping to find it in the regular Wireless interfaces too.

*) wireless - added “skip-dfs-channels” parameter;

8

wireless - added “U-NII-2” support for hAP ac2
ok, but where did U-NII-3 missing??

9

Hi,
Does anybody check OSPF stability? Previous releases has many strange bugs…

10

Upgraded my CloudCore, CCR10009-7g-1c-1s+ and it has been everything but stable. Keep loosing WAN and Lan interface connection, so does not matter if I’m inside lan or outside, still lost connection. After a few min, or seconds in best case, it comes online again. Pingdom reported it as network error. 12h later i reverted to previous version and now things are stable again.

11

I also updated my CCR1009 to 6.46.5 yesterday. So far I’m not seeing anything you describe, connections are stable, not a single disconnect, all ports are in use (sfp+ and ethernet).
Don’t know if it’s required but did you upgrade RouterBOOT, too?

12

You can set this parameter in the command line. I haven’t found it in Winbox.

[user@hAPac2] > /interface wireless set wlan2 skip-dfs-channels=
10min-cac  all  disabled
13

System->auto-upgrade, still problem, can not display available routeros from ftp source !!
Please fix it, it broken after 6.45.7

thx

14

Thank you!

15

Not sure when it happened, but trying to do a PING from tools within the routerboard, or traceroute which uses PING to ANY host, I get 100 % loss, but the DNS lookup is works… the rule I traced this too was the one below:
chain=input action=drop protocol=icmp dst-address=xx.xx.xx.xx in-interface=EoIP-WAN log=no log-prefix=“”
Disabling this would allow the pings to work.

So my question is, why in the past with this rule, did the ping and tracerts work, and then after this upgrade the ping response from the other hosts gets dropped by this rule? After all the rule is set for INPUT chain.

Or did I not see this function for a decade like it did before, and all of the sudden changed?
Note this is the first rule I have to drop ICMP on the wan interface.
If I add the Connection state NEW to this rule, it will allow ROS ping and tracerts to have responses from the hosts, but Inbound ping on WAN is dropped. This behavior was not like this before.

16

Upgraded one of my rb4011 6.46.4 to 6.46.5 using winbox 3.22 on my win10 - even though misaligned and missing text is a minor issue it still triggers my ocd.
winbox3.22-ros6.46.5.minorissue.png

17

U-NII-2
what does that mean?

18

Hi,
Does anybody have any info on OSPFv2 and v3 stability?
Any IPsec issues?
Please, respond…

19

BobcatGuy, the effect of the firewall rules depends on their position in their respective chains. So if there was an “accept established,related” rule before the one which has upset you, and you have (possibly accidentally) removed or disabled it, or simply moved it past the “drop icmp” one, it might explain why now the “drop icmp” rule acts also on outgoing ICMP traffic. Feel free to create a new topic and post your complete /ip firewall export there, and edit your previous post with a link to that new topic.

20

I believe the fix is to drag open the window more to the right and its fixed!!! I just noticed that now. I did the upgrade of the packages but forgot to do the routerboard. Thanks for reminding me