MikroTik

RouterOS version 6.46.7 has been released in public "long-term" 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.7 (2020-Sep-07 07:38):

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.

Changes since 6.46.6:

*) arm - improved stability when forcing 25G speed on unsupported interface;
*) bridge - fixed host table update on SNMP query;
*) bridge - fixed STP alternate and backup port states for devices with switch chip;
*) crs3xx - fixed hardware offloaded MPLS forwarding when using bonding interfaces;
*) crs3xx - fixed QSFP+ interface LEDs when using break-out cable for CRS326-24S+2Q+;
*) crs3xx - fixed switch ACL rules for CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed switch port "egress-rate" removal for CRS305, CRS326-24G-2S+, CRS328, CRS318 devices;
*) crs3xx - improved 10G interface initialization on CRS312 devices;
*) crs3xx - improved Ethernet port group traffic forwarding on CRS354 devices;
*) crs3xx - improved system stability when using hardware offloaded MPLS;
*) defconf - fixed default configuration loading on RBmAPL-2nD;
*) dhcpv6-server - disallow changing binding's "prefix-pool";
*) dhcpv6-server - do not require "server" parameter for bindings;
*) discovery - do not send discovery packets on inactive bonding slave interfaces;
*) discovery - do not send discovery packets on interfaces that are blocked by STP;
*) dot1x - fixed duplicate EAP request packets for server;
*) dot1x - fixed EAP packet version numbering;
*) email - added support for multiple "to" recipients;
*) export - fixed HotSpot "address-per-mac" parameter export;
*) fetch - show status "uploaded" instead of "downloaded" when uploading a file;
*) ftp - fixed possible buffer overflow;
*) hotspot - ignore packets from host while MAC authentication is in progress;
*) ike1 - improved stability when performing policy lookup on non-existant peer;
*) ike2 - fixed local side NAT detection;
*) ike2 - fixed policy reference for pending acquire;
*) ike2 - retry RSA signature validation with deduced digest from certificate;
*) interface - added new builtin "static" interface list;
*) kidcontrol - fixed "time-unlimited-rate" to engage in correct time;
*) lcd - improved general system stability when LCD is not present;
*) lte - fixed modem initialization when multiple modems are used simultaneously;
*) lte - fixed PDP authentication configuration for SIM7600;
*) lte - improved stability during firmware upgrade;
*) metarouter - fixed image importing (introduced in v6.46);
*) ospf - fixed disappearing NSSA default route;
*) ospf - fixed processing of "unknown" LSA type;
*) ospf - improved route tag processing for OSPFv3;
*) poe - fixed "power-cycle" functionality on hEX PoE, PowerBox Pro and OmniTIK 5 PoE ac;
*) port - removed serial console port on hEX S;
*) ppp - removed "comment", "set" and "edit" commands from "PPP->Active" menu;
*) profile - added support for CCR2004-1G-12S+2XS;
*) qsfp - fixed auto-negotiation status;
*) quickset - fixed invalid configuration applying when performing changes during LTE modem initialization process;
*) quickset - show "Antenna Gain" setting on devices without built-in antennas;
*) route - improved stability when 6to4 interface is configured with disabled IPv6 package;
*) routerboard - fixed "reset-button" menu presence on all devices;
*) routerboot - fixed etherboot FCS errors with 100Mbps rate for CRS305, CRS309 and CRS317 devices ("/system routerboard upgrade" required);
*) sfp - stabilized CRS212 SFP port functionality and improved monitoring of optical modules;
*) smb - fixed file path validation (introduced in v6.46);
*) smb - fixed possible memory leak (CVE-2020-11881);
*) smb - limit active session count to 5 per connection;
*) sniffer - allow setting port for "streaming-server";
*) snmp - added "dot1qTpFdbTable" OID reporting for Q-BRIDGE-MIB;
*) switch - correctly enable and disable CPU Flow Control on RB3011UiAS;
*) switch - fixed MAC address learning on switch-cpu port for Atheros8316, Atheros8227 and Atheros7240 switch chips;
*) upgrade - fixed space handling in package file names;
*) w60g - added "mdmg-fix" parameter for RBwAP60Gx3 (CLI only);
*) w60g - improved rate selection in low traffic conditions;
*) webfig - fixed 5 GHz wireless interface "frequency" parameter value list on Audience;
*) winbox - added "region" parameter for W60G interfaces;
*) winbox - allow to specify any Ethernet like interface under "Tool/WoL" menu;
*) winbox - do not allow to enter empty strings in "caps-man-names" and "common-name" parameters;
*) winbox - fixed "Tx/Rx Signal Strength" value presence for 4 chain interfaces;
*) winbox - fixed wireless interface "HT" tab setting presence when "band=5ghz-n/ac";
*) winbox - fixed wireless sniffer parameter setting;
*) winbox - hide irrelevant switch port parameters;
*) wireless - added support for U-NII-2 for cAP ac;
*) wireless - added support for U-NII-2 for wAP ac;
*) wireless - allow setting "tx-power" up to 40;
*) wireless - changed "station-roaming" default setting from "enabled" to "disabled";
*) wireless - fixed potential wireless driver issue related to CVE-2020-3702;
*) wireless - improved management service stability when receiving bogus packets;
*) wireless - updated "bangladesh" regulatory domain information;
*) wireless - updated "canada" regulatory domain information;
*) wireless - updated "egypt" regulatory domain information;
*) wireless - updated "indonesia5" regulatory domain information;
*) wireless - updated "united states" regulatory domain information;
*) www - added "tls-version" parameter in "IP->Services" menu;

