Community discussions

MUM Europe 2020
 
User avatar
emils
MikroTik Support
MikroTik Support
Topic Author
Posts: 558
Joined: Thu Dec 11, 2014 8:53 am

v6.47beta [testing] is released!

Tue Dec 10, 2019 4:49 pm

Version 6.47beta8 has been released.

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.47beta8 (2019-Dec-10 10:33):

Changes in this release:

*) console - fixed "clear-history" restoring historic actions after power cycle;
*) console - removed "edit" and "set" actions from "System/History" menu;
*) crs3xx - fixed "ingress-rate" property on CRS309-1G-8S+, CRS312-4C+8XG, CRS326-24S+2Q+ devices;
*) defconf - fixed default configuration loading after fresh install (introduced in v6.46);
*) dhcpv6-client - improved error logging when when renewed address differs;
*) fetch - fixed "User-Agent" usage if provided by "http-header-field";
*) health - fixed health reporting on OmniTIK 5 PoE ac;
*) health - improved health reporting on CCR1072-1G-8S+;
*) ipsec - improved system stability when processing decrypted packet on unregistred interface;
*) l2tp - improved system stability when disconnecting many clients at once;
*) lora - improved confirmed downlink forwarding;
*) lte - do not reset modem when setting the same SIM slot on LtAP;
*) lte - fixed multiple APN reactivation after deactivation by operator;
*) lte - show SIM error when no card is present;
*) netinstall - removed "Flashfig" from Netinstall;
*) netinstall - removed "Make Floppy" from Netinstall;
*) netinstall - signed netinstall.exe with Digital Signature;
*) ppp - prioritize "remote-ipv6-prefix-pool" from PPP secret over PPP profile;
*) snmp - added "dot1qTpFdbTable" OID reporting for Q-BRIDGE-MIB;
*) snmp - fixed "dot1dBasePort" index offset for BRIDGE-MIB;
*) snmp - fixed health related OID polling (introduced in v6.46);
*) snmp - improved stability when polling MAC address related OID;
*) supout - fixed autosupout.rif file generation (introduced in v6.46);
*) w60g - use "arp" and "mtu" parameters from master interface when creating a new station;
*) winbox - added "auto-erase" option to "Tool/SMS" menu;
*) winbox - fixed "allowed-number" parameter setting invalid value in "Tool/SMS" menu;
*) winbox - show "LCD" menu only on boards that have LCD screen;
*) wireless - improved compatibility by adding default installation mode and gain for devices with integrated antennas;
*) wireless - improved compatibility for Switzerland wireless country profile to improve compliance with ETSI regulations;

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.
 
bnw
just joined
Posts: 20
Joined: Thu Jun 13, 2019 5:56 pm

Re: v6.47beta [testing] is released!

Tue Dec 10, 2019 4:53 pm

*) snmp - fixed health related OID polling (introduced in v6.46);
Could you elaborate please ?
Did not experience any SNMP heath issue with 6.46 yet.
Thank you !
 
bnw
just joined
Posts: 20
Joined: Thu Jun 13, 2019 5:56 pm

Re: v6.47beta [testing] is released!

Tue Dec 10, 2019 4:56 pm

viewtopic.php?f=2&t=116856#p741203
I opened #2019032822004818 a few months ago, many SNMP hardware OIDs are missing for the CCR1072, compared to what Winbox shows :
- Board temperature
- Board temparature 2
- Fan speed 3
- Fan speed 4
- PSU1 status (should be OID .15 (*))
- PSU2 status (should be OID .16 (*))
(*) as seen on other models such as the CRS317-1G-16S+.

We are then clearly at risk with our CCR1072-1G-8S+, not being able to monitor all their hardware components, which is a rather tricky situation for core devices.
And hope to see this in 6.47 finally !
Many thx !
 
User avatar
emils
MikroTik Support
MikroTik Support
Topic Author
Posts: 558
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.47beta [testing] is released!

Tue Dec 10, 2019 5:10 pm

bnw, should affect only a few CRS devices (CRS3xx).
 
anuser
Member
Member
Posts: 423
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.47beta [testing] is released!

Tue Dec 10, 2019 10:02 pm

Will we already get MU-MIMO support within 6.47beta release?
 
User avatar
strods
MikroTik Support
MikroTik Support
Posts: 1424
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.47beta [testing] is released!

Wed Dec 11, 2019 7:12 am

In v6.47beta there is a new menu added - "/system health gauges". You should use this for polling "Health" related data from all the RouterBOARDs.
 
joegoldman
Long time Member
Long time Member
Posts: 521
Joined: Mon May 27, 2013 2:05 am

Re: v6.47beta [testing] is released!

Wed Dec 11, 2019 8:59 am

In v6.47beta there is a new menu added - "/system health gauges". You should use this for polling "Health" related data from all the RouterBOARDs.
Does this come with new associated MIBs / OID's? Or more for polling via API?
 
bnw
just joined
Posts: 20
Joined: Thu Jun 13, 2019 5:56 pm

Re: v6.47beta [testing] is released!

Wed Dec 11, 2019 9:29 am

