MikroTik

Posted: **Tue Dec 03, 2019 11:59 am**

RouterOS version 6.46 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 (2019-Dec-02 11:16):

MAJOR CHANGES IN v6.46:
----------------------
!) lora - added support for LoRaWAN low-power wide-area network technology for MIPSBE, MMIPS and ARM;
!) package - accept only packages with original filenames (CVE-2019-3976);
!) package - improved package signature verification (CVE-2019-3977);
!) security - fixed improper handling of DNS responses (CVE-2019-3978, CVE-2019-3979);
----------------------

Changes in this release:

*) backup - fixed automatic backup file generation when configuration reset by button;
*) backup - store automatically created backup file in "flash" directory;
*) bonding - correctly remove HW offloaded bonding with ARP monitoring;
*) bonding - properly handle MAC addresses when bonding WLAN interfaces;
*) bridge - disable/enable bridge port when setting bpdu-guard;
*) bridge - do not add bridge as untagged VLAN member when frame-types=admit-only-vlan-tagged;
*) bridge - do not add dynamically VLAN entry when changing "pvid" property for non-vlan aware bridge;
*) bridge - include whole VLAN-id in DHCP Option 82 message;
*) btest - removed duplicate "duration" parameter;
*) capsman - fixed background scan showing incorrect regulatory domain mismatch error (CAP upgrade required);
*) capsman - fixed channel auto reselection;
*) capsman - fixed MAC address detection for "common-name" parameter in certificate requests;
*) capsman - improved DFS channel switching when radar detected;
*) capsman - improved radar detection algorithm;
*) ccr - improved general system stability;
*) certificate - added progress bar when creating certificate request;
*) certificate - added support for certificate request signing with EC keys;
*) certificate - allow specifying "file-name" parameter for export (CLI only);
*) certificate - allow specifying "name" parameter for import (CLI only);
*) certificate - improved CRL updating process;
*) certificate - removed "key-size" parameter for "create-certificate-request" command;
*) chr - added support for Azure guest agent;
*) console - added bitwise operator support for "ip6" data type;
*) console - fixed "address" column width when printing DHCPv4 leases;
*) console - fixed IP conversion to "num" data type;
*) console - fixed "tobool" conversion;
*) console - properly detect IPv6 address as "ip6" data type;
*) crs1xx/2xx - allow to set trunk port as mirroring target;
*) crs3xx - correctly handle L2MTU change;
*) crs3xx - do not send pause frames when ethernet "tx-flow-control" is disabled on CRS326/CRS328/CRS305 devices;
*) crs3xx - improved interface initialization;
*) crs3xx - improved switch-chip resource allocation on CRS317-1G-16S+, CRS309-1G-8S+, CRS312-4C+8XG, CRS326-24S+2Q+ devices;
*) crs3xx - improved system stability on CRS309-1G-8S+, CRS312-4C+8XG, CRS326-24S+2Q+ devices;
*) crs3xx - remove previously set mirror-source property before changing it;
*) defconf - fixed default configuration loading on RBmAPL-2nD (introduced in v6.45);
*) defconf - require "policy" permission to print default configuration;
*) dhcpv4-client - allow empty "dhcp-options" parameter when adding new client;
*) dhcpv4-client - fixed "dhcp-options" parameter setting when adding new client;
*) dhcpv4-server - improved stability when RADIUS Interim update is sent;
*) dhcpv6-client - fixed timeout when doing rebind;
*) dhcpv6-client - properly update bind time when unused prefix received from the server;
*) dhcpv6-client - properly update IPv6 address on rebind;
*) dhcpv6-server - fixed logged error message when using "address-pool=static-only";
*) dhcpv6-server - ignore prefix-hint from client's DHCPDISCOVER if static prefix received from RADIUS;
*) dhcpv6-server - include "User-Name" parameter in accounting requests;
*) dhcpv6-server - made "calling-station-id" contain MAC address if DUID contains it;
*) dot1x - added "reject-vlan-id" server parameter (CLI only);
*) dot1x - added support for dynamic switch rules from RADIUS;
*) dot1x - added support for "mac-auth" authentication type (CLI only);
*) ethernet - automatically detect interface when using IP address for power-cycle-ping;
*) ethernet - do not enable interface after reboot that is already disabled;
*) ethernet - send requests only from ethernet interface when using MAC address for power-cycle-ping;
*) export - always export "ssid" value for w60g interfaces;
*) fetch - do not allocate extra 500KiB on SMIPS;
*) fetch - improved stability when processing large output data;
*) gps - use "serial1" as default port on RBLtAP-2HnD;
*) hotspot - fixed non-local NAT redirection to port TCP/64873;
*) hotspot - fixed RADIUS CoA "address-list" update;
*) ike1 - fixed minor spelling mistake in logs;
*) ike2 - improved CHILD SA rekey process with Apple iOS 13;
*) ike2 - improved stability when retransmitting first packet as responder;
*) ipsec - added "error" topic for identity check failure logging messages;
*) ipsec - fixed DNS resolving when domain has only AAAA entries;
*) ipsec - fixed policy "sa-src-address" detection from "local-address" (introduced in v6.45);
*) ipv6 - changed "advertise-dns" default value to "yes";
*) led - fixed default LED configuration for RBLHG-2nD and RBLHG-5HPnD;
*) log - increased log message length limit to 1024 characters;
*) lte - added support for D402 modem;
*) lte - added support for LM960A18;
*) lte - added support for Telit LM960 and LE910C1 modems;
*) lte - do not allow setting 3G and GSM modes on LTE only modems;
*) lte - fixed band setting on R11e-4G;
*) lte - fixed network registration on R11e-LTE-US;
*) lte - fixed Sierra WP7601 driver loading;
*) lte - fix "operator" names not being displayed properly;
*) lte - improved modem initialization;
*) lte - show "primary-band" only for LTE modems;
*) lte - use /128 prefix for IPv6 address on LTE interface;
*) lte - use interface from RA when "ipv6-interface=none" and IPv6 enabled;
*) ppp - added 3GPP IoT "access-technology" definitions;
*) ppp - added support for Sierra WP7601;
*) ppp - disable DTR send when using at-chat;
*) quickset - added "LTE AP Dual" mode support;
*) quickset - added "LTE APN" dropdown support;
*) quickset - fixed "LTE Band" checkbox display;
*) route - fixed area range summary route installation in VRF;
*) routerboard - fixed default CPU frequency on RB750r2 ("/system routerboard upgrade" required);
*) routerboard - fixed USB configuration export on RBLtAP-2HnD;
*) routerboard - hide "memory-frequency" parameter for RBLtAP-2HnD;
*) sniffer - allow filtering by packet size;
*) snmp - added "disabled" and "comment" parameters for communities;
*) snmp - added option to monitor "link-downs" parameter using MIKROTIK-MIB;
*) snmp - fixed "dot1dBasePort" index offset for BRIDGE-MIB;
*) snmp - fixed "ifLastChange" OID reporting for IF-MIB;
*) snmp - fixed "radio-name" (mtxrWlRtabRadioName) OID support;
*) snmp - improved interface status reporting for IfOperStatus OID;
*) snmp - improved LLDP interface returned index and type;
*) snmp - return only interfaces with MAC addresses for LLDP;
*) snmp - use "src-address" also for traps;
*) ssh - fixed output printing when "command" parameter used;
*) supout - include information from all LTE interfaces;
*) supout - removed "file" option from "/system sup-output" command;
*) switch - added "comment" property for switch vlan menu (CLI only);
*) switch - correctly update dynamic switch rule when dhcp-snooping is enabled;
*) switch - ignore "default-vlan-id" property after switch reset on RTL8367 switch chip;
*) switch - show "external" flag for bridge hosts on MT7621, RTL8367 switch chips;
*) timezone - updated time zone database to version 2019c;
*) tr069-client - added CellDiagnostics parameter support;
*) tr069-client - added LTE band and cellular technology selection parameters;
*) tr069-client - added LTE RSCP, ECNO and ICCID parameter support;
*) tr069-client - added multiple LTE monitoring parameters;
*) tr069-client - reconnect to ACS when "ConnectionRequestURL" is updated;
*) upgrade - improved auto package updating using "check-for-updates";
*) ups - improved compatibility with APC UPS's;
*) usb - general USB modem stability improvements;
*) userman - updated Authorize.Net to use SHA512 hashing;
*) w60g - added "region" setting to limit allowed frequencies (CLI only);
*) w60g - do not reset link when changing comment on station;
*) w60g - fixed "monitor" command on disabled interfaces;
*) w60g - move stations to new bridge when "put-in-bridge" parameter is changed;
*) webfig - fixed link to Winbox download;
*) winbox - added "ip-address" and stats columns in "IP/Kid-Control/Devices" menu;
*) winbox - added "public-address-ipv6" parameter to "IP/Cloud" menu;
*) winbox - added "reset-counters" button to "IP/Kid Control/Devices" menu;
*) winbox - added "tx-info-field" parameter to "Wireless/W60G" menu;
*) winbox - added "Vendor Classes" tab in "IP/DHCP Server" menu;
*) winbox - added wireless alignment LED types to "System/LEDs" menu;
*) winbox - fixed allowed range for bridge filter "new-priority" parameter;
*) winbox - fixed "CAPs Scanner" stopping;
*) winbox - fixed "cluster-id" parameter setting in "Routing/BGP/Instances" menu;
*) winbox - fixed file locking when uploading multiple files at once;
*) winbox - fixed firewall limit parameter support for rates more than 4G;
*) winbox - fixed invalid flag presence in "IP/SMB/Shares" menu;
*) winbox - fixed "Routing" menu icon presence when there is no routing package installed;
*) winbox - improved stability when transfering multiple files between multiple windows;
*) winbox - properly show timestamp in file "Creation Time" field;
*) winbox - removed "Set CA Passphrase" button from "Certificate" menu;
*) winbox - renamed "Queue Limit" to "Queue Size" for "pcq-upload-default" and "pcq-download-default" parameters;
*) winbox - replaced "kb" with "KiB" in "Tools/Packet Sniffer" menu;
*) winbox - show "Switch" menu on RBwAPGR-5HacD2HnD;
*) winbox - show "System/RouterBOARD/Mode Button" on devices that have such feature;
*) wireless - added 4 chain MCS support for 802.11n wireless protocol (CLI only);
*) wireless - added "ETSI" regulatory domain information;
*) wireless - added "indonesia4" regulatory domain information;
*) wireless - added "push-button-5s" value for "wps-mode" parameter;
*) wireless - added U-NII-2 support forRBSXTsqG-5acD, RBLHGG-5acD-XL, RBLHGG-5acD, RBLDFG-5acD, RBDiscG-5acD;
*) wireless - allow using "canada2" regulatory domain on US lock devices;
*) wireless - fixed 802.11n rate selection when managed by CAPsMAN;
*) wireless - fixed RX chain selection;
*) wireless - fixed sensor MAC address reporting in TZSP header;
*) wireless - improved 802.11ac stability for all ARM devices with wireless;
*) wireless - improved IPQ4019, QCA9984, QCA9888 wireless interface stability;
*) wireless - updated "ukraine" regulatory domain information;
*) wireless - updated "united-states" 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.