For a full changelog please visit https://mikrotik.com/download/changelogs

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 specific RouterOS release.

Hi

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

Also what is the process for 'upgrading' a routerboard that does not have direct internet access from stable to long-term release channel when it is on e.g. 6.47.x? I give it the .npk from long-term, and even set channel to long-term in packages but log says that newer version is installed - seems only way to change channel is with proper internet access?

Thanks

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

We already had discussion about that without results
viewtopic.php?f=21&t=150045&p=738887#p739011

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

Yes, that would be logical.

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

Yes, that would be logical.

Mikrotik fought the Logic and Mikrotik won.

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

Yes, that would be logical.

Mikrotik fought the Logic and Mikrotik won.

Flawless victory.

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

Yes, that would be logical.

Mikrotik fought the Logic and Mikrotik won.

Flawless victory.

Lost buyers of our Mikrotik products.

Wow, i thought MT had forgotten the 6.46 train.
For long time it as not been listed under "ANNOUNCEMENTS" section, so you had to search for it to find it.

Hi

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

Also what is the process for 'upgrading' a routerboard that does not have direct internet access from stable to long-term release channel when it is on e.g. 6.47.x? I give it the .npk from long-term, and even set channel to long-term in packages but log says that newer version is installed - seems only way to change channel is with proper internet access?

Thanks

Upload File go to System Packages and use Downgrade Option.

Also what is the process for 'upgrading' a routerboard that does not have direct internet access from stable to long-term release channel when it is on e.g. 6.47.x? I give it the .npk from long-term, and even set channel to long-term in packages but log says that newer version is installed - seems only way to change channel is with proper internet access?

The process is called "downgrade" ...

snmp-get still not working.

Shouldn't we be seeing the changelog from 6.45.9 to 6.46.7 not from 6.46.6 ? Going up a major version in a long-term release should be looked over a bit more carefully before we take the plunge.

Yes, that would be logical.

Mikrotik fought the Logic and Mikrotik won.

Man, they fight even hard evidence through supout files.

I have an un-resolved bug report with a properly generated supout file that clearly shows the bug along with the logs they asked for along with screenshot as proof plus the configuration they suggested me to use.

It's not that hard to understand why MikroTik doesn't have the market share or popularity that Cisco, Juniper etc does.

Yeah I was waiting for 6.45.10 ........... very confused LOL.

By the way what does this one mean.
*) interface - added new builtin "static" interface list;

Please stick to the topic. If you do not have anything meaningful to say about the specific version, keep it to yourself or post it in a separate topic.

By the way what does this one mean.
*) interface - added new builtin "static" interface list;

This is a very interesting changelog item, one that has never been in a stable (or development) release.

I find confusing that this comes to the long term release with barely no testing, has been first seen in testing in 6.48beta27, 2020-Aug-18 06:20 (announced here on 19th). Never been, let's say, properly released before going to long term.

By the way what does this one mean.
*) interface - added new builtin "static" interface list;