Interesting. And if available through SNMP, will these "gauges" give the PSUs status (which are for now missing on CCR1072 as stated above) ?
 
ivicask
Member Candidate
Member Candidate
Posts: 249
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v6.47beta [testing] is released!

Wed Dec 11, 2019 11:22 am

When is ROMON getting fixed?I need some other fixes from new betas, but they also break ROMON..
 
mistry7
Forum Guru
Forum Guru
Posts: 1383
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: v6.47beta [testing] is released!

Wed Dec 11, 2019 11:26 am

Will we already get MU-MIMO support within 6.47beta release?
shure on xmas, but you don't will get any year....
 
User avatar
strods
MikroTik Support
MikroTik Support
Posts: 1424
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.47beta [testing] is released!

Wed Dec 11, 2019 12:37 pm

ivicask - Have you reported this problem to support@mikrotik.com or https://help.mikrotik.com/servicedesk/c ... on=portals ?? We are not aware of any RoMON problems;
 
CoMMyz
newbie
Posts: 26
Joined: Fri Dec 04, 2015 10:56 pm

Re: v6.47beta [testing] is released!

Wed Dec 11, 2019 7:09 pm

*) netinstall - removed "Flashfig" from Netinstall;

Can you please elaborate? Is this feature removed completely or just moving to a standalone executable ?
 
kmrue
just joined
Posts: 10
Joined: Mon Aug 05, 2019 10:53 am

Re: v6.47beta [testing] is released!

Sat Dec 14, 2019 7:26 pm

as no UPS-bugfixing is listed I tested anyhow:
UPS still not working with APC SMT750I, SMT1000I, SMT1500I (to name just 3 models). All of them connected via their USB-port. They all get identified, but only a few parameters get transferred to the routerboard. Tested using CRS125.

Is there anything you guys @ mikrotik want me to further check out?
 
ivicask
Member Candidate
Member Candidate
Posts: 249
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v6.47beta [testing] is released!

Sat Dec 14, 2019 9:08 pm

ivicask - Have you reported this problem to support@mikrotik.com or https://help.mikrotik.com/servicedesk/c ... on=portals ?? We are not aware of any RoMON problems;
But some of your support confirmed it here, post #5
viewtopic.php?f=21&t=154286&p=762462#p762468
 
Guscht
just joined
Posts: 7
Joined: Thu Jul 01, 2010 5:32 pm

Re: v6.47beta [testing] is released!

Sun Dec 15, 2019 12:43 am

Hoped the snmp-IP-Forward MIB is fixed as well.