Posted: **Tue Dec 03, 2019 12:18 pm**

CRS226-24G-2S+ and 750GL upgraded to v6.46 without problems, but since they are not in production this only prove that upgrade works work
those two devices.

Posted: **Tue Dec 03, 2019 12:57 pm**

The upgrade of my CRS305-1G-4S+IN and RB4011iGS+5HacQ2HnD-IN went fine. Updating my CCR1036-8G-2S+ seems to have broken the L2TP/IPSec server; the router is back, but I can no longer connect to it with the Android VPN client; it just times out. Will look at it when I'm home this evening...

Posted: **Tue Dec 03, 2019 2:25 pm**

Updating:
6 of CRS326
10 of hAP Lite
10 of RB951Ui
20 of RB2011UiAS
5 of 1100
without any problem.

Posted: **Tue Dec 03, 2019 3:08 pm**

I'm guessing that

*) ike1 - fixed minor spelling mistake in logs;

isn't regarding this: viewtopic.php?f=21&t=154286#p763108 since it's the same in this release.
My logs are from ike2 anyway.

Posted: **Tue Dec 03, 2019 3:52 pm**

X86 reports "broken package lora-6.46.npk" and reverts back to 6.45.7 when trying to update.

Posted: **Tue Dec 03, 2019 3:57 pm**

rmozer Lora package for x86 was never publicly released. How did you obtain it for 6.45.7? Is it installed on your system when looking at System Packages menu?

Znevna No those typo's are not fixed in this release.

mbovenka Please keep us updated on what you find. You can also generate a supout.rif file before attempting to fix an issue and send it to us.

Posted: **Tue Dec 03, 2019 4:05 pm**

mbovenka Please keep us updated on what you find. You can also generate a supout.rif file before attempting to fix an issue and send it to us.

Seems to have been a false alarm; it suddenly started working, and the logging didn't show any attempts at all before that. Maybe an ISP issue... I'll keep an eye on it.

Posted: **Tue Dec 03, 2019 5:03 pm**

Yep, not sure how it was installed on the X86 but once removed, it took 6.46 with no issues. Thanks!

Posted: **Tue Dec 03, 2019 5:52 pm**

*) wireless - added 4 chain MCS support for 802.11n wireless protocol (CLI only)

Any example ? I cant find this option in cli

Posted: **Tue Dec 03, 2019 6:00 pm**

Posted: **Tue Dec 03, 2019 6:11 pm**

Background Images in the Dude won't load.
And what happened to the font, the "1" at the end isn't readable.

Posted: **Tue Dec 03, 2019 7:15 pm**

*) winbox - added "public-address-ipv6" parameter to "IP/Cloud" menu;

This .. doesn't appear in WinBox nor in WebFig. Only present in terminal.

Posted: **Tue Dec 03, 2019 8:06 pm**

We updated a few CCRs from V6.45.7 to V6.46.
The Route Status SNMP sensors stopped working in our monitoring system (IP-FORWARD-MIB) with "object not found". If we downgrade to V6.45.7 the sensors work again.

This is a V6.46 related bug.

Posted: **Tue Dec 03, 2019 8:56 pm**

Everything fine except I get "Limited Access" now on Internet Detect feature without any config change. Maybe MikroTik has to change something server side ...

Posted: **Tue Dec 03, 2019 9:58 pm**

ccr - improved general system stability;

Any specifics about this?

Posted: **Tue Dec 03, 2019 10:01 pm**

Background Images in the Dude won't load.
And what happened to the font, the "1" at the end isn't readable.

CONFIRM

Images in the Dude won't load.

/dude/files/default
Permission denied

Don't update DUDE !!!

Posted: **Tue Dec 03, 2019 10:04 pm**

Background Images in the Dude won't load.
And what happened to the font, the "1" at the end isn't readable.

Same issue here, is there any fix for the problem or we shall wait for an official fix?

Posted: **Wed Dec 04, 2019 12:08 am**

I can confirm a BUG relatet to the SNMP IP-FORWARD-MIB:

SNMP-Output with V6.45.7

