Installed 6.47beta8 and works fine now, thanks!
Hello. You have to consider that a lot of devices are unable to support ros 7 because of flash disk limitations. I think that they should develop ros 6 for a loong time.
I moved the question in ros v7.0beta4 topic !
Just testing this…
[admin@MikroTik] /system health gauges> :put [ :typeof [ get [ find where type="V" ] value ] ]
str
[admin@Mikrotik] /system health gauges> :put [ get [ find where type="V" ] value ]
50.3
As RouterOS does not support decimal numbers with place (but only integer)… Any chance to change the unit (V/10 or mV) and return numeric values here?
That would simplify using the values in scripts a lot! Thanks!
Version 6.47beta19 has been released.
Before an upgrade:
- Remember to make backup/export files before an upgrade and save them on another storage device;
- Make sure the device will not lose power during upgrade process;
- Device has enough free storage space for all RouterOS packages to be downloaded.
What’s new in 6.47beta19 (2020-Jan-09 08:08):
**MAJOR CHANGES IN v6.47:
!) socks - added support for SOCKS5 (RFC 1928);
----------------------**
Changes in this release:
!) socks - added support for SOCKS5 (RFC 1928);
*) bonding - improved slave interface MAC address handling;
*) bonding - prefer primary slave MAC address for bonding interface;
*) bridge - added logging message when a host MAC address is learned on a different bridge port;
*) chr - improved stability when changing ARP modes on e1000 type adapters;
*) console - prevent “flash” directory from being removed (introduced in v6.46);
*) console - updated copyright notice;
*) crs305 - disable optical SFP/SFP+ module Tx power after disabling SFP+ interface;
*) defconf - fixed “caps-mode” not initialized properly after resetting;
*) defconf - fixed default configuration loading on RBwAPG-60adkit (introduced in v6.46);
*) discovery - do not send CDP and LLDP packets on interfaces that does not have MAC address;
*) 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 - added “radius-mac-format” parameter (CLI only);
*) health - added “gauges” submenu with SNMP OID reporting;
*) lora - added “ru-864-mid” channel plan;
*) lora - fixed packet sending when using “antenna-gain” higher than 5dB;
*) lora - improved immediate packet delivery;
*) lte - do not allow running “scan” on R11e-4G;
*) lte - fixed “band” value setting when configuration is reset on R11e-4G;
*) lte - fixed “cell-monitor” on R11e-LTE in 3G mode;
*) lte - fixed “earfcn” reporting on R11e-LTE6 in UMTS and GSM modes;
*) lte - improved all APN session activation after disconnect on R11e-LTE;
*) lte - report only valid info parameters on R11e-LTE6;
*) lte - use APN from network when blank APN used on R11e-4G;
*) ppp - fixed minor typo in “ppp-client” monitor;
*) qsfp - do not report bogus monitoring readouts on modules without DDMI support;
*) qsfp - improved module monitoring readouts for DAC and break-out cables;
*) routerboard - added “mode-button” support for RBcAP2nD;
*) sniffer - allow setting port for “streaming-server”;
*) snmp - added “dot1qTpFdbTable” OID reporting for Q-BRIDGE-MIB;
*) snmp - improved OID policy checking and error reporting on “set” command;
*) supout - added “dot1x” section to supout files;
*) system - correctly handle Generic Receive Offloading (GRO) for MPLS traffic;
) system - fixed ".auto.rsc" file execution (introduced in v6.46);
*) system - fixed “check-installation” on PowerPC devices (introduced in v6.46);
*) traceroute - improved stability when invalid packet is received;
*) traffic-generator - improved memory handling on CHR;
*) webfig - allow skin designing without “ftp” and “sensitive” policies;
*) webfig - fixed “skins” saving to “flash” directory if it exists (introduced in v6.46);
*) winbox - automatically refresh “Packets” table when new packets are captured by “Tools/Packet Sniffer”;
*) winbox - fixed “Default Route Distance” default value when creating new LTE APN;
*) winbox - removed duplicate “join-eui”, “dev-eui”, “counter”, “chain”, “size” and “payload” parameters under “Lora/Traffic”;
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 expected or after crash.
!) socks - added support for SOCKS5 (RFC 1928);
Well, it’s january, and it’s christmas again! S2
*) winbox - automatically refresh “Packets” table when new packets are captured by “Tools/Packet Sniffer”;
AWESOME, So good to see this 
The button with “Clear” and “AutoScrool” will be good addition as future request.
.
.
*) lte - fixed “cell-monitor” on R11e-LTE in 3G mode;
*) lte - fixed “earfcn” reporting on R11e-LTE6 in UMTS and GSM modes;
But still developers can easily show current PHY-CellID because it is in hex in at command response:
/log print where message~"CREG: 1"
lte,async,raw SXTR__LTE: $CREG: 1,"2b01","047ff4fb",2,"021"
# $CREG: 1,"LAC hex","CellID hex",UMTS type,"PHY-CellID hex"
In my example 021hex => 33 dec and CellLock in 3G works as:
/interface lte at-chat lte1 input="at*cell=2,2,,3030,33"
but with all detected phy-cellid from cell-monitor I cannot connect and my current 33 dec is not detected by cell-monitor.
Reported: SUP-3946
.
.
.
*) lte - report only valid info parameters on R11e-LTE6;
What this means?
.
.
Error 1) Cannot login via RoMon and WinBox (by IPv4).
Upgrade SXTR+R11e-LTE6 = not possibility to login via RoMON and WinBox by IP.
MACTelnet and WinBox via mac-address works. Logs:
16:46:50 echo: system,error,critical login failure for user marcin.przysowa from 192.168.88.253 by romon 00:00:00:00:00:01 via winbox
22:25:22 warning denied winbox/dude connect from 192.168.91.253
I type many time’s the same credentials. They works via MacTelnet, not works by RoMON. I create a super easy asd user with password asd123 and still the same.
New Sniffer not see the incomming IPv4 but MAC-ADDRESS-es but in logs he report the IPv4 and tools torch see the IPv4.
from PC
Socks5 with radius auth? maybe?
@irqhost: why do you quoute whole post? Isn’t it enough just to ask a question in this thread?
Many does not see det big red post button at the bottom of the page 
Just for your information, the SNMP-IP-Forward is still broken (with V6.47beta19):
Testing OIDs...
16.01.2020 12:01:28 (1401 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=3 #
16.01.2020 12:01:28 (1433 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) #
16.01.2020 12:01:28 (1467 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) #
16.01.2020 12:01:28 (1503 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.1.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:28 (1532 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) #
16.01.2020 12:01:28 (1560 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) #
16.01.2020 12:01:28 (1587 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.2.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (1617 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) #
16.01.2020 12:01:29 (1649 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) #
16.01.2020 12:01:29 (1680 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.3.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (1710 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) #
16.01.2020 12:01:29 (1740 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) #
16.01.2020 12:01:29 (1764 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.4.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (1791 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) #
16.01.2020 12:01:29 (1818 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) #
16.01.2020 12:01:29 (1851 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.5.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (1880 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) #
16.01.2020 12:01:29 (1906 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) #
16.01.2020 12:01:29 (1930 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.6.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (1958 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) #
16.01.2020 12:01:29 (1981 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) #
16.01.2020 12:01:29 (2008 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.7.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2033 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) #
16.01.2020 12:01:29 (2062 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) #
16.01.2020 12:01:29 (2086 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.8.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2112 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) #
16.01.2020 12:01:29 (2137 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) #
16.01.2020 12:01:29 (2166 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.10.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2213 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) #
16.01.2020 12:01:29 (2233 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) #
16.01.2020 12:01:29 (2257 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.11.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2284 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) #
16.01.2020 12:01:29 (2308 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) #
16.01.2020 12:01:29 (2332 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.12.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2357 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) #
16.01.2020 12:01:29 (2379 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) #
16.01.2020 12:01:29 (2405 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.13.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2426 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) #
16.01.2020 12:01:29 (2449 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) #
16.01.2020 12:01:29 (2474 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.14.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2495 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) #
16.01.2020 12:01:29 (2524 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) #
16.01.2020 12:01:29 (2543 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.15.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
16.01.2020 12:01:29 (2565 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) #
16.01.2020 12:01:29 (2589 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) #
16.01.2020 12:01:30 (2614 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
Test 1.3.6.1.2.1.4.24.4.1.16.192.168.11.0.255.255.255.0.0.192.168.11.1: value=No such object (SNMP error # 222) #
And here are the expected result after downgrading (with V6.44.6):
Testing OIDs...
16.01.2020 12:06:09 (1173 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=3 #
16.01.2020 12:06:09 (1200 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 #
16.01.2020 12:06:09 (1226 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 #
16.01.2020 12:06:09 (1255 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.1.192.168.11.0.255.255.255.0.0.192.168.11.1: value=192.168.11.0 #
16.01.2020 12:06:09 (1283 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 #
16.01.2020 12:06:09 (1304 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 #
16.01.2020 12:06:09 (1328 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.2.192.168.11.0.255.255.255.0.0.192.168.11.1: value=255.255.255.0 #
16.01.2020 12:06:09 (1354 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 #
16.01.2020 12:06:09 (1383 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 #
16.01.2020 12:06:09 (1405 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.3.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
16.01.2020 12:06:09 (1430 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 #
16.01.2020 12:06:09 (1453 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 #
16.01.2020 12:06:09 (1480 ms) : SNMP Datatype: ASN_IPADDRESS
Test 1.3.6.1.2.1.4.24.4.1.4.192.168.11.0.255.255.255.0.0.192.168.11.1: value=192.168.11.1 #
16.01.2020 12:06:09 (1504 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 #
16.01.2020 12:06:09 (1529 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 #
16.01.2020 12:06:09 (1554 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.5.192.168.11.0.255.255.255.0.0.192.168.11.1: value=12 #
16.01.2020 12:06:09 (1581 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 #
16.01.2020 12:06:09 (1601 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 #
16.01.2020 12:06:09 (1624 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.6.192.168.11.0.255.255.255.0.0.192.168.11.1: value=3 #
16.01.2020 12:06:09 (1648 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 #
16.01.2020 12:06:09 (1670 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 #
16.01.2020 12:06:09 (1697 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.7.192.168.11.0.255.255.255.0.0.192.168.11.1: value=2 #
16.01.2020 12:06:09 (1717 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 #
16.01.2020 12:06:09 (1740 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 #
16.01.2020 12:06:09 (1763 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.8.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
16.01.2020 12:06:09 (1785 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 #
16.01.2020 12:06:09 (1812 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 #
16.01.2020 12:06:09 (1835 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.10.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
16.01.2020 12:06:09 (1857 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 #
16.01.2020 12:06:09 (1879 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 #
16.01.2020 12:06:09 (1900 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.11.192.168.11.0.255.255.255.0.0.192.168.11.1: value=0 #
16.01.2020 12:06:10 (1927 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 #
16.01.2020 12:06:10 (1951 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 #
16.01.2020 12:06:10 (1974 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.12.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
16.01.2020 12:06:10 (1997 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 #
16.01.2020 12:06:10 (2017 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 #
16.01.2020 12:06:10 (2044 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.13.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
16.01.2020 12:06:10 (2068 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 #
16.01.2020 12:06:10 (2091 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 #
16.01.2020 12:06:10 (2115 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.14.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
16.01.2020 12:06:10 (2138 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 #
16.01.2020 12:06:10 (2190 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 #
16.01.2020 12:06:10 (2210 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.15.192.168.11.0.255.255.255.0.0.192.168.11.1: value=4294967295 #
16.01.2020 12:06:10 (2239 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 #
16.01.2020 12:06:10 (2261 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 #
16.01.2020 12:06:10 (2285 ms) : SNMP Datatype: ASN_INTEGER
Test 1.3.6.1.2.1.4.24.4.1.16.192.168.11.0.255.255.255.0.0.192.168.11.1: value=1 #
I have already sent you supout-files. But I’ve never got an answer from you…
My wish, please fix this problem, It was introduces with V6.46.
Please provide the ticket number starting with “SUP-”. We are unable to reproduce the issue.
Try to update my RB4011 from routeros-arm-6.46.2.npk + user-manager-6.46.2-arm.npk = Error IPSEC can no longer login, downgrade back to 6.46.2
Anyone @Mikrotik working on that bug?
Same thing finally for the FANs.
On some devices, FAN speed always remains at a high level, making FAN monitoring based on their speed rather easy.
Though, on some other devices, FAN speed sometimes falls to 0 RPM, then increases to some thousands, then falls again to 0…
Making FAN speed monitoring on such devices rather impossible.
Could you then also add a fan-state OID among the new health gauges ?
Many thanks !
anyone can explain what exactly improve on this
*) system - correctly handle Generic Receive Offloading (GRO) for MPLS traffic;
i 'am having ping rapid random timeout on vpls, hope the improvement can fix the problem.
thx
Version 6.47beta32 has been released.
Before an upgrade:
- Remember to make backup/export files before an upgrade and save them on another storage device;
- Make sure the device will not lose power during upgrade process;
- Device has enough free storage space for all RouterOS packages to be downloaded.
What’s new in 6.47beta32 (2020-Feb-10 11:45):
**Important note!!!
\
- The Dude server must be updated to monitor v6.47beta30+ RouterOS type devices.
- The Dude client must be manually upgraded after upgrading The Dude server.
- Make sure LTE APN Profile name does not match any of the DHCP server’s names if LTE passthrough is used.
MAJOR CHANGES IN v6.47:
!) socks - added support for SOCKS5 (RFC 1928);
----------------------**
Changes in this release:
*) arm - improved watchdog and kernel panic reporting in log after reboots on RB3011 and IPQ4018/IPQ4019 devices (“/system routerboard upgrade” required);
*) branding - allow forcing configuration script as default configuration (new branding packet required);
*) branding - fixed “company-url” and “router-default-name” survival after system upgrade;
*) branding - fixed WEB HTML page survival after system upgrade;
*) certificate - fixed certificate verification when flushing CRL’s;
*) crs3xx - correctly remove switch rules on CRS317-1G-16S+ and CRS309-1G-8S+ devices;
*) crs3xx - fixed QSFP+ interface linking for CRS326-24S+2Q+ device (introduced in v6.47beta19);
*) crs3xx - improved switch host table updating;
*) defconf - added welcome note with common first steps for new users;
*) defconf - fixed default configuration initialization if power loss occurred during the process;
*) defconf - fixed “no-defaults=yes” applying default configuration (introduced in v6.47beta);
*) disk - improved recently created file survival after reboots;
*) dns - use only servers received from IKEv2 server when present;
*) dot1x - added hex value support for RADIUS switch rules;
*) dot1x - added range “dst-port” support for RADIUS switch rules;
*) dot1x - added support for lower case “mac-auth” RADIUS formats;
*) dot1x - fixed dynamically created switch rule removal when client disconnects;
*) dot1x - fixed port blocking when interface changes state from disabled to enabled;
*) dot1x - fixed “reject-vlan-id” value range;
*) dot1x - improved debug logging output to “dot1x” topic;
*) dot1x - improved value validation for dynamically created switch rules;
*) dude - updated The Dude to use new style authentication method;
*) ike1 - added support for “UNITY_DEF_DOMAIN” and “UNITY_SPLITDNS_NAME” payload attributes;
*) ike2 - added support for “INTERNAL_DNS_DOMAIN” payload attribute;
*) ike2 - fixed DHCP Inform package handling when received on PPPoE interface;
*) ipsec - added “split-dns” parameter support for mode configuration (CLI only);
*) ipsec - fixed minor spelling mistake in logs;
*) ipsec - improved IPsec service stability when receiving bogus packets;
*) lte - added interface name prefix for logging events;
*) lte - added “phy-cellid” value support for LTE-US;
*) lte - added support for multiple passthrough APN configuration;
*) lte - do not allow using empty APN Profile names;
*) lte - show “phy-cellid” value only in LTE mode;
*) quickset - removed “LTE band” setting from Quick Set;
*) quickset - show “Antenna Gain” setting on devices without built-in antennas;
*) quickset - use “station-wds” mode when connecting to AP with RouterOS flag;
*) routing - improved IGMP-Proxy service stability when receiving bogus packets;
*) snmp - fixed “routeros-version” value returning from registration table;
*) snmp - fixed UPS battery voltage value scaling;
*) supout - improved UPS information reporting;
*) telnet - improved telnet compatibility with other client implementations;
*) tr069-client - removed warning log message when not using HTTPS;
*) traffic-flow - added “postDestinationMacAddress” parameter support for IPFIX and Netflow v9;
*) upgrade - fixed space handling in package file names;
*) ups - improved compatibility with APC Smart UPS 1000 and 1500;
*) user-manager - fixed signup enabling (introduced in v6.46);
*) w60g - improved stability after multiple disconnections;
*) webfig - added default configuration confirmation window to WebFig;
*) webfig - do not show WebFig menu when opening ‘Check For Updates’ in Quick Set;
*) winbox - added support for inline bar graphs for LTE signal values;
*) winbox - completely removed old style authentication method;
*) winbox - fixed “invalid” flag presence under “System/Certificates/CRL” menu;
*) wireless - improved compatibility for “ETSI” wireless country profile;
*) www - added “tls-version” parameter in “IP->Services” menu (CLI only);
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 expected or after crash.
What’s new in 6.47beta32 (2020-Feb-10 11:45):
Why did you remove the “antenna gain” line in Winbox for wireless??? To fix the ETSI not imposing the minimum. ???
Well I knew ETSI regulatory domain forgot to check the minimal antenna gain. Countries did impose the minimal gain.
As setting TX power is difficult with the few left over options, the method explained in this forum several times is to increase the antenna gain, to reduce the transmit power.
“All rates fixed” is no good as the radio cannot follow for the higher MCS encodings. And “manual” and “card rates” is not allowed.
The only other oprion is not to set the country (“no_country_set”) and go fully manual." What an improvement! Forget regulations, you are on your own now!"
Why did you remove the “antenna gain” line in Winbox ??? To fix the ETSI not imposing the minimum.? It was the only practical way to reduce the TX power, not to heat up the radio, and always be legal
It’s probably just a missed bug, you can still set the antenna gain from terminal. There’s no mention of it beeing removed in the changelog, no need to panic like that.
It’s under testing branch for a reason. Hold your horses.
I’m happy that this got fixed: *) ike2 - fixed DHCP Inform package handling when received on PPPoE interface;
BTW, shouldn’t that be packet instead of package?
As for “all rates fixed”, I’d like to see an additional mode setting where TX power for all rates is equal to the lowest value (for the highest rate) but set automatically (without need to specify any value). Why?
While it’s OK to distort the transmitted signal a little more at QPSK compared to 64QAM (or 256QAM for AC) and it will still be received correctly, any distortion (no matter what modulation is used) will increase noise outside the proper channel width. Perhaps it still fits the wide spectral mask, but we are more noisy than usually needed.
So this setting woud be effectively “be nice to nearby devices on adjacent channels”. You still gain RX sensitivity at lower modulations, but TX power would remain constant for less distortion.