We get still a "no such object" error with 6.47beta8:
Testing OIDs...
14.12.2019 23:31:27 (98726 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=3 #
14.12.2019 23:31:28 (99944 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) #
14.12.2019 23:31:30 (101377 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) #
14.12.2019 23:31:31 (102658 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) #
14.12.2019 23:31:32 (103789 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) #
14.12.2019 23:31:33 (104495 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) #
14.12.2019 23:31:33 (105034 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) #
14.12.2019 23:31:35 (106269 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) #
14.12.2019 23:31:36 (107475 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) #
14.12.2019 23:31:37 (108783 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) #
14.12.2019 23:31:39 (110254 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) #
14.12.2019 23:31:40 (111267 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) #
14.12.2019 23:31:40 (111839 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) #
14.12.2019 23:31:41 (112396 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) #
14.12.2019 23:31:42 (113092 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) #
14.12.2019 23:31:42 (113881 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) #
14.12.2019 23:31:43 (114760 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) #
14.12.2019 23:31:44 (115728 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) #
14.12.2019 23:31:45 (116158 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) #
14.12.2019 23:31:45 (116616 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) #
14.12.2019 23:31:46 (117546 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) #
14.12.2019 23:31:47 (118558 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) #
14.12.2019 23:31:48 (119709 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) #
14.12.2019 23:31:50 (121071 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) #
14.12.2019 23:31:51 (122398 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) #
14.12.2019 23:31:52 (123440 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) #
14.12.2019 23:31:53 (124483 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) #
14.12.2019 23:31:54 (125600 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) #
14.12.2019 23:31:55 (126839 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) #
14.12.2019 23:31:56 (127828 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) #
14.12.2019 23:31:58 (129141 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) #
14.12.2019 23:31:58 (129730 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) #
14.12.2019 23:31:59 (130054 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) #
14.12.2019 23:31:59 (130798 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) #
14.12.2019 23:32:00 (131935 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) #
14.12.2019 23:32:01 (132994 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) #
14.12.2019 23:32:03 (134092 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) #
14.12.2019 23:32:04 (135693 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) #
14.12.2019 23:32:05 (136548 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) #
14.12.2019 23:32:06 (137167 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) #
14.12.2019 23:32:06 (137965 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) #
14.12.2019 23:32:07 (138930 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) #
14.12.2019 23:32:09 (140092 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) #
14.12.2019 23:32:10 (141385 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) #
14.12.2019 23:32:11 (142697 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) #
14.12.2019 23:32:13 (144062 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) #
With 6.45.7 (or less) a good result:
Testing OIDs...
14.12.2019 23:34:53 (6895 ms) : SNMP Datatype: ASN_UNSIGNED
Test 1.3.6.1.2.1.4.24.3.0: value=3 #
14.12.2019 23:34:53 (7012 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 #
14.12.2019 23:34:53 (7128 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 #
14.12.2019 23:34:53 (7245 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 #
14.12.2019 23:34:53 (7361 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 #
14.12.2019 23:34:53 (7620 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 #
14.12.2019 23:34:54 (7937 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 #
14.12.2019 23:34:54 (8054 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 #
14.12.2019 23:34:54 (8172 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 #
14.12.2019 23:34:54 (8288 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 #
14.12.2019 23:34:54 (8447 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 #
14.12.2019 23:34:55 (8753 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 #
14.12.2019 23:34:55 (8878 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 #
14.12.2019 23:34:55 (8997 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 #
14.12.2019 23:34:55 (9161 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 #
14.12.2019 23:34:55 (9375 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 #
14.12.2019 23:34:55 (9626 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 #
14.12.2019 23:34:56 (9831 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 #
14.12.2019 23:34:56 (9979 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 #
14.12.2019 23:34:56 (10094 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 #
14.12.2019 23:34:56 (10210 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 #
14.12.2019 23:34:56 (10325 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 #
14.12.2019 23:34:56 (10581 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 #
14.12.2019 23:34:57 (10794 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 #
14.12.2019 23:34:57 (10907 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 #
14.12.2019 23:34:57 (11043 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 #
14.12.2019 23:34:57 (11156 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 #
14.12.2019 23:34:57 (11270 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 #
14.12.2019 23:34:57 (11384 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 #
14.12.2019 23:34:57 (11617 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 #
14.12.2019 23:34:58 (11814 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 #
14.12.2019 23:34:58 (11918 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 #
14.12.2019 23:34:58 (12132 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 #
14.12.2019 23:34:58 (12236 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 #
14.12.2019 23:34:58 (12342 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 #
14.12.2019 23:34:58 (12587 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 #
14.12.2019 23:34:59 (12785 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 #
14.12.2019 23:34:59 (12889 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 #
14.12.2019 23:34:59 (12999 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 #
14.12.2019 23:34:59 (13103 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 #
14.12.2019 23:34:59 (13208 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 #
14.12.2019 23:34:59 (13312 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 #
14.12.2019 23:34:59 (13458 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 #
14.12.2019 23:35:00 (13755 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 #
14.12.2019 23:35:00 (13992 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 #
14.12.2019 23:35:00 (14193 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 #
 
User avatar
emils
MikroTik Support
MikroTik Support
Topic Author
Posts: 558
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.47beta [testing] is released!

Mon Dec 16, 2019 9:01 am

Guscht You need to send supout.rif file to support@mikrotik.com and brief problem description. We are currently unable to reproduce such issue.

ivicask
Have you tried the 6.46 stable and 6.47 testing versions? RoMoN works for me now. Make sure both the end user and the agent is updated. If it is not working in the latest versions, please open a support ticket with supout.rif file from your routers.
 
Guscht
just joined
Posts: 7
Joined: Thu Jul 01, 2010 5:32 pm

Re: v6.47beta [testing] is released!

Mon Dec 16, 2019 2:28 pm

Hi,

I did this already when V6.46 was released, but I got no response from you...

Try the SNMP-Tester (https://downloads.paessler.com/tools/SN ... +5.2.3.zip) from PRTG.
The OID-LIB (IP-FORWARD.MIB) is attached.

Then simply run the OID-LIB against a RouterOS device with ROS V6.46 or greater. It will fail in the way I posted I above (SNMP Error 222).
ROS V6.45.7 (or lower) report valid data back.
hc_001.jpg
You do not have the required permissions to view the files attached to this post.
 
bnw
just joined
Posts: 20
Joined: Thu Jun 13, 2019 5:56 pm

Re: v6.47beta [testing] is released!

Mon Dec 16, 2019 2:54 pm

viewtopic.php?f=2&t=116856#p741203
I opened #2019032822004818 a few months ago, many SNMP hardware OIDs are missing for the CCR1072, compared to what Winbox shows

In v6.47beta there is a new menu added - "/system health gauges". You should use this for polling "Health" related data from all the RouterBOARDs.

Does this come with new associated MIBs / OID's? Or more for polling via API?

Interesting. And if available through SNMP, will these "gauges" give the PSUs status (which are for now missing on CCR1072 as stated above) ?

Good news, here is what we now have (as of 6.47b8) for the CCR1072 :
$ snmpwalk ... .1.3.6.1.4.1.14988.1.1.3
.1.3.6.1.4.1.14988.1.1.3.9.0 = STRING: "n/a"
.1.3.6.1.4.1.14988.1.1.3.11.0 = INTEGER: 370
.1.3.6.1.4.1.14988.1.1.3.12.0 = INTEGER: 435
.1.3.6.1.4.1.14988.1.1.3.14.0 = INTEGER: 1000
.1.3.6.1.4.1.14988.1.1.3.17.0 = Gauge32: 4169
.1.3.6.1.4.1.14988.1.1.3.18.0 = Gauge32: 4182
.1.3.6.1.4.1.14988.1.1.3.100.1.16 = STRING: "power-consumption"
.1.3.6.1.4.1.14988.1.1.3.100.1.17 = STRING: "cpu-temperature"
.1.3.6.1.4.1.14988.1.1.3.100.1.7001 = STRING: "fan1-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7002 = STRING: "fan2-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7003 = STRING: "fan3-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7004 = STRING: "fan4-speed"
.1.3.6.1.4.1.14988.1.1.3.100.1.7101 = STRING: "board-temperature1"
.1.3.6.1.4.1.14988.1.1.3.100.1.7102 = STRING: "board-temperature2"
.1.3.6.1.4.1.14988.1.1.3.100.1.7201 = STRING: "psu1-voltage"
.1.3.6.1.4.1.14988.1.1.3.100.1.7202 = STRING: "psu2-voltage"
.1.3.6.1.4.1.14988.1.1.3.100.1.7301 = STRING: "psu1-current"
.1.3.6.1.4.1.14988.1.1.3.100.1.7302 = STRING: "psu2-current"
.1.3.6.1.4.1.14988.1.1.3.100.2.16 = Gauge32: 435
.1.3.6.1.4.1.14988.1.1.3.100.2.17 = Gauge32: 37
.1.3.6.1.4.1.14988.1.1.3.100.2.7001 = Gauge32: 4169
.1.3.6.1.4.1.14988.1.1.3.100.2.7002 = Gauge32: 4182
.1.3.6.1.4.1.14988.1.1.3.100.2.7003 = Gauge32: 4182
.1.3.6.1.4.1.14988.1.1.3.100.2.7004 = Gauge32: 4222
.1.3.6.1.4.1.14988.1.1.3.100.2.7101 = Gauge32: 25
.1.3.6.1.4.1.14988.1.1.3.100.2.7102 = Gauge32: 25
.1.3.6.1.4.1.14988.1.1.3.100.2.7201 = Gauge32: 0
.1.3.6.1.4.1.14988.1.1.3.100.2.7202 = Gauge32: 121
.1.3.6.1.4.1.14988.1.1.3.100.2.7301 = Gauge32: 0
.1.3.6.1.4.1.14988.1.1.3.100.2.7302 = Gauge32: 36
.1.3.6.1.4.1.14988.1.1.3.100.3.16 = INTEGER: 5
.1.3.6.1.4.1.14988.1.1.3.100.3.17 = INTEGER: 1
.1.3.6.1.4.1.14988.1.1.3.100.3.7001 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7002 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7003 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7004 = INTEGER: 2
.1.3.6.1.4.1.14988.1.1.3.100.3.7101 = INTEGER: 1
.1.3.6.1.4.1.14988.1.1.3.100.3.7102 = INTEGER: 1
.1.3.6.1.4.1.14988.1.1.3.100.3.7201 = INTEGER: 3
.1.3.6.1.4.1.14988.1.1.3.100.3.7202 = INTEGER: 3
.1.3.6.1.4.1.14988.1.1.3.100.3.7301 = INTEGER: 4
.1.3.6.1.4.1.14988.1.1.3.100.3.7302 = INTEGER: 4

.1.3.6.1.4.1.14988.1.1.3.100 is the new interesting part, the gauges.

Same new gauges on a RB4011 :
$ snmpwalk ... .1.3.6.1.4.1.14988.1.1.3
.1.3.6.1.4.1.14988.1.1.3.9.0 = STRING: "n/a"
.1.3.6.1.4.1.14988.1.1.3.10.0 = INTEGER: 270
.1.3.6.1.4.1.14988.1.1.3.14.0 = INTEGER: 1400
.1.3.6.1.4.1.14988.1.1.3.100.1.13 = STRING: "voltage"
.1.3.6.1.4.1.14988.1.1.3.100.1.14 = STRING: "temperature"
.1.3.6.1.4.1.14988.1.1.3.100.2.13 = Gauge32: 238
.1.3.6.1.4.1.14988.1.1.3.100.2.14 = Gauge32: 27
.1.3.6.1.4.1.14988.1.1.3.100.3.13 = INTEGER: 3
.1.3.6.1.4.1.14988.1.1.3.100.3.14 = INTEGER: 1

We'll now be able to properly monitor CCR1072 8)
Many thanks MikroTik for this !
 
bnw
just joined
Posts: 20
Joined: Thu Jun 13, 2019 5:56 pm

Re: v6.47beta [testing] is released!

Mon Dec 16, 2019 4:12 pm

One thing perhaps following my post above.
We have the PSUs' voltage and current in these new gauges.
We could then monitor PSUs checking for example that voltage >12.
Will you however add a psu-state OID ?

Could you also provide us with the new MIB containing these gauges' part please ?

Thank you again !
 
mducharme
Trainer
Trainer
Posts: 890
Joined: Tue Jul 19, 2016 6:45 pm

Re: v6.47beta [testing] is released!

Thu Dec 19, 2019 7:48 am

I am curious - how many more 6.4x versions are expected given that 7 is now in beta? Is 6.47 or 6.48 possibly the last RouterOS 6.x? Or will there be a longer period of overlap while 7.x is released and 6.x is still being developed?
 
ivicask
Member Candidate
Member Candidate
Posts: 249
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v6.47beta [testing] is released!

Thu Dec 19, 2019 1:18 pm

Guscht You need to send supout.rif file to support@mikrotik.com and brief problem description. We are currently unable to reproduce such issue.

ivicask
Have you tried the 6.46 stable and 6.47 testing versions? RoMoN works for me now. Make sure both the end user and the agent is updated. If it is not working in the latest versions, please open a support ticket with supout.rif file from your routers.
Installed 6.47beta8 and works fine now, thanks!
 
User avatar
Maggiore81
Member Candidate
Member Candidate
Posts: 242
Joined: Sun Apr 15, 2012 12:10 pm
Location: Italy
Contact:

Re: v6.47beta [testing] is released!

Fri Dec 27, 2019 9:08 am

I am curious - how many more 6.4x versions are expected given that 7 is now in beta? Is 6.47 or 6.48 possibly the last RouterOS 6.x? Or will there be a longer period of overlap while 7.x is released and 6.x is still being developed?
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.
Dott. Elia Spadoni
---
Network Administrator,
MTCNA, MTCRE, MTCTCE, MTCINE, MTCWE
Spadhausen Internet Provider
Ravenna, ITALY
http://www.spadhausen.com
 
User avatar
JohnTRIVOLTA
Member Candidate
Member Candidate
Posts: 213
Joined: Sun Dec 25, 2016 2:05 pm
Location: BG/Sofia

Re: v6.47beta [testing] is released!

Mon Dec 30, 2019 10:23 am

I moved the question in ros v7.0beta4 topic !
 
User avatar
eworm
Member
Member
Posts: 463
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.47beta [testing] is released!

Mon Jan 06, 2020 10:20 pm

In v6.47beta there is a new menu added - "/system health gauges". You should use this for polling "Health" related data from all the RouterBOARDs.
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!
Manage RouterOS scripts and extend your devices' functionality: RouterOS Scripts
 
User avatar
emils
MikroTik Support
MikroTik Support
Topic Author
Posts: 558
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.47beta [testing] is released!

Mon Jan 13, 2020 3:34 pm

Version 6.47beta19 has been released.

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.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.
 
guipoletto
Member Candidate
Member Candidate
Posts: 102
Joined: Mon Sep 19, 2011 5:31 am

Re: v6.47beta [testing] is released!

Mon Jan 13, 2020 4:52 pm

!) socks - added support for SOCKS5 (RFC 1928);
Well, it's january, and it's christmas again! S2
 
User avatar
SiB
Member
Member
Posts: 442
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v6.47beta [testing] is released!

Mon Jan 13, 2020 5:25 pm

*) 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;
DY33IxHn0r.png
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.
winbox_v3.20_64_1dJ4785PvW.png
from PC
Wireshark_wXmDbBOpfV.png
You do not have the required permissions to view the files attached to this post.
MTCNA + MTCRE + MTCINE | ~600 users at ~150 RouterBoards in EMEA | Telegram: @SiB_PL
WinBox Tip: F6 works as ALT+TAB | Gliffy.com - free network schematic | prnt.sc - free ScreenShot software
I will be at MUMEUROPE Prague on 26-27 march 2020
 
irghost
Member Candidate
Member Candidate
Posts: 283
Joined: Sun Feb 21, 2016 1:49 pm

Re: v6.47beta [testing] is released!

Tue Jan 14, 2020 1:23 pm

Version 6.47beta19 has been released.

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.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.
Socks5 with radius auth? maybe?
MTCNA MTCRE MTCTCE MTCUME MTCWE MTCIPv6E MTCINE
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 1763
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: v6.47beta [testing] is released!

Tue Jan 14, 2020 3:18 pm

@irqhost: why do you quoute whole post? Isn't it enough just to ask a question in this thread?
Real admins use real keyboards.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 1316
Joined: Sat Dec 24, 2016 11:17 am
Location: jo.overland at gmail.com

Re: v6.47beta [testing] is released!

Tue Jan 14, 2020 8:47 pm

Many does not see det big red post button at the bottom of the page ;)
 
How to use Splunk to monitor your MikroTik Router

MikroTik->Splunk
 
 
Guscht
just joined
Posts: 7
Joined: Thu Jul 01, 2010 5:32 pm

Re: v6.47beta [testing] is released!

Thu Jan 16, 2020 1:09 pm

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.
 
User avatar
emils
MikroTik Support
MikroTik Support
Topic Author
Posts: 558
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.47beta [testing] is released!

Thu Jan 16, 2020 1:39 pm

Please provide the ticket number starting with "SUP-". We are unable to reproduce the issue.
 
Michel
just joined
Posts: 22
Joined: Mon Aug 16, 2010 12:50 pm

Re: v6.47beta [testing] is released!

Thu Jan 16, 2020 7:22 pm

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
 
kmrue
just joined
Posts: 10
Joined: Mon Aug 05, 2019 10:53 am

Re: v6.47beta [testing] is released!

Mon Jan 27, 2020 7:35 pm

as no UPS-bugfixing is listed I tested anyhow:
UPS still not working with APC SMT750I, SMT1000I, SMT1500I (to name just 3 models). All of them connected via their USB-port. They all get identified, but only a few parameters get transferred to the routerboard. Tested using CRS125.

Is there anything you guys @ mikrotik want me to further check out?
Anyone @Mikrotik working on that bug?
 
bnw
just joined
Posts: 20
Joined: Thu Jun 13, 2019 5:56 pm

Re: v6.47beta [testing] is released!

Tue Jan 28, 2020 1:14 am

One thing perhaps following my post above.
We have the PSUs' voltage and current in these new gauges.
We could then monitor PSUs checking for example that voltage >12.
Will you however add a psu-state OID ?
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 !
 
buset1974
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Wed Sep 13, 2006 12:12 pm
Location: Jakarta

Re: v6.47beta [testing] is released!

Sat Feb 08, 2020 5:52 pm

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
 
User avatar
emils
MikroTik Support
MikroTik Support
Topic Author
Posts: 558
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.47beta [testing] is released!

Mon Feb 10, 2020 4:11 pm

Version 6.47beta32 has been released.

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.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.
 
User avatar
bpwl
Member Candidate
Member Candidate
Posts: 151
Joined: Mon Apr 08, 2019 1:16 am

Re: v6.47beta [testing] is released!

Mon Feb 10, 2020 6:32 pm

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
 
Znevna
Frequent Visitor
Frequent Visitor
Posts: 70
Joined: Mon Sep 23, 2019 1:04 pm

Re: v6.47beta [testing] is released!

Mon Feb 10, 2020 11:14 pm

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?
 
marekm
Member Candidate
Member Candidate
Posts: 219
Joined: Tue Feb 01, 2011 11:27 pm

Re: v6.47beta [testing] is released!

Mon Feb 10, 2020 11:55 pm

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.
 
User avatar
bpwl
Member Candidate
Member Candidate
Posts: 151
Joined: Mon Apr 08, 2019 1:16 am

Re: v6.47beta [testing] is released!

Tue Feb 11, 2020 12:49 am

@Znevna: I know it's test track only. But once a developper sets for a solution (no antenna gain check needed anymore) , they may stick to that.

It's a pain now to set the country, if you don't fill in the antenna gain before entering APPLY.,
Set the gain via "terminal" to a low value, and then let somebody set the country via WinBox or Webfig.

Same with the choice for the SXTsq ac 5, to only allow "outdoor" frequencies. I want to use it indoor ... but are limited to outdoor frequencies.
We know that the "outdoor" setting exists because it is more restrictive than "indoors". (You are not allowed to disturb the ether outdoors.)
 
Extrems
just joined
Posts: 2
Joined: Tue Sep 11, 2018 8:09 pm
Location: Quebec, Canada
Contact:

Re: v6.47beta [testing] is released!

Tue Feb 11, 2020 1:12 am

*) dns - use only servers received from IKEv2 server when present;
This might sound strange, but I need to not use the servers received.
 
User avatar
SiB
Member
Member
Posts: 442
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v6.47beta [testing] is released!

Tue Feb 11, 2020 2:39 am

@emils
Version 6.47beta32
*) winbox - added support for inline bar graphs for LTE signal values;
Where are that inline bar graphs? I cannot found it. This will be a new feature?

Then please fix the LED display who give us info in WinBox about modem-signal-treshold=-93 who in only CLI give info that WinBox give fake information, CLI:
Ci6fF9RgSS.png
You do not have the required permissions to view the files attached to this post.
MTCNA + MTCRE + MTCINE | ~600 users at ~150 RouterBoards in EMEA | Telegram: @SiB_PL
WinBox Tip: F6 works as ALT+TAB | Gliffy.com - free network schematic | prnt.sc - free ScreenShot software
I will be at MUMEUROPE Prague on 26-27 march 2020
 
rooted
just joined
Posts: 22
Joined: Tue Feb 04, 2020 5:58 pm

Re: v6.47beta [testing] is released!

Tue Feb 11, 2020 4:52 am

Shouldn't that be "threshold"?
 
raffav
Member
Member
Posts: 303
Joined: Wed Oct 24, 2012 4:40 am

Re: v6.47beta [testing] is released!

Tue Feb 11, 2020 9:23 am

I had to netinstall my cap ac when I applied this version, lost completely access to it just user id and power led was on
After that caps and capsman don't act normally
I woke up today my 2g were down
I had to reboot twice one i got a msg telling that regulatory domain mismatch in cap (since when in capsman mode its care about setting in wireless interface?)
After changing to match
Interface did not come up as manager although the 5 g was showing managed by capsman was not working.. I had to reboot for 2 time

Sent from my Moto Z3 Play using Tapatalk

 
msatter
Forum Guru
Forum Guru
Posts: 1378
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v6.47beta [testing] is released!

Tue Feb 11, 2020 12:25 pm

Any chance that dynamic DNS servers in IKEv2 can be deactivated? I have a long list to which not should be connected (NordVPN). Putting a ICMP reject (output) on it helps a bit but rather I have them ignored if the user wants that. Like as it possible in L2TP/IPSEC.

Update:

GRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR

Updated my inner router also from 6.46beta68 to this beta and the DNS completely stopped working. It refuses to use my local DNS Server and only wants to use the dynamic DNS Servers. I can only block that by putting in filter the following rule:
add action=reject chain=output comment="Rejecting request made by the router itself, if not to the local DNS server" dst-address=!192.168.88.2 dst-port=53 log-prefix="DNS unreach" protocol=udp reject-with=icmp-admin-prohibited src-address=192.168.88.1

I had to revert to the previous beta to be able to post here.
*) dns - use only servers received from IKEv2 server when present;
Is this the cause that using NordVPN is not working anymore in this Beta if using a local DNS?
Two RB760iGS (hEX S) in series. One does PPPoE and both do IKEv2.
Running:
RouterOS 6.46.x / Winbox 3.21 / MikroTik APP 1.3.10
Android device owners, use https://github.com/M66B/NetGuard/releases (no root required)
 
msatter
Forum Guru
Forum Guru
Posts: 1378
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v6.47beta [testing] is released!

Tue Feb 11, 2020 4:38 pm

It is no fun looking at and being forced to use that list of dynamic servers while not wanting to use them. I want to use my Pihole at 192.168.88.2

DNSdyn.JPG
You do not have the required permissions to view the files attached to this post.
Two RB760iGS (hEX S) in series. One does PPPoE and both do IKEv2.
Running:
RouterOS 6.46.x / Winbox 3.21 / MikroTik APP 1.3.10
Android device owners, use https://github.com/M66B/NetGuard/releases (no root required)
 
User avatar
eworm
Member
Member
Posts: 463
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.47beta [testing] is released!

Thu Feb 13, 2020 4:42 pm

*) dns - use only servers received from IKEv2 server when present;
IMHO that's a bad change. I have an open wifi network for guests, client traffic is routed via IKEv2 provider. I do not necessarily trust this provider - I just want to hide my public IP address for unknown clients.
Traffic from known clients and router itself goes via ISP, the same should be true for DNS traffic.

I understand the idea for that change, but sending all DNS traffic to a VPN provider without the data itself does not improve the privacy or security situation. More the contrary.

Any chance to have a setting for IKEv2 peer (or mode-config or whatever...) named "use-dns" with three valid values: yes, no and exclusively?
Manage RouterOS scripts and extend your devices' functionality: RouterOS Scripts
 
kmrue
just joined
Posts: 10
Joined: Mon Aug 05, 2019 10:53 am

Re: v6.47beta [testing] is released!

Thu Feb 13, 2020 6:09 pm

The release notes on 6.47beta32 states
*) ups - improved compatibility with APC Smart UPS 1000 and 1500;

However I can not confirm on that one. There seems to be absolutely no change in behaviour compared to the previous beta.

Tab General:
all fine (to my understanding, those are internal anyhow and not UPS-protocol dependant=
Alarm Setting: does not have any effect even if set to immediate

Tab Model:
Model: Fine and complete
Version: no information
Serial Number: Fine
Manufacture Date: Fine
Nominal Battery Voltage: No Information

Tab Status:
Transfer Case: no information
Run Time Left: FINE
Offline After: FINE
Battery Charge: FINE
Battery voltage: no information
Line Voltage: no information
Output Voltage: no information
Load: no information
Temperature: no information
Frequency: no information

ON Line Checkbox: Fine
On Battery Checkbox: no information
All other Checkboxes: not tested

Tests performed on a SMART UPS 1000 FW UPS 09.4 / ID=18
and with a Smart-UPS 1500 FW:COM 02.1 / UPS.05.I

both with same readings. AFAIR this new beta version - which was supposed to be IMPROVED - does not make any change at all to the previous beta.

Furthermore: UPS only gets identified upon boot (so somehow the syncing of the UPS to the RB does not seem to be easy)

Once more my offer @mikrotik that I am willing to test even intermediate versions of the UPS-npk
Last edited by kmrue on Thu Feb 13, 2020 6:12 pm, edited 1 time in total.
 
msatter
Forum Guru
Forum Guru
Posts: 1378
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v6.47beta [testing] is released!

Thu Feb 13, 2020 6:12 pm

I like to add to make to naming more clear like "Use Peer DNS" as it is used else where in ROS.

By exclusively do you mean that the dynamic DNS is resolving only for that link? Not going into the pool of Dynamic DNS servers under IP-DNS.
Two RB760iGS (hEX S) in series. One does PPPoE and both do IKEv2.
Running:
RouterOS 6.46.x / Winbox 3.21 / MikroTik APP 1.3.10
Android device owners, use https://github.com/M66B/NetGuard/releases (no root required)
 
User avatar
osc86
Frequent Visitor
Frequent Visitor
Posts: 64
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.47beta [testing] is released!

Thu Feb 13, 2020 6:22 pm

Please give us the option, to not use any dynamic servers at all, no matter what the source is.
I don't want to use any kind of dynamic dns servers, for obvious reasons.
Who is using the dns servers the vpn/isp provides anyway..
CCR1009-7G-1C-1S+ ROS6.45.7
 
msatter
Forum Guru
Forum Guru
Posts: 1378
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v6.47beta [testing] is released!

Thu Feb 13, 2020 6:59 pm

Using the dnsservers from the VPN providers is wished for and so you avoid leaking DNS data.

However if you have your own server you want to 'leak' to your own server. This is for advanced users and the default setting should be, using the dynamic servers.
Two RB760iGS (hEX S) in series. One does PPPoE and both do IKEv2.
Running:
RouterOS 6.46.x / Winbox 3.21 / MikroTik APP 1.3.10
Android device owners, use https://github.com/M66B/NetGuard/releases (no root required)
 
ingus16
just joined
Posts: 21
Joined: Sun Jan 27, 2013 11:44 am

Re: v6.47beta [testing] is released!

Sun Feb 16, 2020 6:06 pm

6.47 beta 32
dns - use only servers received from IKEv2 server when present;

With this "fix" no i am not able to use local pihole +dnscrypt server because ike ipsec receive their vpn dns servers and mikrotik use only ike dns servers even despite dstnat override rule
 
User avatar
Xymox
Member
Member
Posts: 388
Joined: Thu Jan 21, 2010 5:04 pm
Location: Phoenix, Arizona US
Contact:

Re: v6.47beta [testing] is released!

Sun Feb 16, 2020 6:44 pm

*) bonding - improved slave interface MAC address handling;
*) bonding - prefer primary slave MAC address for bonding interface;

Hmmmmm... Im seeing a weird issue with 6.47

I have a LAG Bonded interface to my cable modem. 802.3ad . Yes the cable modem supports this. This works perfect on 6.46 It strangely fails on the beta. Im running DHCP-Client and NAT and using firewall rules that use rules based on a interface list item WAN which is the bonded interface.

Im not smart enough to troubleshoot what goes wrong, but, when I upgrade firmware on the CCR to 47 I loose connection to the outside world. I don't see where its getting lost either. Im not smart enough to follow a packet thru the router to isolate where it gets lost.

DHCP-Client is talking to the cable modem and does get a IP.

I can regain the connection by removing the bonded interface and putting it back.

Because there was a change to bonding behavior in 6.47 I thought I should report this weird issue I am seeing. Should I send a support email ?

I have 6.46.3 and the beta on partitions and can swap around easily. So I copy 6.46.3 and save config to a partition, activate that partition, upgrade firmware on it to 6.47x, and it 100% fails every time. Swap back to 6.46.3 works fine. Swap back to 6.47x and remove/readd bonding interface and it works..

I might also be seeing the issue come back over time even after I get it working. I am monitoring that.

This fixes the issue after upgrade:
/interface bonding remove Modem1;
/interface bonding add name=Modem1 mode=802.3ad slaves=ether7,ether8 transmit-hash-policy=layer-3-and-4;
/ip dhcp-client set 0 interface=Modem1;
/interface list member add interface=Modem1 list=WAN;
 
Rudolfs
MikroTik Support
MikroTik Support
Posts: 9
Joined: Fri Jun 01, 2018 8:57 am

Re: v6.47beta [testing] is released!

Mon Feb 17, 2020 1:01 pm

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
Hello,
This line was removed from Winbox GUI only for wireless devices with built-in antennas, due to the fact that changing this setting did not affect the performance in any way. Please note that RouterOS CLI shows all of the available options (not only the ones that can be used on the router). For example, if you type band=<tab> on router with 2 GHz wireless, you will be able to see also 5 GHz bands.
 
User avatar
bpwl
Member Candidate
Member Candidate
Posts: 151
Joined: Mon Apr 08, 2019 1:16 am

Re: v6.47beta [testing] is released!

Mon Feb 17, 2020 3:50 pm

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
Hello,
This line was removed from Winbox GUI only for wireless devices with built-in antennas, due to the fact that changing this setting did not affect the performance in any way. Please note that RouterOS CLI shows all of the available options (not only the ones that can be used on the router). For example, if you type band=<tab> on router with 2 GHz wireless, you will be able to see also 5 GHz bands.
Can you please tell us then how to reduce the TX power, like all experts in Wifi give as advice, on those devices using the GUI. Most settings don't work at all or you will cut off things that you didn't want (e.g. all fixed). Changing the antenna gain was many times reported on this forum as the easiest , safest and the better method, to be some defined value below the legal and the device technical limits. I'm one of the persons that repeated this solution to others.
For other explicit methods you have to look up the data-sheets to know what the device limlits are.
Of course you can go to the CLI. You can always go to the CLI for non-trivial, special, expert and exceptional settings. And we are "blind" anyway , as the "current TX powers" is not filled in. Or should we use the CLI for that as well???
 
User avatar
w32pamela
Member Candidate
Member Candidate
Posts: 136
Joined: Fri Jul 12, 2013 4:22 pm

Re: v6.47beta [testing] is released!

Mon Feb 17, 2020 5:17 pm

*) quickset - use "station-wds" mode when connecting to AP with RouterOS flag;
Thank you for eliminating the automatic change to wireless mode = "station-wds" when an AP is identified as a routerboard device.

Who is online

Users browsing this forum: JardinEspanol, r00t and 18 guests