This is a very interesting changelog item, one that has never been in a stable (or development) release.

I find confusing that this comes to the long term release with barely no testing, has been first seen in testing in 6.48beta27, 2020-Aug-18 06:20 (announced here on 19th). Never been, let's say, properly released before going to long term.

It was added in 6.47.2, so all is fine.

I'd be careful with this one and Wireless Wire products. is a 6.47 change and 6.47 has been terrible for 60g reliability

Updated 5G gear, so far no issues. Not upgrading any 60G radios until it's confirmed to be safe and working without any issues. Currently don't have any spare hardware to do the testing either...

*) upgrade - fixed space handling in package file names;

system auto-upgrade still broken.

thx

Upgraded my home hAP ac^2 and I had a problem that I saw for the first time. It seems like router only preserved 200-something address list entries, and many were gone completely or only partially preserved, breaking access to the router itself and internet access (because I use those as NAT out address lists). Had to manually restore them from backups.

Upgraded my home hAP ac^2 and I had a problem that I saw for the first time. It seems like router only preserved 200-something address list entries, and many were gone completely or only partially preserved, breaking access to the router itself and internet access (because I use those as NAT out address lists). Had to manually restore them from backups.

How many entries did you have in the list. I had a similar problem but mine always came after restart. My entries where static but the disk on the unit was full and I could add more via script but after a restart I lost them. Never managed to solve this so now I have a startup script that populates everything have have gone for dynamic entries instead.

You seem to be correct, although it doesn't completely explain why only ~200 entries remained out of 50k (all are/were static). I have many small address lists and a huge one with over 50k entries. There is only 2.1MB free space on hAP ac^2 nand chip, and these are the sizes of a couple of latest backup files:
I will just remove the big acl, since I do not want to test if it will wipe the configuration after restart (router was not restarted in months until today update).

Can I downgrade to this from 6.47 without losing the config?

Can I downgrade to this from 6.47 without losing the config?

Yes, make a backup to feel more comfortable anyways

Can I downgrade to this from 6.47 without losing the config?

Yes, make a backup to feel more comfortable anyways

The problem is not the backups (they are done automatically every day), but that these devices are in a remote location, so I can't access them physically.

There's an bug with LTE on startup on CCR1016. Static ipv4 address(es) are loosing their interface setting in IP addresses and coming up 'unknown'.

This causes routes to break to the LTE modem as there is no address on the lte1 interface without correcting the unknown and putting back lte1.

Happened twice. Once on upgrade to 6.46.7 and again to reboot to update the bootloader so its completely reproducible. Means backup LTE is pretty useless without access to IP addresses.

Ticket SUP-27850

I have a problem discovering devices. In a small network, the main router ccr 1016, discovery interface is bridge1,
it is also configured as OVPN server, type Ethernet, OVPN profile - bridge1. There is a remote OVPN client - rb951,
its discovery interface is also bridge1. So, in ip neighbors, 1016 sees the entire network except rb951,
and rb951 also sees in ip neighbors the entire network, except for 1016.
in 6.45.9 there was no such problem

Yesterday I caught a joint at 6.46.7 !!!
Ping breaks from the dhcp server to the client, and from the dhcp client to the dhcp server, ping is lossless. At the same time, when connecting to an access point, the Internet is there for a couple of minutes and then it will be irretrievably lost !!!
Returned 6.45.9 again everything worked in normal mode.
Equipment:
Hap ac lite - dhcp server.
CAP ac - dhcp client.

Had to roll-back to 6.45.9 on my Rb4011. Have had issues which only we're solvable by rebooting the router. Couldn't make supout.rif file either before reboot. The last problem was all non local routes were gone, couldn't see them in winbox or terminal. Actually the route list was totally empty but locally connected routes worked. No OSPF or BGP connected routes worked. Before that I've had one random reboot of the router. Before the upgrade it was totally stable and been running for like 100 days uptime or so.I'll let the rest of the equipment run on 6.46.7 (hAP, cAP, cAP AC, wAP ac, CRS309, CRS317) since they seem to work fine. So I'll stick with 6.45.9 on the RB4011 for a while now. Anyone else seen any strange behavour with this version?

I upgraded a new 328-24P-4S+ to this release. When setting a bridge VLAN in Winbox the new window shows a VLAN ID of 4294967295 and 'VLAN IDs' is red (since number is invalid). I change it to the VLAN ID I want and it seems to be fine. It shows this each time I add a new VLAN.