03.12.2019 23:04:54 (5562 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=2 #
03.12.2019 23:04:54 (5668 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0.0.0.0 #
03.12.2019 23:04:54 (5774 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.10.10.0.0.255.255.252.0.0.10.10.0.70: value=10.10.0.0 #
03.12.2019 23:04:54 (5881 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0.0.0.0 #
03.12.2019 23:04:54 (6112 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.10.10.0.0.255.255.252.0.0.10.10.0.70: value=255.255.252.0 #
03.12.2019 23:04:55 (6217 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
03.12.2019 23:04:55 (6322 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:55 (6552 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.0.0.0.0.0.0.0.0.0.10.10.0.1: value=10.10.0.1 #
03.12.2019 23:04:55 (6656 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.10.10.0.0.255.255.252.0.0.10.10.0.70: value=10.10.0.70 #
03.12.2019 23:04:55 (6851 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.0.0.0.0.0.0.0.0.0.10.10.0.1: value=11 #
03.12.2019 23:04:55 (7091 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.10.10.0.0.255.255.252.0.0.10.10.0.70: value=11 #
03.12.2019 23:04:55 (7196 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4 #
03.12.2019 23:04:56 (7301 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.10.10.0.0.255.255.252.0.0.10.10.0.70: value=3 #
03.12.2019 23:04:56 (7532 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.0.0.0.0.0.0.0.0.0.10.10.0.1: value=3 #
03.12.2019 23:04:56 (7637 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.10.10.0.0.255.255.252.0.0.10.10.0.70: value=2 #
03.12.2019 23:04:56 (7741 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
03.12.2019 23:04:56 (7845 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:56 (8071 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
03.12.2019 23:04:56 (8173 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:57 (8277 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.0.0.0.0.0.0.0.0.0.10.10.0.1: value=1 #
03.12.2019 23:04:57 (8419 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:57 (8621 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:57 (8770 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:57 (8972 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:57 (9170 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:58 (9274 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:58 (9417 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:58 (9621 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:58 (9725 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:58 (9829 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.0.0.0.0.0.0.0.0.0.10.10.0.1: value=1 #
03.12.2019 23:04:58 (10070 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.10.10.0.0.255.255.252.0.0.10.10.0.70: value=1 #

And here with V6.46 (a catastrophic outcome!!!!):

03.12.2019 23:00:42 (12293 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=2 #
03.12.2019 23:00:42 (12401 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:42 (12594 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:42 (12794 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:42 (13032 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13180 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13383 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13490 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13595 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13833 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14070 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14216 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14418 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14525 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14630 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14775 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (15053 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15158 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15303 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15547 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15794 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16083 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16189 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16294 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16523 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16624 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16724 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16825 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:47 (17063 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:47 (17162 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:47 (17262 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #

Please Mikrotik fix this as soon as possible! This is massive bug and should never happen in a stable version!!!!!!!!

Posted: **Wed Dec 04, 2019 2:36 am**

what's a differences between
"push-button-5s and "push-button"??

Posted: **Wed Dec 04, 2019 8:41 am**

The cpu temperature (.1.3.6.1.4.1.14988.1.1.3.11.0) for CRS326-24G-2S+ stopped working with "object not found".

Posted: **Wed Dec 04, 2019 10:12 am**

Updated 3xHap AC 6.45.7 -> 6.46 - so far without issues
Updated 3xHap AC Lite 6.45.7 -> 6.46 - no issues

Thanks!

Posted: **Wed Dec 04, 2019 10:44 am**

Please, contact MikroTik support with attached support output file and example of failing SNMP.

It seems to work for me,
snmpwalk -v1 -c public2 10.155.0.99 1.3.6.1.2.1.4.24.4.1.2.10
IP-MIB::ip.24.4.1.2.10.155.0.0.255.255.255.0.0.10.155.0.99 = IpAddress: 255.255.255.0
IP-MIB::ip.24.4.1.2.10.155.99.0.255.255.255.0.0.10.155.99.1 = IpAddress: 255.255.255.0

I can confirm a BUG relatet to the SNMP IP-FORWARD-MIB:

SNMP-Output with V6.45.7

03.12.2019 23:04:54 (5562 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=2 #
03.12.2019 23:04:54 (5668 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0.0.0.0 #
03.12.2019 23:04:54 (5774 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.10.10.0.0.255.255.252.0.0.10.10.0.70: value=10.10.0.0 #
03.12.2019 23:04:54 (5881 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0.0.0.0 #
03.12.2019 23:04:54 (6112 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.10.10.0.0.255.255.252.0.0.10.10.0.70: value=255.255.252.0 #
03.12.2019 23:04:55 (6217 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
03.12.2019 23:04:55 (6322 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:55 (6552 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.0.0.0.0.0.0.0.0.0.10.10.0.1: value=10.10.0.1 #
03.12.2019 23:04:55 (6656 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.10.10.0.0.255.255.252.0.0.10.10.0.70: value=10.10.0.70 #
03.12.2019 23:04:55 (6851 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.0.0.0.0.0.0.0.0.0.10.10.0.1: value=11 #
03.12.2019 23:04:55 (7091 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.10.10.0.0.255.255.252.0.0.10.10.0.70: value=11 #
03.12.2019 23:04:55 (7196 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4 #
03.12.2019 23:04:56 (7301 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.10.10.0.0.255.255.252.0.0.10.10.0.70: value=3 #
03.12.2019 23:04:56 (7532 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.0.0.0.0.0.0.0.0.0.10.10.0.1: value=3 #
03.12.2019 23:04:56 (7637 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.10.10.0.0.255.255.252.0.0.10.10.0.70: value=2 #
03.12.2019 23:04:56 (7741 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
03.12.2019 23:04:56 (7845 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:56 (8071 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.0.0.0.0.0.0.0.0.0.10.10.0.1: value=0 #
03.12.2019 23:04:56 (8173 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:57 (8277 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.0.0.0.0.0.0.0.0.0.10.10.0.1: value=1 #
03.12.2019 23:04:57 (8419 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.10.10.0.0.255.255.252.0.0.10.10.0.70: value=0 #
03.12.2019 23:04:57 (8621 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:57 (8770 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:57 (8972 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:57 (9170 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:58 (9274 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:58 (9417 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:58 (9621 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.0.0.0.0.0.0.0.0.0.10.10.0.1: value=4294967295 #
03.12.2019 23:04:58 (9725 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.10.10.0.0.255.255.252.0.0.10.10.0.70: value=4294967295 #
03.12.2019 23:04:58 (9829 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.0.0.0.0.0.0.0.0.0.10.10.0.1: value=1 #
03.12.2019 23:04:58 (10070 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.10.10.0.0.255.255.252.0.0.10.10.0.70: value=1 #

And here with V6.46 (a catastrophic outcome!!!!):

03.12.2019 23:00:42 (12293 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=2 #
03.12.2019 23:00:42 (12401 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:42 (12594 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:42 (12794 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:42 (13032 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13180 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13383 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13490 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13595 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:43 (13833 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14070 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14216 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14418 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14525 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14630 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (14775 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:44 (15053 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15158 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15303 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15547 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:45 (15794 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16083 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16189 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16294 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16523 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16624 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16724 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:46 (16825 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:47 (17063 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #
03.12.2019 23:00:47 (17162 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.0.0.0.0.0.0.0.0.0.10.10.0.1: value=No such object (SNMP error # 222) #
03.12.2019 23:00:47 (17262 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.10.10.0.0.255.255.252.0.0.10.10.0.70: value=No such object (SNMP error # 222) #

Please Mikrotik fix this as soon as possible! This is massive bug and should never happen in a stable version!!!!!!!!

Posted: **Wed Dec 04, 2019 11:17 am**

I Get "Limited Access" on Android App Since The Update to 6.46

Posted: **Wed Dec 04, 2019 11:27 am**

*) wireless - improved 802.11ac stability for all ARM devices with wireless;

For me no improvement at all. Still on mobile devices connected to cAP ac or hAP ac2 at 5 GHz download during speedtest peaks to more than 100 Mbit/s, then rapidly slows down. Speedtest in average shows less than 60 Mbit/s for download and more than 150 Mbit for upload. During download test CCQ falls to less than 20%. During upload CCQ is larger than 90%. The same happens in two different locations. There are no other networks at 5 GHz spectrum so noise is not the problem. How long it will take Mikrotik to fix this? Two years like it took with 802.11n and Broadcom clients? Once again regret not buying AP from other vendor.

Posted: **Wed Dec 04, 2019 11:51 am**

*) usb - general USB modem stability improvements;

RB3011UiAS-RM
usb hub + 2 usb modem = 1 usb port
Now trying to put both modems on the same port. As a result, only one modem is available.
After the firmware downgrade, everything is fine.

Posted: **Wed Dec 04, 2019 12:41 pm**

*) wireless - improved 802.11ac stability for all ARM devices with wireless;
............. How long it will take Mikrotik to fix this? Two years like it took with 802.11n and Broadcom clients? Once again regret not buying AP from other vendor.

We all would like to know... It would be great to have MikroTik router (with very good ROS features) and great working WiFi on it. MikroTik team - please improve wireless at ROS.

Posted: **Wed Dec 04, 2019 12:48 pm**

Updated my home Hap AC2 from long term 6.44.6 to 6.46 stable and ios devices keeps reassociating constantly on 5GHz and 2GHz Wifi. downgraded back to long term - 6.44.6 and WiFi again works great.

Posted: **Wed Dec 04, 2019 1:38 pm**

The cpu temperature (.1.3.6.1.4.1.14988.1.1.3.11.0) for CRS326-24G-2S+ stopped working with "object not found".

Thanks for sharing this, we will try to fix it in next RouterOS version.

Posted: **Wed Dec 04, 2019 4:50 pm**

*) wireless - added 4 chain MCS support for 802.11n wireless protocol (CLI only)

Any example ? I cant find this option in cli

?????

Posted: **Wed Dec 04, 2019 4:53 pm**

i have a lot of RB450/RB450G (very old ones, i know), RB2011, RB3011 and some few RB750 Gr3. Update was smooth on all of them, and the only problem i noted is that skin completly stopped working on the RB750 Gr3 devices. I can't even save a new skin, for example, is gets back to auth page and never works (nor gives any useful error).

In short, skin support completly stopped working on RB750 Gr3 units, was working fine until 6.45.7

Posted: **Wed Dec 04, 2019 5:55 pm**

i have a lot of RB450/RB450G (very old ones, i know), RB2011, RB3011 and some few RB750 Gr3. Update was smooth on all of them, and the only problem i noted is that skin completly stopped working on the RB750 Gr3 devices. I can't even save a new skin, for example, is gets back to auth page and never works (nor gives any useful error).

In short, skin support completly stopped working on RB750 Gr3 units, was working fine until 6.45.7

maybe the same file/folder permssion issue we see with the dude files.

Posted: **Wed Dec 04, 2019 5:57 pm**

hAP lite: after upgrade from 6.45.1 to 6.46 webproxy doesn't work

Posted: **Wed Dec 04, 2019 6:21 pm**

maybe the same file/folder permssion issue we see with the dude files.

Makes sense ... in that case, of all models i use and updated, RB750Gr3 is the only one that has the "flash/" partition, on the others everything is located on /. Maybe something permission issue related to the "flash/" folder/filesystem, if that's the case. Those who have skin files on /skins/filename.json, are not affected at all.

Posted: **Wed Dec 04, 2019 6:23 pm**

Big issue!
After the upgrade hap ac2 (RouterBOARD D52G-5HacD2HnD-TC) - stopped working any wi-fi (2 and 5 GHz)!
After downgrade to 6.45.7 - wi-fi work fine.

Posted: **Wed Dec 04, 2019 6:48 pm**

Quick Fix for the Dude:
- stop dude server
- copy entire /dude/files folder from 6.45.7 installation to your computer
- rename files folder in 6.46 to something else
- copy the files folder from your computer back to your 6.46 installation (/dude/)
- start dude server
I used Filezilla for this, everything is back to normal

Posted: **Wed Dec 04, 2019 7:27 pm**

*) ccr - improved general system stability;
Could anyone explain what does it improve? Is it addressing an issue with high CPU spikes on CCR at high speeds?

Posted: **Wed Dec 04, 2019 8:35 pm**

Ugraded Groove 52ac from 6.45.7 to v6.46 . Skins no longer works. The .json file appears to be ignored.

If I attempt to use "Design Skin" to build a new skins file the program makes the changes but when I attempt to save the new skin I am dumped back out to the login page with an error message saying that the login name or login password is incorrect.

When I downgrade back to v6.45.7 my skins files work.

Posted: **Wed Dec 04, 2019 8:38 pm**

Big issue!
After the upgrade hap ac2 (RouterBOARD D52G-5HacD2HnD-TC) - stopped working any wi-fi (2 and 5 GHz)!
After downgrade to 6.45.7 - wi-fi work fine.

No issues at all for me, upgraded two hAP AC2 fine, one has a lot of configurations as well (ipsec, qos, etc..).

Posted: **Wed Dec 04, 2019 10:21 pm**

*) wireless - improved 802.11ac stability for all ARM devices with wireless;
... During download test CCQ falls to less than 20%. During upload CCQ is larger than 90%...

I see similar behaviour on hAP ac2. In my case CCQ during upload goes beyond 100%.

Posted: **Wed Dec 04, 2019 11:19 pm**

I Get "Limited Access" on Android App Since The Update to 6.46

Yes, indeed, limited access. My connection is hAPac2 (DHCP client on ether1) -> cable modem -> ISP

Screenshot_20191204-225501__01.jpg

I also noticed that DHCP client options are missing in /export command output in comparison with output from 6.45.7

Posted: **Thu Dec 05, 2019 12:01 am**

It seems the inability to get a full Dude installation comes from the fact that 'dude/files/default' is hidden (and is automatically hidden by the dude process).

Posted: **Thu Dec 05, 2019 12:03 am**

however "push-button-5s and "push-button" are not working at all.

Only once time it was working. WPS-Accept only does work

Posted: **Thu Dec 05, 2019 9:05 am**

updating to 6.46 went smooth ... from 6.45.7 to 6.46 done thru the dude

No problems so far

Posted: **Thu Dec 05, 2019 10:13 am**

Background Images in the Dude won't load.
And what happened to the font, the "1" at the end isn't readable.

CONFIRM

Images in the Dude won't load.

/dude/files/default
Permission denied

Don't update DUDE !!!

confirm bug on ARM and CHR devices.
Temporary hint on RB3011UiAS where's attached USB flash: move all /dude content to disk1/, after that all default content is accessible and works fine.

Posted: **Thu Dec 05, 2019 11:17 am**

After the upgrade cycle (upgrade,reboot,firmware,reboot) the 5GHz Wi-Fi of a RB4011 stop 1 day later to work, a extra reboot solved the issue.
Also upgraded 2x RB2011 and 6x PL7411-2nD.
No errors found so far.

Posted: **Thu Dec 05, 2019 12:06 pm**

Yesterday I have upgraded one AP (sxt ac) with 35 clients (mixed n/ac/mipsbe/arm) first impression is that wireless worsk better in peak time.

This morning I have upgraded a tower with 5 AP (RB922) a I hope tomorow to have more data to discuss

Posted: **Thu Dec 05, 2019 12:36 pm**

As every time after upgrade I sent the mipsbe and arm firmware files for the CAPs to my CCR1009 CAPSMAN. But obviously it cannot deploy the firmware properly:

11:30:31 caps,error [E4:8D:*********,Run,CAP-E48D********] upgrade status: failed, failed to download file 'routeros-mipsbe-6.46.npk', no such file

but the files are there - as every time.

13 routeros-mipsbe-6.46.npk                                                                package                                                                                    11.2MiB dec/05/2019 11:29:51
14 routeros-arm-6.46.npk                                                                   package                                                                                    11.6MiB dec/05/2019 11:30:01

Posted: **Thu Dec 05, 2019 3:26 pm**

'routeros-mipsbe-6.46.npk', no such file

I can confirm that too....

Posted: **Thu Dec 05, 2019 5:25 pm**

Did you set

/caps-man manager set package-path

correctly?

Posted: **Thu Dec 05, 2019 7:50 pm**

*) usb - general USB modem stability improvements;
RB3011UiAS-RM
usb hub + 2 usb modem = 1 usb port
Now trying to put both modems on the same port. As a result, only one modem is available.
After the firmware downgrade, everything is fine.

Same situation for me with a USB hub and multiple USB-->RS232 adaptors - now seen as one usb port with multiple channels - these work OK but not optimal as you cannot choose separate baud rates etc. etc. for each one individually. @mikrotik can we revert to old behaviour?

Posted: **Thu Dec 05, 2019 8:18 pm**

... ask to upgrade, version 6.46
... upgrade status: failed, failed to download file 'routeros-arm-6.46.npk', no such file

Same problem.

Package path is set.
package-path: /

And the file exists:
/file> print
# NAME
0 routeros-arm-6.46.npk ...

Posted: **Thu Dec 05, 2019 10:20 pm**

Upgraded several CRS326-24G-2S+RM / CRS112-8P-4S-IN / RB1100AHx4 from 6.45.7 to 6.46 without any issues so far.

Posted: **Fri Dec 06, 2019 6:49 am**

Not so sure I want to upgrade, my RB450Gx4 is not a concern its my two CAPACs and the reports above of possible wifi issues????

Posted: **Fri Dec 06, 2019 9:38 am**

Not so sure I want to upgrade, my RB450Gx4 is not a concern its my two CAPACs and the reports above of possible wifi issues????

running several HAP AC (RB962) on 6.46 ... dozens of IOS devices. I don't see any unexpected wifi reconnects ...

Posted: **Fri Dec 06, 2019 10:35 am**

Not so sure I want to upgrade, my RB450Gx4 is not a concern its my two CAPACs and the reports above of possible wifi issues????
running several HAP AC (RB962) on 6.46 ... dozens of IOS devices. I don't see any unexpected wifi reconnects ...

It's good that wifi still works well after the upgrade on mipsbe devices (hAP ac), but issues are reported on arm devices (hAP ac2, cAP ac, RB4011).

Posted: **Fri Dec 06, 2019 1:27 pm**

Another issue I have on all my devices is that a scheduler script that used to run on boot, but with version 6.46 dosen't run anymore:

add name=UpgradeFirmware on-event="if ([/system routerboard get current-firmware] < [/system routerboard get upgrade-firmwar\
e]) do={\r\
\n/system routerboard upgrade\r\
\n:delay 1\r\
\n/system reboot\r\
\n}\r\
\n" policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive start-time=startup

Posted: **Fri Dec 06, 2019 4:40 pm**

Same situation for me with a USB hub and multiple USB-->RS232 adaptors - now seen as one usb port with multiple channels - these work OK but not optimal as you cannot choose separate baud rates etc. etc. for each one individually. @mikrotik can we revert to old behaviour?

This is really bad, I need to set different baudrates for two RS232 adapters because one device needs 9600 and other 38400 and these can't be changed. Grouping them as multichannel serial with single settings is really bad idea...

Posted: **Fri Dec 06, 2019 8:23 pm**

DHCPv6 Client is making Problems.
After changing some settings on the client I cann't configure or print it anymore.
Neither via Winbox nor via CLI.

script error: action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

Posted: **Fri Dec 06, 2019 8:52 pm**

Another issue I have on all my devices is that a scheduler script that used to run on boot, but with version 6.46 dosen't run anymore:

add name=UpgradeFirmware on-event="if ([/system routerboard get current-firmware] < [/system routerboard get upgrade-firmwar\
e]) do={\r\
\n/system routerboard upgrade\r\
\n:delay 1\r\
\n/system reboot\r\
\n}\r\
\n" policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive start-time=startup

I've verified this issue and can confirm the problem. It worked with 6.44.6 for example but no longer with 6.46.
The issue is unrelated to the content of "do". It seems that's something wrong with the system-commands in the if-part of the script.

Posted: **Fri Dec 06, 2019 9:02 pm**

Background Images in the Dude won't load.
And what happened to the font, the "1" at the end isn't readable.

CONFIRM

Images in the Dude won't load.

/dude/files/default
Permission denied

Don't update DUDE !!!
confirm bug on ARM and CHR devices.
Temporary hint on RB3011UiAS where's attached USB flash: move all /dude content to disk1/, after that all default content is accessible and works fine.

FYI, the font issue is not present in the long-term 6.44.6 software. Since we're running CHR's it was easier to change the package channel than to downgrade back to 6.45.7.

Posted: **Fri Dec 06, 2019 9:54 pm**

Upgraded 2 CAPacs and 3 RB952s from 6.45.7, no issues, all boxes work as before upgrade.

Although release notes mention wireless stability fixes and "improved radar detection algorithm", false positive radar detections on DFS channels still occur on 6.46 with the same average rate as in previous versions. Also, AP can still be "radar-killed" by RPi 3B+ or 4 during association phase (reported to support at the beginning of 2019). Thus staying on frequency-mode=superchannel since regulatory-domain, at least for country=cz, is useless.

Ondrej

Posted: **Fri Dec 06, 2019 10:44 pm**

if ([/system routerboard get current-firmware] < [/system routerboard get upgrade-firmware]) do={ ...

The values are of type "str" (string):

[admin@Mikrotik] > :put [ :typeof [ /system routerboard get current-firmware ] ]
str
[admin@Mikrotik] > :put [ :typeof [ /system routerboard get upgrade-firmware  ] ]   
str

So you can not use mathematical expression to compare them. Just replace "<" with "!=":

if ([/system routerboard get current-firmware] != [/system routerboard get upgrade-firmware]) do={ ...

Posted: **Sat Dec 07, 2019 3:05 pm**

... ask to upgrade, version 6.46
... upgrade status: failed, failed to download file 'routeros-arm-6.46.npk', no such file

Same problem.

Package path is set.
package-path: /

And the file exists:
/file> print
# NAME
0 routeros-arm-6.46.npk ...

I have CAPSMAN at RB3011 and remote CAPs were upgraded successfully.
But I have also another CAPSMAN manager at hEX and I got the same error trying to upgrade its remote CAPs

upgrade status: failed, failed to download file 'routeros-mipsbe-6.46.npk', no such file

The only diffrence with CAPSMAN's setting between RB3011 and hEX:
RB3011's package path is /pub
hEX's package path is / (root)
So here is the bug of 6.46: CAPSMAN can't upgrade remote CAPs from root.
Solution:
1. create any subfolder, for example "pub" (to create subfolder in Mikrotik create empty folder in Windows and drag this folder to Mikrotik)
2. Move your upgrade NPK file to newly create subfolder.
3. Change settings in CAPSMAN: CAP Interface -> Manager -> Package path from root (/) to your newly created subforder (/pub)
4. Start upgrade remote caps

Posted: **Sat Dec 07, 2019 7:19 pm**

(...)

So you can not use mathematical expression to compare them. Just replace "<" with "!=":
Code: Select all
if ([/system routerboard get current-firmware] != [/system routerboard get upgrade-firmware]) do={ ...

Further, you can get quite strange results in the test. For example, with development channel selected and 6.46 installed:

[admin@Mikrotik] > :put ([system routerboard get current-firmware]<([:system package update check-for-updates as-value ]->"latest-version"))  
Script Error: cannot compare if string is less than string
[admin@Mikrotik] > :put "$[system routerboard get current-firmware]<$([:system package update check-for-updates as-value ]->"latest-version")"
6.46<7.0beta3

With long-term channel selected and 6..46 installed:

[admin@Mikrotik] > :put ([system routerboard get current-firmware]<([:system package update check-for-updates as-value ]->"latest-version"))
true
[admin@Mikrotik] > :put "$[system routerboard get current-firmware]<$([:system package update check-for-updates as-value ]->"latest-version")" 
6.46<6.44.6
[admin@MikrotikTole

Posted: **Sat Dec 07, 2019 8:40 pm**

RB1100ahx2
6.45.7->6.46

Upgrade via winbox (system-packages)
Upgrade went seemingly ok, rebooted fine and all packages were displayed as 6.46
But clicking on "check installation", got message "system package damaged".

Reverted back to 6.45.7 -> "check installation" ok again.
Tried upgrading several times, 100% reproducable.

Posted: **Sun Dec 08, 2019 11:16 am**

Skin Stopped working , It is now open to any user I create , Files are default in /Skin Folder , running 3011 6.46

Posted: **Sun Dec 08, 2019 2:29 pm**

PPPoE stopped accepting new connections after 3 days of uptime on our CCR1036 on ROS 6.46. Number of PPPoE users connected was 628.
When I disconnected 10 users, a 10 other users which couldn't connect earlier was connected, and disconnected users keep trying to connect without success.
Router reboot helps, 698 users were connected without issues.
Sadly I didn't grab support file when there was a problem.

Screenshot of a log when there was a problem

1.png

Posted: **Sun Dec 08, 2019 7:30 pm**

on HAP AC (RB962) wireless is no good,speed is poor vs 6.45.7,in special download
ping=10,12ms!!!on 6,45,7 ping is 1 or 2ms

Posted: **Sun Dec 08, 2019 11:59 pm**

on HAP AC (RB962) wireless is no good,speed is poor vs 6.45.7,in special download
ping=10,12ms!!!on 6,45,7 ping is 1 or 2ms

Well my HAP AC did much worse than Yours, I am using capsman2 - I got almost useless 5GHz Wifi, ping up to 2700ms..
2,4GHz also no good, much better bud some jerks and pauses, some "page did not load.." surprises.
I had to use cable to downgrade to 6.45.7, succeed and all is ok again.
Well I do not feel confident with mean of "stable" release anymore..

I have some HAP AC^2 on distant site, falling off VPN every few hours or more -
Now I am not sure whether it could be related to 6.46 update. ?

Posted: **Mon Dec 09, 2019 7:57 am**

This version completely break PPP Server functionality. When under load >700 users, new users cannot login to either the PPPOE service or the PPTP. The connection is abruptly closed by the CCR1036. PPTP users on Windows 10 Report that the VPN server has run out of resources or not accepting connection. Wifi Routers / PPPOE Clients are not able to establish PPPOE session once the logged in users reach around 700. Reverting to older version fixed the issues for us. Nothing in the Log, its like the PPP Server just stops.

Posted: **Mon Dec 09, 2019 11:31 am**

I got almost useless 5GHz Wifi, ping up to 2700ms..
2,4GHz also no good, much better bud some jerks and pauses, some "page did not load.." surprises.
I had to use cable to downgrade to 6.45.7, succeed and all is ok again.
Well I do not feel confident with mean of "stable" release anymore..

I have some HAP AC^2 on distant site, falling off VPN every few hours or more -
Now I am not sure whether it could be related to 6.46 update. ?

RB750Gr3 - everything was fine for a few hours and then all traffic (LAN and WAN) slowed down to crawl just as described here. Reboot solved the issue, but there was no time (or sense) to test this further on my home network. Downgrade solved the problem.

Will pass on this one (I'm not deploying "stable" releases to customers anyway)...

Posted: **Mon Dec 09, 2019 1:02 pm**

Had lot of issues with pppoe in 6.46
reverting back to 6.44.6 & things got back to normal.

Posted: **Mon Dec 09, 2019 3:13 pm**

So you can not use mathematical expression to compare them. Just replace "<" with "!=":
Code: Select all
if ([/system routerboard get current-firmware] != [/system routerboard get upgrade-firmware]) do={ ...

Done, and worked, thank you.

Posted: **Mon Dec 09, 2019 8:13 pm**

Not working /system upgrade
I have my own upgrade-package-source. After upgrade 6.46 not working. It's big problem for me, i have automatic script on more than 1000 devices.

Posted: **Tue Dec 10, 2019 10:02 am**

DO not upgrade if you have a PPPoE connection. Simple pppoe connection to mikrotik server stopt working in 6.46. No connection error in log from server.
Revert back to 6.44.6 and the PPPoe connection is fine.

Posted: **Tue Dec 10, 2019 10:29 am**

Hi all

couldn't find a way to delete post, so i deleted the post's content instead!

/peter

Posted: **Tue Dec 10, 2019 10:43 am**

Logging actions to an USB-disk are lost after reboot (for me on a hAP ac²). It seems, that the USB-disk is recognized too late after system boot.

Already mentioned here:
viewtopic.php?t=153588

Posted: **Tue Dec 10, 2019 3:28 pm**

Hi
Device - hAP AC2. Update - from 6.45.7 to 6.46 with WinBOX 6.20. Result - crash, device is not available from Winbox and reboot after about 1 min.
Restored the device through netinstall to 6.45.7. The device is able to work. I tried to flash 6.46 through netinstall - crash, the analog result and symptoms.
After that - restored the device through netinstall to 6.45.7. Now the device is working fine.

how can I find a problem - I need to update two more devices of other types

Posted: **Tue Dec 10, 2019 3:46 pm**

After Upgrading to v6.46 some of our CaptivePortals do not open anymore. Previously after connecting to the WIFI your Phone would open a captiveportal when using the hotspot feature.This isnt true anymore for some devices. Instead the phone will connect to the wifi and bypass the captiveportal procedure. I figure it has something todo with redirecting of WISPr, because opening the hotspot-captive via browser works perfectly, but opening http://www.apple.com/library/test/success.html will no longer redirect to the hotspot-captiveportal

Does anyone else experience similar problems and has some insights?

Posted: **Tue Dec 10, 2019 3:52 pm**

In the v6.46beta, you indicated

*) ptp - added support for IEEE 1588 Precision Clock Synchronization Protocol on CRS317-1G-16S+ (CLI only);

Did this feature make the v6.46 [stable] release? Is this IEEE 1588 version 2?

Posted: **Tue Dec 10, 2019 3:54 pm**

In the v6.46beta, you indicated

*) ptp - added support for IEEE 1588 Precision Clock Synchronization Protocol on CRS317-1G-16S+ (CLI only);

Did this feature make the v6.46 [stable] release? Is this IEEE 1588 version 2?

From 6.46rc1:

!) ptp - disabled support for IEEE 1588 Precision Clock Synchronization Protocol until further notice;

Posted: **Tue Dec 10, 2019 7:17 pm**

Upgraded, but seems unstable for Apple devices with frequent disconnects.

Also, 1 device became unresponsive, CAP-AC. It serves users, but unable to access webfig and ssh. Have experienced the same with this and other devices previously when upgrading, and ultimately I have been forced to completely reinstall...

Posted: **Tue Dec 10, 2019 9:43 pm**

I have 3 machines that I upgraded to 6.46. No issues with 2 of the upgrades but after upgrade on the third I am unable to login using the web interface. I get an "ERROR: Not Found" message but I am able to log in by ssh using the same username and password.

Update: This is true only using the Safari browser. Webfig on the third machine can be accessed using Firefox. Safari works on the other 2 machines.

Posted: **Tue Dec 10, 2019 10:01 pm**

PPPoE stopped accepting new connections after 3 days of uptime on our CCR1036 on ROS 6.46. Number of PPPoE users connected was 628.
When I disconnected 10 users, a 10 other users which couldn't connect earlier was connected, and disconnected users keep trying to connect without success.
Router reboot helps, 698 users were connected without issues.
Sadly I didn't grab support file when there was a problem.

Screenshot of a log when there was a problem
1.png

I can to confirm the same problem in two CCR's. Not tested with another architectures.

Posted: **Wed Dec 11, 2019 10:03 am**

So... did anybody tried to turn off your CAPs on 6.46? I mean actualy disconnect them from power and turning it on again...
When we do this, the device resets configuration to defaults and stops working as CAP.
Also there is same problem on latest beta, but on 6.45.7 this does not happen...
We were testing this only on wap ac and hap ac lite, as we did not have more time to test more devices at the moment...

Posted: **Wed Dec 11, 2019 2:14 pm**

Quick Fix for the Dude:
- stop dude server
- copy entire /dude/files folder from 6.45.7 installation to your computer
- rename files folder in 6.46 to something else
- copy the files folder from your computer back to your 6.46 installation (/dude/)
- start dude server
I used Filezilla for this, everything is back to normal

How would i go about fixing this if i dont have a 6.45.7 installation to grab the files from ?

Thanks

Posted: **Wed Dec 11, 2019 3:14 pm**

Iphone connect . . . reassociating . . . disconnect . . . connect . . . ??????????????????????? Mikrotik feature ?

Dec/10/2019 20 43 25 disk wireless. inlo 3B SE 2A connecled. signál slrenglh -6S
Dec/10/2019 20 49 39 disk wireless. inlo 33 SE 2A reassocialing
Dec/10/2019 20 49 35 disk wireless. inlo 3B 3E 2A disconnecled. ok
Dec/10/2019 20 49 39 disk wireless. inlo 3B 8E 2A connecled. signál slrenglh -6S
Dec/10/2019 20 52 53 disk wireless. inlo 3B 3E 2A reassocialing
Dec/10/2019 20 52 53 disk wireless. inlo 3B SE 2A disconnecled. ok
Dec/10/2019 20 52 53 disk wireless. inlo 3B 3E 2A connecled. signál slrenglh -71
Dec/10/2019 20 55 14 disk wireless. inlo 3B 3E 2A reassocialing
Dec/10/2019 20 55 14 disk wireless. inlo 3B SE 2A disconnecled. ok
Dec/10/2019 20 55 14 disk wireless. inlo 33 SE 2A connecled. signál slrenglh -70
Dec/10/2019 20 57 2S disk wireless. inlo 3B 3E 2A reassocialing
Dec/10/2019 20 57 2S disk wireless. inlo 3B 8E 2A disconnecled. ok
Dec/10/2019 20 57 2S disk wireless. inlo 3B 3E 2A connecled. signál slrenglh -70
Dec/10/2019 20 53 27 disk wireless. inlo 3B SE 2A disconnecled. etfensive dala loss
Dec/10/2019 20 59 44 disk wireless. inlo 3B 3E 2A connecled. signál slrenglh -70
Dec/10/2019 21 1 5S disk wireless. inlo 3B 3E 2A reassocialing
Dec/10/2019 21 1 53 disk wireless. inlo 3B SE 2A disconnecled. ok
Dec/10/2019 21 1 5S disk wireless. inlo 33 SE 2A connecled. signál slrenglh -70
Dec/10/2019 21 2 45 disk wireless. inlo 3B SE 2A reassocialing
Dec/10/2019 21 2 45 disk wireless. inlo 3B SE 2A disconnecled. ok
Dec/10/2019 21 2 45 disk wireless. inlo 3B SE 2A connecled. signál slrenglh -70
Dec/10/2019 21 3 27 disk wireless. inlo 3B SE 2A reassocialing
Dec/10/2019 21 3 27 disk wireless. inlo 3B 3E 2A disconnecled. ok
Dec/10/2019 21 3 27 disk wireless. inlo 3B SE 2A connecled. signál slrenglh -70
Dec/10/2019 21 4 11 disk wireless. inlo 3B SE 2A reassocialing
Dec/10/2019 21 4 11 disk wireless. inlo 33 SE 2A disconnecled. ok
Dec/10/2019 21 4 11 disk wireless. inlo 3B SE 2A connecled. signál slrenglh -74
Dec/10/2019 21 4 47 disk wireless. inlo 3B SE 2A disconnecled. etfensive dala loss
Dec/10/2019 21 5 0 disk wireless. inlo 3B SE 2A connecled. signál slrenglh -74
Dec/10/2019 21 5 5S disk wireless. inlo reassocialmg

Posted: **Wed Dec 11, 2019 3:19 pm**

The phone disconnected itself. AP did not drop it, the message is clear.

Posted: **Wed Dec 11, 2019 3:52 pm**

Updated my RB3011 on this release. No issues! (...so far

)

Posted: **Wed Dec 11, 2019 3:53 pm**

After Upgrading to v6.46 some of our CaptivePortals do not open anymore. Previously after connecting to the WIFI your Phone would open a captiveportal when using the hotspot feature.This isnt true anymore for some devices. Instead the phone will connect to the wifi and bypass the captiveportal procedure. I figure it has something todo with redirecting of WISPr, because opening the hotspot-captive via browser works perfectly, but opening http://www.apple.com/library/test/success.html will no longer redirect to the hotspot-captiveportal

Does anyone else experience similar problems and has some insights?

I upgraded a lot of RB2011s and RB3011s, all serving hotspot-enabled networks, and had no problem at all.

Posted: **Wed Dec 11, 2019 4:17 pm**

After Upgrading to v6.46 some of our CaptivePortals do not open anymore. Previously after connecting to the WIFI your Phone would open a captiveportal when using the hotspot feature.This isnt true anymore for some devices. Instead the phone will connect to the wifi and bypass the captiveportal procedure. I figure it has something todo with redirecting of WISPr, because opening the hotspot-captive via browser works perfectly, but opening http://www.apple.com/library/test/success.html will no longer redirect to the hotspot-captiveportal

Does anyone else experience similar problems and has some insights?
I upgraded a lot of RB2011s and RB3011s, all serving hotspot-enabled networks, and had no problem at all.

For me it were 2 positives from around 1600 hotspot-networks so far. Any idea how to debug this?

Posted: **Wed Dec 11, 2019 9:46 pm**

The phone disconnected itself. AP did not drop it, the message is clear.

It is not normal for the phone to disconnect and connect every 2 minutes. . . I plugged in the old wl500gp and everything ok. On microtics samsung ok, only the iPhone has a problem. Two iPhones tested, both behave the same way. Or ? Thx

Posted: **Thu Dec 12, 2019 6:42 am**

I had problem on many version of ros (RB4011iGS+5HacQ2HnD-IN) on 5G wifi.
Recently on 6.46 stable channel, everything is great now.
Runing torrent on 5G wifi (RB4011iGS+5HacQ2HnD-IN), 8 days in a row without failing once.

I'm sticking on this 6.46 for now and might for a long time.

Thanks for this update.

Posted: **Thu Dec 12, 2019 1:26 pm**

After upgraded to 6.46, webfig design not working. It shown all items same as default. My router are RB450G, RB2011 and CCR1009.

Posted: **Thu Dec 12, 2019 9:02 pm**

6.46 not work pppoe server!!!

Posted: **Fri Dec 13, 2019 12:11 am**

after upgrading our dude server to 6.46 we are encountering this errorr after a few seconds of uptime

routeros management socket failed: Too many open files(24) (6)

our dude server is a licenced CHR dedicated to the dude, no such issue exists on 6.45.6

Posted: **Fri Dec 13, 2019 2:31 am**

Upgrade from RouterOS v6.45.7 to 6.46 on SXTR+R11e-LTE6 at 7/dec/2019 13:00.
Work as CPE - without passthrough mode means simple Router.
At v6.45.7 works perfect via ~20 days.

Pros:
cell-monitor start show data in EARFCN column.

winbox_v3.20_64_WdbLEa3x99.png

Cons 1:
Less stability of R11e-LTE6 connection when I use "Using Cell lock" after ~2d on new ROS.
Time 00:06
After 20h from "Cell Lock" start's stoping a internet, no ping or any nexthops in traceroute. Public IP at lte1 interface exist, connection exist without Rx/Tx traffic even if I ping it from my smartphone (via ISP connection, remotely).
Disable and Enable lte1 interface and works again.

D0i8pcBuRk.png

Time 09:08 - after next 9h still with problems. I see only Band3 connected without B8 who have better signal and works as my stability line and without CellLock is a primary band.
When problem exist the same LTE logs happens, no internet, any next hops in traceroute.
New error in resetting "Using Cell lock" like:

interface lte at-chat lte1 input="AT*Cell=0"
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

Cell-Monitor show me only B8 but ignore that is connected into B3 and show me a signal etc.
I cannot check Scan - No operators detected.
I do Support File and open it / check it at my account microtik.com - no any new information or logs .
Second time resetting "Using Cell lock" works and bring me internet again.
Problem exist few times more... I enable WatchDog :(.

HW3mNlMkN2.png

Cons 2:
I must do "Refresh" at webpage, Clicking to links again, sometimes long loading webpage, strange, just like MSS problem. MTU is OK.

Cons 3:
When I put SXTR on the floor and comeback to optimal position then internet is not work, signals are frozen !.
ROS 6.45.7 it's loose signal and restore signal - few timeout's and internet comeback.
ROS 6.46 it's stoping traffic, RSRQ -19.5 dB and other signal parameters not change a little via minutes of waiting... means a winter one snow and your remote branch will be disconnected :(. WatchDog must be setup at production.

Posted: **Fri Dec 13, 2019 3:33 am**

We have a problem with ros 4.46 related to pppoe sessions. Apparently Mikrotik gets PADI but doesn't reply with PADO.

Posted: **Fri Dec 13, 2019 3:38 am**

PPPoE stopped accepting new connections after 3 days of uptime on our CCR1036 on ROS 6.46. Number of PPPoE users connected was 628.
When I disconnected 10 users, a 10 other users which couldn't connect earlier was connected, and disconnected users keep trying to connect without success.
Router reboot helps, 698 users were connected without issues.
Sadly I didn't grab support file when there was a problem.

Screenshot of a log when there was a problem
1.png

We have the same problem on CCR1016. With over 700 sessions.

Posted: **Fri Dec 13, 2019 9:13 am**

Hi i've just upgrade to 6.46 stable to various mikrotik routers.I 've noticed that if i change some parameters in interface wireless configuration(mode,freq,sc-list etc)
it freezes for no reason (show initializing in bottom interface status menu) then i have to manually access the router,reset and
reconfigure the interface in order to work.This happened to me in 3 different routers (rb433,rb953,rb922) and its a serious issue
specialy for remote location installations.

Posted: **Fri Dec 13, 2019 9:31 am**

Issue with many PPP (including PPPoE) sessions will be fixed in the next stable and testing builds. All issues with file accessing including Dude, skins, etc will also be fixed in stable and testing builds.

We are already working on 6.46.1 version and if all goes smoothly it will be released this year. Sorry for any inconvenience.

Posted: **Fri Dec 13, 2019 9:42 am**

Hi i've just upgrade to 6.46 stable to various mikrotik routers.I 've noticed that if i change some parameters in interface wireless configuration(mode,freq,sc-list etc)
it freezes for no reason (show initializing in bottom interface status menu) then i have to manually access the router,reset and
reconfigure the interface in order to work.This happened to me in 3 different routers (rb433,rb953,rb922) and its a serious issue
specialy for remote location installations.

I have observed similar behavior on SXT 4G kit. If I change something in lte1 interface (for example APN, or add/remove SIM card) - ether1 stops responding, LED's turns off. Interface looks like disabled. I connected to device via ether2 - interface ether1 was not disabled, no suspicious signs, but LED do not shine. Reboot do not helps. I have even uninstalled device from mounting on roof, was ready to send to RMA. It happens several times, each time after reset device started to work normally. And this is not a cable issues, I used several cables. Note - this happens on 6.44.6 long-term and only with ether1.

Posted: **Sat Dec 14, 2019 12:34 am**

>

confirm bug on ARM and CHR devices.
> Temporary hint on RB3011UiAS where's attached USB flash: move all /dude content to disk1/, after that all default content is accessible and works fine.

How to do that? I'm trying to drag dude dir to disk1 but Winbox says 'Couldn't change file ... - action failed (6)'

Posted: **Sat Dec 14, 2019 12:49 am**

After update to 6.46, problem of explain in below topic occuer. Please fix that.
viewtopic.php?f=8&t=154498

Posted: **Sat Dec 14, 2019 11:42 pm**

RB850Gx2

Similar to a previous poster, I also ran into a "damaged" routeros package error when updating a RB850Gx2 from 6.45.7 stable to 6.46 stable. The update seems to work fine, but the installation check fails at around 55%. I was able to revert it to 6.45.7 without any issues. I downloaded 6.46 manually, verified the checksums, and tried the update again, but it failed in the same manner.

Posted: **Mon Dec 16, 2019 8:14 pm**

I upgraded my fleet last Monday night from 6.45.6 to 6.46 and we've had several instances of devices running hotspots fail to bring up a splash page. Redirect doesn't work, manually accessing the splash page via IP/hostname doesn't work. There's just no way to authenticate outside of being bypassed. Disabling hotspot server allows access.

Reboot temporarily resolves it. Considering I've seen references to hotspot being broken on 6.45.7, 6.46, and also everything after 6.44.6 long-term, I am ad-hoc downgrading devices to 6.44.6 long-term channel as they come up.

I've submitted my supout.rif via email.

Posted: **Mon Dec 16, 2019 9:40 pm**

RB1100AHx2

Upgrade from 6.45.7->6.46

Upgrade via winbox, upgrade firmware went ok, rebooted fine.
But web proxy stoped working after a while. Do Disable\Enable proxy work again, after about 2 hours proxy stopped working again.

Downgrade back to 6.45.7 -> web proxy working ok

Posted: **Tue Dec 17, 2019 8:28 am**

Hi!
I have Dude on x86 and
After update from 6.45.7 to 6.46
in about 24-48h no more can access to port 80: Error 404: Not Found
but i can ping and can access with winbox
after reboot again everything working and again after 24-48h cant access port 80

Posted: **Tue Dec 17, 2019 8:59 am**

2x WapR lte kit bricked after updates for 6.46 !!!!
All people need atention with product and updates from Mikrotik !!!!
It's not stable it's not solid !!! Never tested completly!!!

Posted: **Tue Dec 17, 2019 10:25 am**

It's an old and very clever rule for every software - never put in production new release before first bugfix subrelease, so in this case wait for 6.46.1 at least.

Posted: **Tue Dec 17, 2019 11:48 am**

It's an old and very clever rule for every software - never put in production new release before first bugfix subrelease, so in this case wait for 6.46.1 at least.

+++

Posted: **Tue Dec 17, 2019 12:27 pm**

Any chance that SUP-3815 might get fixed in 6.46.1 ? It's regarding this: viewtopic.php?f=2&t=154743&p=764979#p764979

Posted: **Tue Dec 17, 2019 3:38 pm**

New version 6.46.1 has been released in stable RouterOS channel:

viewtopic.php?f=21&t=154848

MikroTik

v6.46 [stable] is released!

v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Radar false positives still occuring

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!

Re: v6.46 [stable] is released!