I confirmed this happens on a second 328, and on a 326. Both upgraded from previous long-term 6.45.9.

It looks like this VLAN entry thing is happening on other devices as well - even when configured from scratch. Configuration seems to work OK when it is done.

I upgraded a new 328-24P-4S+ to this release. When setting a bridge VLAN in Winbox the new window shows a VLAN ID of 4294967295 and 'VLAN IDs' is red (since number is invalid). I change it to the VLAN ID I want and it seems to be fine. It shows this each time I add a new VLAN.

I confirmed this happens on a second 328, and on a 326. Both upgraded from previous long-term 6.45.9.

This sounds very scary. Have you contacted support as you seam to be able to replicate the issue?

Seems like i will stuck at 6.45.9, because this one have some issues. Wait for another "stable" long term build.

Hi,
This is my post in winbox release thread: posting.php?mode=edit&f=21&p=816318
Straight about "red vlan error"

I'd be careful with this one and Wireless Wire products.

Code: Select all

*) w60g - improved rate selection in low traffic conditions;

is a 6.47 change and 6.47 has been terrible for 60g reliability

Yes, I had to downgrade to 6.46.6, w60g links were very unstable with 6.46.7, especially Wireless Wire, but some LHG links too.

I'd be careful with this one and Wireless Wire products.

Code: Select all

*) w60g - improved rate selection in low traffic conditions;

is a 6.47 change and 6.47 has been terrible for 60g reliability

I can confirm this issue. Upgraded some of our LHG60's to 6.46.7 and we've had multiple disconnects since. Downgraded them to 6.45.9 again and they are rock solid.

I'd be careful with this one and Wireless Wire products.

Code: Select all

*) w60g - improved rate selection in low traffic conditions;

is a 6.47 change and 6.47 has been terrible for 60g reliability

I can confirm this. I had to revert my Wireless Wire units back to 6.46.6

in DHCP-client scripts don't work

In our CCR1036 devices, DHCP does not always populate the ARP table. ARP table entries are critical in our setup.
Or the ARP table entries are disappearing despite the longer timeout setting on the DHCP bridge.

Actually, thinking more and more that the ARP entries get added to the ARP List but later disappear for some reason. Despite the long timeout setting on the Bridge.

in CRS305-1G-4S+ (ARM) v6.46.7
SFP+DAC of any brand not work in 10G mode

UPDATE:
not work between Huawei MA5608T into 10GE port and CRS305-1G-4S+, with mikrotik dac, Ubiquiti Dac, works only with some models of optical sfp+ transceiver
(I deduce that it may be some driver missing from his ARM platform)
works well in anothers CRSxx models witdh dacs and sfp+

please help
what this
evry show the router board stop need reboot to work

And my modem i see mac address of my router board but ip difference
My rouer board ip = 192.168.1.10 and real mac
But in my modem I see it in dhcp field but ip = 192.168.1.4 or 192.168.1.8 or address
Another for the same Mac for the router board
This way below

Then my router shuts down and I have to restart it again and it is only hours or sometimes minutes and it stops again and I don't know what is causing the problem, is it a hack or what

Please help me

This thing caused me big problems,
Please take care because I am losing a lot of time and work.
please help and Thanks in advance

And my modem i see mac address of my router board but ip difference

Create a dedicated topic in General. This topic is reserved for issues specifically related to 6.46.7.

This release is BROKEN.

Upon upgrade from previous long term on several 750Gr3:
[*]Bridge config almost always borked after upgrade:
[*][*]certain ports get randomly disabled from the bridge config
[*][*]certain bridges and their ports show "unknown/unknown" and are obviously broken - in config it shows add interface=*1F add interface=*1E


[*]DHCP client is broken
[*]randomly the dhcp client does not accept responses with default options (the dhcp client from default config)
[*][*]custom DHCP client does not accept responses at all if more than one option 50 is specified. The dhcp server returns one of the addresses requested ( I can see the OFFER in the debug log), yet the response is not used by the router (no ACK) and continues sending requests.

all of these worked without problems in previous long term release.

New version 6.46.8 has been released in long-term RouterOS channel:

viewtopic.php?f=21&t=168411