Page 1 of 1

v6.48beta [testing] is released!

Posted: Tue Jul 07, 2020 12:33 pm
by emils
Version 6.48beta12 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.48beta12 (2020-Jul-06 13:33):

Changes in this release:

*) arm - added support for automatic CPU frequency stepping for IPQ4018/IPQ4019 devices;
*) arm - improved watchdog and kernel panic reporting in log after reboots on IPQ4018/IPQ4019 devices;
*) bonding - added LACP monitoring (CLI only);
*) bridge - added warning message when port is disabled by the BPDU guard;
*) bridge - correctly remove dynamic VLAN assignment for bridge ports;
*) bridge - fixed dynamic VLAN assignment when changing port "frame-type" property (introduced in v6.46);
*) bridge - fixed dynamic VLAN assignment when changing port to tagged VLAN member;
*) bridge - fixed local MAC address removal from host table when deleting bridge interface;
*) bridge - improved BPDU guard logging;
*) chr - improved interface loading on startup on XEN;
*) chr - improved system stability when changing flow control settings on e1000;
*) crs3xx - added initial Bridge Port Extender support (CLI only);
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);
*) crs3xx - fixed duplicate host entries when creating static switch hosts;
*) crs3xx - fixed HW offloading for netPower 15FR and netPower 16P devices (introduced in v6.47);
*) crs3xx - fixed increased CPU temperature for CRS354-48G-4S+2Q+ device (introduced in v6.47);
*) crs3xx - improved Ethernet port group traffic forwarding for CRS354 devices;
*) defconf - fixed default configuration loading on RBmAPL-2nD;
*) defconf - improved default configuration generation on devices with changed wireless interface names;
*) dhcpv6-server - added ability to generate binding on first request;
*) dhcpv6-server - disallow changing binding's "prefix-pool";
*) dhcpv6-server - improved stability when changing server for static bindings;
*) dns - do not allow setting "forward-to" same as "name" or "regex";
*) dns - do not allow setting zero value IP addresses for "A" and "AAAA" records;
*) dns - do not use DoH for local queries when a server is specified;
*) dns - do not use type "A" for static entries with unspecified type;
*) dns - fixed listening for DNS queries when only dynamic static entries exist (introduced in v6.47);
*) export - fixed HotSpot "address-per-mac" parameter export;
*) export - fixed RouterBOARD USB "type" parameter export;
*) fetch - show status "uploaded" instead of "downloaded" when uploading a file;
*) filesystem - fixed increased "sector writes" reporting (introduced in v6.47);
*) filesystem - improved long-term filesystem stability and data integrity;
*) ftp - fixed possible buffer overflow;
*) ike1 - allow using "my-id" parameter with XAuth;
*) ike1 - fixed policy update with and without mode configuration;
*) ike1 - rekey phase 1 as responder for Windows initiators;
*) ike2 - added "prf-algorithm" support for phase 1;
*) ike2 - fixed initiator child SA init without policy;
*) ike2 - fixed policy reference for pending acquire;
*) ike2 - improved child SA rekeying process;
*) ike2 - retry RSA signature validation with deduced digest from certificate;
*) ipsec - added SHA384 hash algorithm support for phase 1 (CLI only);
*) ipsec - do not update peer endpoints for generated policy entries (introduced in v6.47);
*) ipsec - fixed multiple warning message display for peers;
*) ipsec - inactivate peer's policy on disconnect;
*) kidcontrol - allow creating static device entries without assigned user;
*) lora - added "spoof-gps" parameter for fake GPS coordinate sending;
*) lora - fixed JSON statistics inaccuracies;
*) lte - added "age" column and "max-age" parameter to "cell-monitor" (CLI only);
*) lte - added "comment" parameter for APN profiles (CLI only);
*) lte - added support for MTS 8810FT;
*) lte - fixed modem initialization when multiple modems are used simultaneously;
*) lte - fixed PDP authentication configuration for SIM7600;
*) metarouter - fixed image importing (introduced in v6.46);
*) ospf - improved route tag processing for OSPFv3;
*) ppp - added "ipv6-routes" parameter to "secrets" menu;
*) ppp - added support for "Framed-IPv6-Route" RADIUS attribute;
*) ppp - allow specifying pool name for "remote-ipv6-prefix-pool" parameter;
*) profile - fixed "unclassified" load reporting on PowerPC devices (introduced in v6.47);
*) qsfp - fixed auto-negotiation status;
*) qsfp - fixed break-out cable linking after reboot (introduced in v6.47);
*) qsfp - ignore FEC mode when set to fec91, only fec74 mode is supported (introduced in v6.47);
*) route - improved stability when 6to4 interface is configured with disabled IPv6 package;
*) routerboard - fixed "mode-button" support on SMIPS devices (introduced in v6.47);
*) routerboard - fixed "reset-button" menu presence on all devices;
*) smb - fixed possible memory leak;
*) smb - fixed SMB server (introduced in v6.47);
*) smb - limit active session count to 5 per connection;
*) ssh - fixed returned output saving to file when "output-to-file" parameter is used;
*) supout - added "LoRa" section to supout file;
*) switch - fixed MAC address learning on switch-cpu port for Atheros8316, Atheros8227 and Atheros7240 switch chips;
*) system - replace "3" in superscript to "^3" on RBD53GR devices;
*) tr069-client - added LTE model and revision parameters;
*) tr069-client - added "X_MIKROTIK_MimoRSRP" parameter for LTE RSRP value reporting;
*) tr069-client - allow passing LTE firmware update URL as XML;
*) w60g - added "mdmg-fix" parameter for RBwAP60Gx3 (CLI only);
*) winbox - allow performing "USB Power Reset" on "0" bus on RBM33G;
*) winbox - fixed flag displaying under "IP/DNS/Static" table;
*) winbox - fixed "IP->Kid Control->Devices" table automatic refreshing;
*) winbox - fixed minor typo in "BGP/Peer" menu;
*) winbox - fixed minor typo in "Users" menu;
*) winbox - fixed "receive-errors" setting persistence under "Wireless/Wireless Sniffer/Settings" menu;
*) winbox - fixed "tls-version" parameter setting under "IP/Services" menu;
*) winbox - hide irrelevant switch port parameters;
*) winbox - use health values reported by gauges for "System/Health" menu;
*) wireless - changed "station-roaming" default setting from "enabled" to "disabled";
*) wireless - create "connect-list" rule when address specified for "setup-repeater";
*) wireless - updated "bangladesh" regulatory domain information;
*) wireless - updated "egypt" regulatory domain information;

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.

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

Posted: Tue Jul 07, 2020 12:51 pm
by eworm
Now non-wireless devices have issues with the default configuration script:
system;error;critical;13328;39528;13328 error while running customized default configuration script: expected end of command (line 1310 column 53)
This is on RB750GL.

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

Posted: Tue Jul 07, 2020 1:08 pm
by emils
Can you please send the supout.rif file from your device to support@mikrotik.com?

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

Posted: Tue Jul 07, 2020 1:42 pm
by whatever
*) arm - added support for automatic CPU frequency stepping for IPQ4018/IPQ4019 devices;
Is this comparable to "ondemand" scheduler from x86 linux? Any numbers on expected power savings when the device is idle?

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

Posted: Tue Jul 07, 2020 2:03 pm
by santyx32
I wonder what's the real advantage of running my router with ondemand scheduler?

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

Posted: Tue Jul 07, 2020 2:15 pm
by eworm
I wonder what's the real advantage of running my router with ondemand scheduler?
It saves power and runs less hot.

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

Posted: Tue Jul 07, 2020 2:15 pm
by morf
What does "Bridge Port Extender" mean ? MLAG ?

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

Posted: Tue Jul 07, 2020 2:15 pm
by msatter
Can you please send the supout.rif file from your device to support@mikrotik.com?
And on the 4011RM and the hEX-S the same error message:
648beta12-error.JPG
13:04:38 system,error,critical error while running customized default configuration script: expected end of command (line 1310 column 53) 
13:04:38 system,error,critical 

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

Posted: Tue Jul 07, 2020 2:28 pm
by emils
msatter Do you have custom set of packages installed and wireless package is not installed?

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

Posted: Tue Jul 07, 2020 2:45 pm
by msatter
msatter Do you have custom set of packages installed and wireless package is not installed?
648beta12-pack.JPG
I also lost direct Winbox access to my 4011RM which is behind the the hEX-S and now only able to connect through Romon. The configuration did not change and Winbox just flashes by on my screen. For the safety I revered to 6.47 on my hEX-S.

Update.
The TikAPP can access the 4011 directly without problem. Really strange!

Update:
Ignoring the saved VIW file gives access again and I hope that this will not happen again and I have to make backups of those VIW files in case of that.

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

Posted: Tue Jul 07, 2020 2:52 pm
by eworm
msatter Do you have custom set of packages installed and wireless package is not installed?
Correct. My system has system, dhcp, advanced-tools & security installed. Opened SUP-21264 with support output.

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

Posted: Tue Jul 07, 2020 3:07 pm
by honzam
On ARM: Check for updates: ERROR: file not found

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

Posted: Tue Jul 07, 2020 3:17 pm
by emils
The default configuration script error message will be fixed in the next release. Thank you for reporting.
honzam Is there a specific package that is missing? What packages are installed on the device?

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

Posted: Tue Jul 07, 2020 3:21 pm
by honzam
See:

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

Posted: Tue Jul 07, 2020 3:30 pm
by eworm
*) dns - do not use DoH for local queries when a server is specified;
This is about forwarding? Looks like queries are still sent via DoH for me.
*) dns - do not use type "A" for static entries with unspecified type;
I do not understand that one... How could type be "A" and unspecified at the same time?

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

Posted: Tue Jul 07, 2020 3:31 pm
by nkourtzis
On ARM: Check for updates: ERROR: file not found
Not only on ARM. They probably withdrew the build due to the problems mentioned above.

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

Posted: Tue Jul 07, 2020 3:33 pm
by msatter
See:
I had that same message on my hEX-S, so I manually uploaded the firmware file.

@nkourtzis: It happened even before any reports were made so not likely that the files have been removed.

Re: v6.48beta [testing] is released! - 802.1BR

Posted: Tue Jul 07, 2020 4:03 pm
by doneware
crs3xx - added initial Bridge Port Extender support (CLI only);
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);

is this 802.1BR?

if so, how long until we get also support for this in CCRs? i'd love to see ports from port extenders to show up as 'virtual ports' on the connected CCRs...

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

Posted: Tue Jul 07, 2020 5:15 pm
by nkourtzis
Trying to upgrade but getting "not enough space for upgrade" after downloading and on rebooting, on a mAP 2nD, with the following packages installed:
  • Advanced Tools
  • DHCP
  • IPv6
  • LTE
  • NTP
  • PPP
  • Routing
  • Security
  • System
  • Wireless
Indeed, the "HDD space" is reported as 76 KiB without any files on it. This 16MB flash thing is becoming more and more annoying...

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

Posted: Tue Jul 07, 2020 8:56 pm
by Jotne
*) bridge - fixed dynamic VLAN assignment when changing port "frame-type" property (introduced in v6.46);
*) crs3xx - fixed HW offloading for netPower 15FR and netPower 16P devices (introduced in v6.47);
*) crs3xx - fixed increased CPU temperature for CRS354-48G-4S+2Q+ device (introduced in v6.47);
*) dns - fixed listening for DNS queries when only dynamic static entries exist (introduced in v6.47);
*) filesystem - fixed increased "sector writes" reporting (introduced in v6.47);
*) ipsec - do not update peer endpoints for generated policy entries (introduced in v6.47);
*) metarouter - fixed image importing (introduced in v6.46);
*) profile - fixed "unclassified" load reporting on PowerPC devices (introduced in v6.47);
*) qsfp - fixed break-out cable linking after reboot (introduced in v6.47);
*) qsfp - ignore FEC mode when set to fec91, only fec74 mode is supported (introduced in v6.47);
*) routerboard - fixed "mode-button" support on SMIPS devices (introduced in v6.47);
*) smb - fixed SMB server (introduced in v6.47);
Maybe there should be some more testing before new version is released?
10 errors was introduced in 6.47
2 errors was introduced in 6.46
That is 12 in total, maybe more that still are not found.

Where is 6.47.1 to fix errors introduced in 6.47?
I was hoping for no 6.48, but for 7.0beta

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

Posted: Tue Jul 07, 2020 10:31 pm
by msatter
There seems to be testing but internal. We start 6.48 at version beta twelve.

The flash write counter is a big problem despite it not be actual writes. It will decrease the resell value of your router because the write counter is extremely high due to this bug. This bug alone should have been tackled by 6.47.1 version at a earlier moment.

I don't think it is wise to have two active beta's side by side, being developed.

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

Posted: Tue Jul 07, 2020 11:11 pm
by DarkNate
*) ppp - added "ipv6-routes" parameter to "secrets" menu;
*) ppp - added support for "Framed-IPv6-Route" RADIUS attribute;
*) ppp - allow specifying pool name for "remote-ipv6-prefix-pool" parameter;
Does any of these changes mean it will help with this viewtopic.php?f=13&t=162930?

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

Posted: Tue Jul 07, 2020 11:52 pm
by mikrotikedoff
There will continue to be 6.X versions for the foreseeable future as not all the chip sets out there will be able to support the new linux kernel in 7.X

@msatter What feature sets are you using in the versions with the flash write counter issue that are preventing you from just rolling back to a version without this issue?

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

Posted: Wed Jul 08, 2020 12:15 am
by mducharme
There will continue to be 6.X versions for the foreseeable future as not all the chip sets out there will be able to support the new linux kernel in 7.X
What is not able to support the new linux kernel in v7? (other than really old devices, ex. mipsle)

From what I have seen, any MikroTik model that is currently sold works with v7, and probably most of those from the past several years that have been discontinued.

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

Posted: Wed Jul 08, 2020 1:46 am
by msatter
@msatter What feature sets are you using in the versions with the flash write counter issue that are preventing you from just rolling back to a version without this issue?
I am sorry, but I won't go for that.

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

Posted: Wed Jul 08, 2020 9:06 am
by emils
Upgrade issues from System Package menu should be resolved now.

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

Posted: Wed Jul 08, 2020 1:14 pm
by corp9592
*) bridge - fixed dynamic VLAN assignment when changing port "frame-type" property (introduced in v6.46);
*) crs3xx - fixed HW offloading for netPower 15FR and netPower 16P devices (introduced in v6.47);
*) crs3xx - fixed increased CPU temperature for CRS354-48G-4S+2Q+ device (introduced in v6.47);
*) dns - fixed listening for DNS queries when only dynamic static entries exist (introduced in v6.47);
*) filesystem - fixed increased "sector writes" reporting (introduced in v6.47);
*) ipsec - do not update peer endpoints for generated policy entries (introduced in v6.47);
*) metarouter - fixed image importing (introduced in v6.46);
*) profile - fixed "unclassified" load reporting on PowerPC devices (introduced in v6.47);
*) qsfp - fixed break-out cable linking after reboot (introduced in v6.47);
*) qsfp - ignore FEC mode when set to fec91, only fec74 mode is supported (introduced in v6.47);
*) routerboard - fixed "mode-button" support on SMIPS devices (introduced in v6.47);
*) smb - fixed SMB server (introduced in v6.47);
Maybe there should be some more testing before new version is released?
10 errors was introduced in 6.47
2 errors was introduced in 6.46
That is 12 in total, maybe more that still are not found.

Where is 6.47.1 to fix errors introduced in 6.47?
I was hoping for no 6.48, but for 7.0beta

I actually has the same though. The v6.47 is supposed to be the stable one, but with that bug fixing I am not inclined to deploy it to my Tik.

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

Posted: Wed Jul 08, 2020 7:32 pm
by krafg
*) lte - fixed modem initialization when multiple modems are used simultaneously;
Updated RBM33G and LtAP LTE kit successfully.

R11e-LTE-US keeps working well after update.

Regards.

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

Posted: Wed Jul 08, 2020 7:35 pm
by arendn
*) w60g - added "mdmg-fix" parameter for RBwAP60Gx3 (CLI only);
After update no traffic flows through to station devices. cannot mactel to them or macping. Downgraded back to 6.46.6

Re: v6.48beta [testing] is released! - 802.1BR

Posted: Thu Jul 09, 2020 2:36 am
by nz_monkey
crs3xx - added initial Bridge Port Extender support (CLI only);
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);

is this 802.1BR?

Yes it is 802.1BR

if so, how long until we get also support for this in CCRs? i'd love to see ports from port extenders to show up as 'virtual ports' on the connected CCRs...

I wondered the same thing. I suspect it may come fairly quickly, the CCR2004 is using it internally, so the code is already in place.

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

Posted: Thu Jul 09, 2020 12:36 pm
by encorer
Testing the hap ac ^ 2 router with a 0-1% CPU load showed that there is no difference between the power consumption of 6.47 and 6.48beta12 firmware. In both cases, it is 5.2-5.4W

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

Posted: Thu Jul 09, 2020 1:21 pm
by emils
Did you enable the on demand CPU scaling?
/system routerboard settings set cpu-frequency=auto

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

Posted: Thu Jul 09, 2020 2:40 pm
by encorer
/system routerboard settings set cpu-frequency=auto
Now I tried it, the result: with any frequency, consumption does not change, only the full load on the processor increases it by about one watt.

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

Posted: Thu Jul 09, 2020 3:00 pm
by mkx
Weird stuff ... the cpu-frequency setting. On my RB951G running ROS 6.46.5 it is possible to set cpu-frequency as well as cpu-mode ... which can be set to either regular or power-save. However, both print output and export keep quiet about this setting regardless the value. I'm not going to bother measuring the power draw to check if there's a difference.
On my RBD52G (hAP ac2) running same ROS version it is not possible to set cpu-mode ... it is not listed as possible argument to set command.

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

Posted: Thu Jul 09, 2020 3:52 pm
by la2185x
OK, Question, is it possible to provide an overview of the properties and syntax of the port-controller and port-extender CLI menu? This would be helpful and much appreciated

crs3xx - added initial Bridge Port Extender support (CLI only);
crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);

cheers

H

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

Posted: Thu Jul 09, 2020 4:12 pm
by onnoossendrijver
Let me tell you that this 802.1BR support makes me very excited :)

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

Posted: Thu Jul 09, 2020 9:48 pm
by nithinkumar2000
What's new in 6.48beta12 (2020-Jul-06 13:33):

Changes in this release:

*) ppp - added "ipv6-routes" parameter to "secrets" menu;
*) ppp - added support for "Framed-IPv6-Route" RADIUS attribute;
*) ppp - allow specifying pool name for "remote-ipv6-prefix-pool" parameter;
-
FInally some effort by Mikrotik Team for development of IPv6. :-o

Please add Radius Accounting for Delegated-IPv6-Prefix over PPPOE

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

Posted: Fri Jul 10, 2020 12:56 am
by osc86
Still no fix mentioned for discarded IPv6 Neighbor solicitations entering the bridge when igmp-snooping is enabled.
It's really annoying not being able to use IPv6 and igmp-snooping together on the same bridge.

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

Posted: Fri Jul 10, 2020 11:38 am
by nithinkumar2000
I Wonder why still many people are not demanding IPv6 features.
IPv6 is now in trend and it is really beneficial because it consumes less resource and No NAT tensions....

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

Posted: Fri Jul 10, 2020 12:07 pm
by Chupaka
No NAT tensions....
Multihoming and load balancing?..

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

Posted: Fri Jul 10, 2020 12:32 pm
by nithinkumar2000
No NAT tensions....
Multihoming and load balancing?..
BGP Multihoming can be done but not sure about Load balancing...... Well for ISP always NAT is the biggest problem. So much of tension in maintaing NAT Logs and also issues with Govt. Sites when Multiple Clients use same Public IP...

I Hope IPv6 is the only solutions to these set of issues...

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

Posted: Fri Jul 10, 2020 6:54 pm
by Sob
BUG: DNS resolution fails for TXT records containing multiple strings.

Another user reported the problem here. I see slightly different results:

- client sends query to RouterOS device (e.g. "dig mail2._domainkey.mail.ru TXT @<routeros device>")
- RouterOS sends query to upstream resolver
- upstream resolver sends response
- RouterOS ignores response
- RouterOS retries previous two steps few times
- RouterOS sends server failure to client

In any case, it's broken. If there's only one string in TXT record, it works correctly. But if there are more, it fails. Other examples:

pp-epsilon1._domainkey.mail.paypal.com
softmaker_com_2018._domainkey.softmaker.com

I guess it's probably broken since DNS changes in 6.47.

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

Posted: Fri Jul 10, 2020 8:23 pm
by nescafe2002
Sob, 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.

Edit: Issue has been reported to support (SUP-22228)

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

Posted: Wed Jul 15, 2020 10:36 am
by mattgorecki
*) w60g - added "mdmg-fix" parameter for RBwAP60Gx3 (CLI only);
After update no traffic flows through to station devices. cannot mactel to them or macping. Downgraded back to 6.46.6
Upgraded a pair of Wireless Wire dishes and experienced the same thing. Link comes up but passes no traffic, not even mactel. Downgraded both sides to 6.47.1 for it to work again.

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

Posted: Wed Jul 15, 2020 9:17 pm
by msatter
msatter
I also lost direct Winbox access to my 4011RM which is behind the the hEX-S and now only able to connect through Romon. The configuration did not change and Winbox just flashes by on my screen. For the safety I revered to 6.47 on my hEX-S.

Update.
The TikAPP can access the 4011 directly without problem. Really strange!

Update:
Ignoring the saved VIW file gives access again and I hope that this will not happen again and I have to make backups of those VIW files in case of that.

I lost again my setting and the only thing I did was use "shown columns" and I had this time a backup to restore the current config. This is really nasty that Winbox 3.24 and Beta 6.48-12 is causing this!

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

Posted: Sun Jul 19, 2020 1:31 am
by bobaoapae
Hello, i have a RouterBoard Hex S, and on version 6.47.1 or 6.48.beta12, the dns server stop resolving certains domains after randomly time without any error on log.. I tested with and without DoH enabled, i don't know how to send info to check this issue, logs on WinBox don't show any error, after reboot DNS has back work.. I has do a downgrade to long term version and no issue has been in 3 days, on versions 6.47 or 6.48 dns stop working every day.

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

Posted: Sun Jul 19, 2020 1:55 am
by nescafe2002
i don't know how to send info to check this issue, logs on WinBox don't show any error, after reboot DNS has back work..

When DNS is unresponsive again, before rebooting: add logging topic dns, perform name lookup from client, generate supout.rif, download supout.rif and send it to support.

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

Posted: Sun Jul 19, 2020 2:47 am
by rooted
hAP AC² updated and so far everything is working fine, maybe a couple hundred kilobytes more free memory is all I've noticed immediately.

Will let it settle in and see if anything pops up.

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

Posted: Sun Jul 19, 2020 12:56 pm
by rooted
There seems to be testing but internal. We start 6.48 at version beta twelve.

The flash write counter is a big problem despite it not be actual writes. It will decrease the resell value of your router because the write counter is extremely high due to this bug. This bug alone should have been tackled by 6.47.1 version at a earlier moment.

I don't think it is wise to have two active beta's side by side, being developed.
Are these devices known to have an issue with the memory failing? I've had dd-wrt devices flashed and written to for 10+ years without failure, and these devices had new firmware flashed at least twice a month.

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

Posted: Fri Jul 24, 2020 12:35 am
by pe1chl
I found that reset to defaults does not work correctly when only part of the packages is installed.
For example, I typically use only these packages on routers without wireless interface:
- advanced-tools
- dhcp
- ipv6
- ppp
- routing
- security
- system

So, no hotspot, mpls, wireless.
When such a router is reset to defaults, it will not be configured with defaults. It can only be accessed via MAC address.

Before I reset to defaults, I had the issue mentioned in reply #8 viewtopic.php?p=804449#p804449
(I did the reset because of that)

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

Posted: Mon Jul 27, 2020 10:49 pm
by MRYAN81
While using 6.48beta12 on a CCR1009, I noticed that my WAN IP isn't being obtained automatically. After the modem resets or looses service, the router doesn't not obtain a IP on IPv4. IPv6 seems to work fine. On the IPv4 side it just shows renewing, but appears to be passing traffic. If I click release, it grabs it with no issues.

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

Posted: Tue Jul 28, 2020 5:45 pm
by petrb
Thanks for working on IPv6 ... please implement also "Framed-IPv6-Route" RADIUS attribute for DHCPv6. You are in half away. Thanks. Petr

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

Posted: Fri Aug 07, 2020 6:25 am
by Ivoshiee
*) w60g - added "mdmg-fix" parameter for RBwAP60Gx3 (CLI only);
After update no traffic flows through to station devices. cannot mactel to them or macping. Downgraded back to 6.46.6
What ever it is supposed to do or what device it shall affect, but all my ptp w60g do the same - links are up, romon can see them and even ssh into them, but no ip traffic or even arp is working.

I will try to get downgrade to v6.47.1.

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

Posted: Sat Aug 08, 2020 7:24 pm
by petrb
Hi,... bug - IPv6 prefix leases from dhcpv6 server (set via radius) are not marked as used in "ipv6 pool user prefixes". This can create prefix conflict. Works fine for the IPv4 dhcp+radius.
/ipv6 pool
add name=pool1 prefix=2a01:5e0:501::/48 prefix-length=56
/ipv6 dhcp-server
add address-pool=pool1 interface=bridge1 lease-time=10m name=server1 use-radius=yes
/ipv6 pool used print ///empty table, not posting :)
/ipv6 dhcp-server binding print 
Flags: X - disabled, R - radius, D - dynamic 
 #   ADDRESS                                                          DUID                    SERVER                    STATUS 
 0 RD 2a01:5e0:501:f00::/56                                            0xb869f499c7f8          server1                   bound
Same for IPv4, but used IP is successfully set as used.

Thanks.

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

Posted: Wed Aug 12, 2020 12:02 pm
by rushlife
what about 6.48Beta23 ??

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

Posted: Wed Aug 12, 2020 2:05 pm
by msatter
what about 6.48Beta23 ??
Context?

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

Posted: Wed Aug 12, 2020 4:14 pm
by rushlife
ROS 6.48Beta23 should bring fix for CRS354 switches.
And it is "unpublic" release....

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

Posted: Wed Aug 12, 2020 4:25 pm
by msatter
ROS 6.48Beta23 should bring fix for CRS354 switches.
And it is "unpublic" release....
Do you know if there is also a Beta48 fix for the crashing Winbox (64) the next time after you alter any columns in Winbox? Before testing backup your Winbox config files because the one altered has become unusable.

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

Posted: Fri Aug 14, 2020 4:19 pm
by msatter
More than a month without an update of the 6.48 beta. That is a long time.

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

Posted: Fri Aug 14, 2020 5:00 pm
by eworm
Indeed... We are bored, give us something to play with!

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

Posted: Fri Aug 14, 2020 8:16 pm
by msatter
I want to change the shown collumns in Winbox and that it survive than the current session. Not blowing up in my face each time so that I have to restore a back session and start from scratch.

My orignal session was destroyed by 6.48 so I had to use one from a different router to have atleast some columns.

Yes it a beta but you don't expect it destroy your saved sessions by Winbox.

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

Posted: Fri Aug 14, 2020 8:19 pm
by pe1chl
Is that a 6.48 bug or a winbox bug or a combined bug of these two?
I am still using winbox 3.21 because of big problems with newer versions, and I do not see this problem when connecting to 6.48beta12

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

Posted: Fri Aug 14, 2020 10:56 pm
by msatter
Using a non 6.48 is no problem. It is a problem caused by 6.48beta12 and it does corrupt the saved sessions by Winbox. I use Winbox 3.24 64 bits.

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

Posted: Sat Aug 15, 2020 8:46 am
by pe1chl
But it doesn't with winbox 3.21, that is why I think it may be a winbox bug just as well. Changes were made in winbox for scaling and it also
affects me on older RouterOS releases! I cannot reliably "drag" things anymore in winbox, they are dropped at random positions.
When I drag a column width, the width jumps to a very wide value. When I drag a line in the firewall rule set, it is dropped at a random place.

This makes winbox >3.21 (including 3.24) completely unusable for me. So I stick to 3.21 for now, I tried the beta on a CHR, and I do not observe the problem you noticed.

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

Posted: Tue Aug 18, 2020 1:20 pm
by ricardobrock
Does this version also include "Delegated-IPv6-Prefix" for PPP ? And if not, is there a ETA for this?

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

Posted: Wed Aug 19, 2020 10:52 am
by emils
Version 6.48beta27 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.48beta27 (2020-Aug-18 06:20):

Changes in this release:

*) arm - added support for automatic CPU frequency stepping for IPQ4018/IPQ4019 devices;
*) arm - improved stability when forcing 25G speed on unsupported interface;
*) bridge - allow to exclude interfaces from extended ports (CLI only);
*) bridge - fixed host table update on SNMP query;
*) bridge - show error when switch do not support controlling bridge or port extension (CLI only);
*) bridge - show "H" flag for extended bridge ports;
*) certificate - clear challenge password on renew;
*) crs3xx - added initial Bridge Port Extender support (CLI only);
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);
*) crs3xx - fixed "custom-drop-packet" and "not-learned" switch stats for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed hardware offloaded MPLS forwarding when using bonding interfaces;
*) crs3xx - fixed QSFP+ interface LEDs when using break-out cable for CRS326-24S+2Q+;
*) crs3xx - fixed QSFP+ interface linking after reboot for CRS326-24S+2Q+ (introduced in v6.47);
*) crs3xx - fixed switch "not-learned" stats for CRS305, CRS326-24G-2S+, CRS328-24P-4S+, CRS328-4C-20S-4S+, CRS318 devices;
*) crs3xx - improved Ethernet port group traffic forwarding for CRS354 devices;
*) crs3xx - improved system stability when using hardware offloaded MPLS;
*) defconf - improved default configuration generation on devices with non-default wireless interface names;
*) discovery - send the same "Chassis ID" on all interfaces for LLDP packets;
*) discovery - use "static" interface list by default instead of "!dynamic";
*) dot1x - fixed duplicate EAP request packets for server;
*) dot1x - fixed EAP packet version numbering;
*) fetch - show status "uploaded" instead of "downloaded" when uploading a file;
*) filesystem - fixed repartition on non-first partition;
*) filesystem - fixed repartition on RB4011 series devices;
*) filesystem - improved long-term filesystem stability and data integrity;
*) gps - fixed "init-channel" release when not used;
*) health - changed PSU state parameter type to read-only;
*) health - removed unused "heater-control" and "heater-threshold" parameters;
*) hotspot - added "vlan-id" parameter support for hosts and HTML pages;
*) hotspot - do not verify Hotspot interface status when detecting if HTTP/HTTPS login method is allowed;
*) hotspot - ignore packets from host while MAC authentication is in progress;
*) interface - added new builtin "static" interface list;
*) ipsec - fixed client certificate usage when certificate is renewed with SCEP;
*) kidcontrol - fixed "time-unlimited-rate" to engage in correct time;
*) l2tp - fixed multiple tunnel establishment from the same remote IP address (introduced in v6.47);
*) lora - expose "joinEui" un "devEui" values in the log;
*) lora - fixed "spoof-gps" parameter padding (introduced in v6.47.1);
*) lte - added "comment" parameter for APN profiles;
*) lte - fixed dynamic DHCP client creation when editing APN profile;
*) lte - fixed multiple passthrough APN default route installation;
*) lte - fixed RSCP value reporting;
*) lte - validate interface existence on initiation;
*) ospf - fixed case when changing one distribution metric changed metrics for other distribution options;
*) ospf - fixed disappearing NSSA default route;
*) ospf - fixed processing of "unknown" LSA type;
*) ospf - optimized LSA printing for smaller message sizes;
*) poe - fixed "power-cycle" functionality on RB960GSP;
*) ppp - fixed PPP interface editing for the first time after reboot or after 20 seconds;
*) routerboot - fixed etherboot FCS errors with 100Mbps rate for CRS309, CRS317 devices ("/system routerboard upgrade" required);
*) routerboot - fixed memory test on CCR2004-1G-12S+2XS ("/system routerboard upgrade" required);
*) sfp - stabilized CRS212 SFP port functionality and improved monitoring of optical modules;
*) sftp - fixed "flash" directory access (introduced in v6.46);
*) smb - fixed file path validation (introduced in v6.46);
*) snmp - fixed "current" value reporting on CCR series devices;
*) snmp - fixed "fan-speed" value reporting on CCR series devices;
*) ssh - skip interactive authentication when not running in interactive mode;
*) tr069-client - added additional wireless registration table parameters;
*) tr069-client - added wireless "noise-floor" and "overall-tx-ccq" information parameters;
*) traffic-flow - added NAT event logging support for IPFIX;
*) webfig - fixed default value presence when creating new entries under "IP->Kid Control";
*) webfig - fixed negative value usage in "spoof-gps" parameter (introduced in v6.47.1);
*) wireless - added support for U-NII-2 for cAP ac;
*) wireless - added support for U-NII-2 for wAP ac;
*) wireless - updated "canada" regulatory domain information;
*) wireless - updated "indonesia5" regulatory domain information;
*) wireless - updated "no_country_set" regulatory domain information;
*) wireless - updated "united states" regulatory domain information;
*) www - improved WWW service stability when receiving bogus packets;

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.

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

Posted: Wed Aug 19, 2020 1:03 pm
by msatter
My Winbox crash on start, is gone with Beta 27. This happened when I added/deleted/changed a column to any viewing box. Many thanks.

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

Posted: Wed Aug 19, 2020 1:19 pm
by rushlife
6.48beta27 installed on my CRS354, so we will see.
Anyway - thx for your hard work / mikrotik team.

btw.after install I see in log this :
system,error,critical,,, error while running customized default configuration script: expected end of command (line 1315 column 53)

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

Posted: Wed Aug 19, 2020 1:27 pm
by eworm
btw.after install I see in log this :
system,error,critical,,, error while running customized default configuration script: expected end of command (line 1315 column 53)
Me too. Reported for 6.47beta12 as SUP-21264, just re-opened.

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

Posted: Wed Aug 19, 2020 2:15 pm
by emils
My mistake. The fix was not properly pushed in the build. The issue is with non-present wireless package on the router. Will make sure it is fixed in the next build.

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

Posted: Thu Aug 20, 2020 8:22 pm
by marekm
*) wireless - added support for U-NII-2 for cAP ac;
*) wireless - added support for U-NII-2 for wAP ac;
Which U-NII-2 ecactly: 2A, 2B or 2C?
5350-5470 MHz is U-NII-2B; 2A and 2C were already supported weren't they? Or do you mean in some specific countries?

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

Posted: Thu Aug 20, 2020 10:24 pm
by yacq
What is controlling bridge?

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

Posted: Mon Aug 24, 2020 10:23 am
by anthonws
Upgrading 2011UiAS-2HnD from beta 12 to beta 27 puts router in bootloop (stuck). Last message is "Starting services" and then router reboots.

Downgraded to beta 12 and restored configuration.

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

Posted: Mon Aug 24, 2020 3:45 pm
by Kindis
*) wireless - added support for U-NII-2 for cAP ac;
*) wireless - added support for U-NII-2 for wAP ac;
Which U-NII-2 ecactly: 2A, 2B or 2C?
5350-5470 MHz is U-NII-2B; 2A and 2C were already supported weren't they? Or do you mean in some specific countries?
I was also confused by this but I think this is an unlock for US as I think all U-NII-2 bands where locked on US equipment. So for me with EU equipment do not have to care about this.

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

Posted: Wed Aug 26, 2020 1:01 pm
by Ivoshiee
*) w60g - added "mdmg-fix" parameter for RBwAP60Gx3 (CLI only);
After update no traffic flows through to station devices. cannot mactel to them or macping. Downgraded back to 6.46.6
What ever it is supposed to do or what device it shall affect, but all my ptp w60g do the same - links are up, romon can see them and even ssh into them, but no ip traffic or even arp is working.

I will try to get downgrade to v6.47.1.
With the latest beta I went in more cautious mode and did not upgrade too many devices before finding out it being still broken. What is with that?

Btw: Make romon tool capable of transferring files, so that testing of broken firmwares will go more smoothly or so.

Edit: Suppout files as well:
http://ranume.levikom.ee/mikrotik/w60g/ ... supout.rif
http://ranume.levikom.ee/mikrotik/w60g/ ... supout.rif

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

Posted: Wed Sep 02, 2020 12:29 am
by mducharme
I have a question about this 802.1BR support. I understand there is this idea of a controlling bridge, which would be like a master switch. What happens if this goes down? Is it a single point of failure?

With traditional proprietary stacking solutions from other vendors, the stacked units sync their config so that if one goes down the others continue operating, which prevents one from being a single point of failure.

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

Posted: Wed Sep 02, 2020 2:29 pm
by emils
Version 6.48beta35 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.48beta35 (2020-Sep-02 07:50):

Changes in this release:

*) bonding - removed "sys-id" and "sys-priority" from monitor-slaves command;
*) bridge - fixed BPDU guard port disable/enable on HW offloaded interfaces;
*) bridge - fixed host table update on SNMP query;
*) bridge - fixed multicast table printing;
*) bridge - fixed packet forwarding for CAP and BCP controlled interfaces (introduced in v6.48beta12);
*) bridge - fixed STP alternate and backup port states for devices with switch chip (introduced in v6.47);
*) bridge - increased multicast table size to 4K entries;
*) crs3xx - fixed "mirror-source" property on switch port disable for CRS305, CRS326-24G-2S+, CRS328, CRS318 devices;
*) crs3xx - fixed port isolation for "switch-cpu" port for CRS305, CRS326-24G-2S+, CRS328, CRS318 devices;
*) crs3xx - fixed port isolation removal for "switch-cpu" port on CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed "storm-rate" traffic limiting for switch-cpu port on CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed switch ACL rules for CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed switch port "egress-rate" removal for CRS305, CRS326-24G-2S+, CRS328, CRS318 devices;
*) crs3xx - fixed VLAN tagged packet forwarding on "switch-cpu" port for CRS305, CRS326-24G-2S+, CRS328, CRS318 devices (introduced in v6.48beta12);
*) defconf - improved CAP interface bridging;
*) defconf - improved default configuration generation on devices without wireless package installed;
*) discovery - added "lldp-med-net-policy-vlan" property for assigning VLAN ID (CLI only);
*) discovery - allow choosing which discovery protocol is used (CLI only);
*) discovery - fixed discovery on mesh ports;
*) discovery - fixed discovery packet sending on newly bridged port with "protocol-mode=none";
*) discovery - fixed discovery when enabled only on master port;
*) discovery - use interface MAC address when sending MNDP from slave port;
*) dns - added IPv6 support for DoH;
*) dns - fixed multiple TXT string replies;
*) dns - hide default static entry "type" from export;
*) fetch - fixed "src-address" usage for SFTP;
*) filesystem - improved long-term filesystem stability and data integrity;
*) health - removed unused "heater-control" and "heater-threshold" parameters;
*) hotspot - added support for captive portal advertising using DHCP (RFC7710);
*) hotspot - improved management service stability when receiving bogus packets;
*) ike2 - fixed local side NAT detection;
*) ipsec - do not kill connection when peer's "name" or "comment" is changed;
*) ipsec - refresh peer's DNS only when phase 1 is down;
*) lte - added support for Alcatel IK41VE1;
*) snmp - fixed value types for "dot1dStp";
*) tr069-client - send correct "ConnectionRequestURL" when using IPv6;
*) traffic-flow - added "sys-init-time" parameter support;
*) wireless - allow setting "tx-power" up to 40;

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.

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

Posted: Wed Sep 02, 2020 5:08 pm
by Sob
*) ipsec - refresh peer's DNS only when phase 1 is down;
Tiny little problem with this, it keeps resolving hostname even when peer is disabled. It doesn't break anything, but it's unnecessary.

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

Posted: Wed Sep 02, 2020 6:15 pm
by osc86
*) discovery - allow choosing which discovery protocol is used (CLI only);
EDIT: just found out, you can choose multiple protocols, comma separated. Thanks for this welcome change, I can finally disable cdp.

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

Posted: Thu Sep 03, 2020 12:27 am
by ludvik
/tool snmp-get working??? Last functional version is 6.45.6 ... SUP-8826

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

Posted: Thu Sep 03, 2020 1:19 am
by UpRunTech
Emils, what does this mean exactly?

*) crs3xx - fixed switch ACL rules for CRS312, CRS326-24S+2Q+ and CRS354 devices;

I am using rules to prioritise traffic - does this mean they may not have been working up until this point? Which rule settings or behaviours were broken?

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

Posted: Thu Sep 03, 2020 8:22 am
by emils
Tiny little problem with this, it keeps resolving hostname even when peer is disabled. It doesn't break anything, but it's unnecessary.
Unable to reproduce such behavior. Do you see actual DNS requests going out the router? How are you determining the hostname is being resolved when the peer is disabled?

EDIT: Reproduced. Should be resolved in the next build.

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

Posted: Thu Sep 03, 2020 4:53 pm
by Florian
"*) dns - added IPv6 support for DoH;"


Not sure this is working ? The DoH server I'm using is https://doh.opendns.com/dns-query , and I see requests to 146.112.41.2 , but none to 2620:119:fc::2

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

Posted: Tue Sep 08, 2020 2:01 pm
by olivier2831
Version 6.48beta35 has been released.
...
*) discovery - added "lldp-med-net-policy-vlan" property for assigning VLAN ID (CLI only);
Is this feature enough to automatically assign IP Phones to specific VLAN (ie configuring a VoiceVLAN per port) ?

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

Posted: Tue Sep 08, 2020 2:11 pm
by eworm
Not sure this is working ? The DoH server I'm using is https://doh.opendns.com/dns-query , and I see requests to 146.112.41.2 , but none to 2620:119:fc::2
I guess IPv4 is still preferred if a domain resolves with A and AAAA record. Try a domain that has just an AAAA record or use IPv6 address.

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

Posted: Tue Sep 08, 2020 2:18 pm
by skylark
IPv6 DoH will work with:
set use-doh-server="https://[2606:4700:4700::1111]/dns-query"

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

Posted: Wed Sep 09, 2020 12:15 am
by LynxChaus
*) ipsec - do not kill connection when peer's "name" or "comment" is changed;
Wow. It's possible to make this change for vpls, pptp, openvpn interfaces too?

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

Posted: Wed Sep 09, 2020 12:02 pm
by pe1chl
*) ipsec - do not kill connection when peer's "name" or "comment" is changed;
Wow. It's possible to make this change for vpls, pptp, openvpn interfaces too?
In fact this should be done for every possible item in the config. Don't know what is the exact status now, but I have seen many things go down-up when changing only a comment.

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

Posted: Wed Sep 09, 2020 12:18 pm
by notToNew
In fact this should be done for every possible item in the config. Don't know what is the exact status now, but I have seen many things go down-up when changing only a comment.
netwatch too, just changing the comment should not update the uptime

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

Posted: Thu Sep 10, 2020 11:09 pm
by Ivoshiee
May we expect the 60G devices to still be broken?

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

Posted: Tue Sep 15, 2020 3:18 pm
by emils
Version 6.48beta40 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.48beta40 (2020-Sep-14 13:34):

Changes in this release:

*) arm64 - improved reboot reason reporting in log;
*) bridge - added minor fixes and improvements for IGMP snooping with HW offloading;
*) bridge - fixed link-local multicast forwarding when IGMP snooping and HW offloading is enabled;
*) bridge - fixed MDB entry removal when using bridge port "fast-leave" property;
*) conntrack - automatically reduce connection tracking timeouts when table is full;
*) console - allow "once" parameter for bonding monitoring;
*) crs3xx - added initial Bridge Port Extender support (CLI only);
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);
*) crs3xx - added switch-cpu port VLAN filtering (switch-cpu port is now mapped with bridge interface VLAN membership when vlan-filtering is enabled);
*) crs3xx - fixed IGMP snooping for CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed switch "copy-to-cpu" property for CRS305, CRS318, CRS326-24G-2S+, CRS328 devices;
*) detnet - fixed malformed dummy DHCP User Class option;
*) detnet - use MAC address from bridge interface instead of slave port;
*) dhcpv4-server - improved "client-id" value parsing;
*) ipsec - refresh peer's DNS only when phase 1 is down;
*) leds - fixed LED type setting;
*) smb - fixed possible memory leak;
*) sms - fixed SMS sending when both "interface" and "smsc" parameters are specified;
*) snmp - added information from IPsec "active-peers" menu to MIKROTIK-MIB;
*) snmp - fixed "/tool snmp-get" functionality (introduced in v 6.46beta43);
*) snmp - fixed value types for "dot1qPvid";
*) supout - added bonding interface monitor information;
*) switch - fixed Ethernet padding for small packets;
*) tr069-client - allow passing LTE firmware update URL as XML;
*) user-manager - do not allow creating limitation that crosses midnight;
*) user-manager - updated PayPal's root certificate authorities;
*) wireless - improved WPS process stability;

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.

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

Posted: Tue Sep 15, 2020 4:28 pm
by pe1chl
I have a feature request that should be "relatively easy to implement" :-)
There is the existing "/ip dhcp-server vendor-class-id" feature in the DHCP server. I would like to match the items not only by class-id but also by MAC address/mask.
Preferably as an AND function with two optional fields: you can either enter the class-ID (or leave it blank to always match) or enter a MAC address and mask (or leave it at default 00:00:00:00:00:00/00:00:00:00:00:00) or both.

The purpose is to match on e.g. the MAC prefix (with a match like 44:55:66:00:00:00/FF:FF:FF:00:00:00) or on MAC type (with 02:00:00:00:00:00/03:00:00:00:00:00 to match locally assigned MAC addresses, for example).
Once matched the DHCP server would use a specified pool/network just like the "/ip dhcp-server vendor-class-id" already does based on vendor class id.

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

Posted: Tue Sep 15, 2020 6:35 pm
by osc86
- IGMP-Snooping feature on CCR breaks igmp-proxy. IGMP Join Requests generated by the router on the upstream interface are filtered out by the igmp snooping feature.
When disabled, it works fine, but overloads my eoip tunnels because the traffic is flooded to all ports (as expected).

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

Posted: Wed Sep 16, 2020 12:03 pm
by EdPa
@osc86 - I did not manage to repeat the IGMP proxy issue. Please report this to support portal or email to support@mikrotik.com and briefly describe your setup.

Also, for everyone how is interested in the new Bridge Controller and Extender feature, we have created an article that describes it in more detail, more advanced examples are coming soon. Follow this link - https://help.mikrotik.com/docs/display/ ... t+Extender. Feel free to share you feedback and recommendations, or report if something goes wrong.

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

Posted: Tue Sep 22, 2020 4:10 am
by mducharme
Also, for everyone how is interested in the new Bridge Controller and Extender feature, we have created an article that describes it in more detail, more advanced examples are coming soon. Follow this link - https://help.mikrotik.com/docs/display/ ... t+Extender. Feel free to share you feedback and recommendations, or report if something goes wrong.
That's very helpful, but it did not answer my most pressing question - does this create a single point of failure from the controller bridge perspective? Is there a way to have failover for the controller bridge? If you look at traditional stacking situations (ex. two switches stacked), either one can die and the remaining switch will carry on as normal. This is really helpful for ISP situations, you can get two cross connects with important providers so that if one switch dies your cross connect does not go down. With 802.1BR it seems that if you have one switch as a control bridge and the other as a port extender, if the control bridge switch dies, you lose both, so it seems that you don't really get redundancy as in traditional stacking. Can you clarify this?

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

Posted: Tue Sep 22, 2020 7:53 am
by mkx
Another request for clarification: when reading Packet flow section of port extender description it is not entirely clear whether PE device actually switches frames between own ports (after physical port, associated with DST MAC, is known) on its own or all packets are forwarded to CB regardless the destination port location. If it's the later, then CB/PE concept is suboptimal also from performance point of view ...

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

Posted: Tue Sep 22, 2020 10:53 am
by EdPa
@mducharme, mkx - the CB currently does not support any failover techniques. Once the CB device dies, the PE devices will lose all the control and data forwarding rules, other PE will not take over as CB. This is an important aspect when considering this configuration and we are looking for ways how to make CB redundant.

The local switching on PE devices is not supported, the PE does not store any hosts in local FDB, it is considered as a dumb device and the main purpose is to extend ports. The switching performance can be affected when comparing multi-switch to single-switch forwarding. In turn, you get simplified LAN configuration and management. For a very time-sensitive application or congested upstream occasions, it can make sense to enable local switching. We will see if this can be implemented.

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

Posted: Tue Sep 22, 2020 10:59 am
by Cha0s
If there's no redundancy and no efficiency (local switching), what's the point in this technology?

Why not implement something that's more datacenter/enterprise friendly?
Even if it's proprietary. It's not like everyone else's stacking options are inter-compatible anyway...

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

Posted: Tue Sep 22, 2020 12:54 pm
by EdPa
It allows you to manage only one device, you do no need to create VLANs, configure STP and apply other bridge-related settings on each switch separately. You can monitor all the PE devices from a single controller, like the PoE-out status and interface stats, and quickly apply any needed changes or add another port extender.

Edit: Note that this is an early implementation and we are still exploring what other feature sets can be brought into upcoming RouterOS versions, including the redundancy for CB.

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

Posted: Tue Sep 22, 2020 3:13 pm
by pe1chl
It is a good idea, but it should support redundant connections and redundant switches. I.e. a "controlling bridge" is fine for configuration purposes but it should not be a SPOF in the actually running network.

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

Posted: Tue Sep 22, 2020 7:26 pm
by Cha0s
All I am saying is, that those who have enough switches that will benefit from a single management plane, will almost certainly need HA features to go with it. In other words, introducing SPOFs on the network just to save on management costs, probably wont fly with most network engineers. At least that's my opinion.

Of course it's a nice addition, and I will surely use it on small/non critical networks, but if you are going to do it, do it right from the get go.
Otherwise you will just create more negative comments about MikroTik switches from those that expect a typical stacking option, only to find out not only its not "typical" but also a SPOF and a bottleneck.
Just like the negative comments about folks who thought that MikroTik switches can do wirespeed L3 routing.

IMHO you will not do yourself any favors by releasing this feature half-baked.

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

Posted: Wed Sep 23, 2020 4:26 am
by nz_monkey
I see this as being more useful as a port extender to CCR's, to say break out a 100Gbit port on a CCR to 10gigabit ports on the CRS.

Port Extension is NOT stacking...

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

Posted: Wed Sep 23, 2020 10:29 am
by andriys
All I am saying is, that those who have enough switches that will benefit from a single management plane, will almost certainly need HA features to go with it.
My friends have an office here with 200+ client ports, with all cable runs going into a single rack with five 48-port access switches (something from HP as far as I remember), and one 16-port switch sitting in between these 5 access switches and the rest of the equipment in their server room. Managing VLAN memberships here is a pretty tedious task, I would say. Tracking the configuration history is not easy either. This setup already has SPOF, and in this particular case that's fine/acceptable. This port extension thing would be very beneficial for this kind of setups.

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

Posted: Wed Sep 23, 2020 10:42 am
by pe1chl
Exactly. In that configuration (and when the switches are indeed from the same manufacturer) it would normally be possible to configure them as a "stack" and save a lot of effort configuring. But of course then you first need to read the manual chapter about the stacking, which lots of users never do.
Also, such configurations often grow from simple to more complex, adding new switches of different models along the way, and it may not be possible to stack them.

Still it would be nice if there was some configuration management in RouterOS where you can configure multiple units from a single interface. Not only for switches, but also e.g. for redundant routers in a VRRP setup. When this is limited to configuration and does not imply some active master that does all the work at runtime, it would not reduce reliability, in fact it could make it easier to make redundant setups.

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

Posted: Thu Sep 24, 2020 2:40 am
by mducharme
Port Extension is NOT stacking...
Right, this isn't stacking - but where this all started was a thread where people were asking for stacking, and MikroTik said they would look for an open standards way, and then they came out with this. Also, they just said in the response to my request for clarification that they are looking for ways to make the control bridge failover, so presumably this is intended to be their solution for stacking.

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

Posted: Mon Sep 28, 2020 12:43 am
by hatred
hAP ac², 6.48b40
After several days uptime router hanged and become unavailable via winbox (including by MAC).
After power re-cycle, it successfully booted up but most addresses from the address lists disappeared.
How can I enable verbose debug logging to USB flash or external host to see what happened next time?

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

Posted: Tue Sep 29, 2020 11:59 am
by anthonws
RB4011iGS+5HacQ2HnD + 6.48beta40

When enabling IPFIX router enters reboot loop.

Shall I open a support case to share suppout?

Thanks,
anthonws.

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

Posted: Tue Oct 06, 2020 6:34 pm
by shavenne
Tried to update my switches at home (CRS112-8P-4S, CRS112-8G-4S, CRS309-1G-8S+, CRS328-24P-4S+) to 6.48beta40 yesterday (6.47.4 before).
For some reason all clients stopped getting IPv6 addresses from my RB4011 (with 7.1beta2) then.
I started downgrading the firmware on the CRS328-24P-4S+ (to which the RB4011 is also connected) and all clients connected to it were getting IPv6 addresses again.
I still had to downgrade the other switches too to obtain IPv6 there also.

I find it quite strange as I'm not using any routing or firewall functions on the switches. Actually just VLANs (all IPv6 clients are in a vlan) and nothing else.
Any idea what's going wrong?

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

Posted: Thu Oct 15, 2020 2:58 pm
by emils
Version 6.48beta48 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.48beta48 (2020-Oct-14 10:26):

Important note!!!

Using this version on CRS354-48G-4S+2Q+RM or CRS354-48P-4S+2Q+RM will cause booting issues and device may need to be reinstalled.

Changes in this release:

*) bridge - automatically remove extended interfaces when deleting PE device from CB;
*) cap - fixed L2MTU path discovery;
*) cap - fixed L2MTU setting from CAPsMAN;
*) certificate - fixed private key verification for CA certificate during signing process;
*) cloud - improved backup generation process;
*) crs3xx - fixed CDP packet forwarding for CRS305, CRS318, CRS326-24G-2S+, CRS328 devices;
*) crs3xx - fixed port-isolation for CRS305, CRS318, CRS326-24G-2S+, CRS328 devices (introduced in v6.48beta35);
*) defconf - fixed default configuration loading on RBmAP-2nD;
*) dhcpv4-client - fixed DHCP offer packet parsing with overload option present;
*) discovery - fixed occasional wrong Chassis-ID for LLDP packets (introduced in v6.48beta35);
*) dot1x - accept priority tagged (VLAN 0) EAP packets on dot1x client;
*) fetch - improved SSL handshake processing;
*) filesystem - improved long-term filesystem stability and data integrity;
*) ike1 - fixed "my-id=address" parameter usage together with certificate authentication;
*) ike2 - added support for IKEv2 Message Fragmentation (RFC7383);
*) ike2 - fixed EAP MSK length validation;
*) ike2 - fixed too small payload parsing;
*) interface - added temperature warning and interface disable on overheat for SFP and SFP+ interfaces (CLI only);
*) led - fixed state persistence after device reboot on NetMetal 5 ac devices;
*) lora - fixed device going into "ERROR" state caused by FSK modulated downlinks;
*) lte - fixed "band" value reporting;
*) lte - fixed multiple APN passthrough on R11e-4G;
*) lte - improved EARFCN reporting in 3G and LTE modes on Sierra modems;
*) lte - limit allowed APN count to 3 on R11e-LTE;
*) m33g - added support for "/system gpio" menu (CLI only);
*) mpls - fixed duplicate "LabelRelease" message sending;
*) profile - improved idle process detection on x86 processors;
*) profile - improved process classification on ARM devices;
*) quickset - added "Port Mapping" to QuickSet;
*) quickset - fixed local IP address setting on master interface;
*) radius - added "Service-Type" attribute to Access-Request for IPv4 and IPv6 DHCP servers;
*) routerboard - fixed PCIe bus reset during power-on on MMIPS devices ("/system routerboard upgrade" required);
*) routerboard - force power-down on PCIe bus during reboot on LHGR devices ("/system routerboard upgrade" required);
*) script - added error message in the logs if startup script runtime limit was exceeded;
*) snmp - added information from IPsec "active-peers" menu to MIKROTIK-MIB;
*) snmp - added new LTE monitoring OID's to MIKROTIK-MIB;
*) switch - fixed Ethernet padding for small packets;
*) tr069-client - fixed RouterOS downgrade procedure;
*) traffic-flow - added NAT event logging support for IPFIX;
*) traffic-generator - fixed 32Gbps limitation;
*) user - improved WinBox and The Dude authenticated session handling;
*) user-manager - do not allow creating limitation that crosses midnight;
*) user-manager - updated PayPal's root certificate authorities;
*) vrrp - made "password" parameter sensitive;
*) w60g - general stability and performance improvements;
*) wireless - added support for US FCC UNII-2 and Canada country profiles for NetMetal series devices;
*) wireless - do not override MTU and ARP values from CAPsMAN with local forwarding;
*) wireless - fixed incorrect wireless capability information in association response frames;
*) wireless - updated "no_country_set" regulatory domain information;

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.

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

Posted: Thu Oct 15, 2020 4:30 pm
by fbl
May we expect the 60G devices to still be broken?
I have talked with Mikrotik's support about this problem for some time.
They have applied a fix in 6.48beta48, which fixed the issues for me.
My 3,7km Link is stable again with 6.48beta48. It had massive stability issues (very frequent disconnects) with anything above 6.46.6.

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

Posted: Thu Oct 15, 2020 4:36 pm
by antonsb
May we expect the 60G devices to still be broken?
I have talked with Mikrotik's support about this problem for some time.
They have applied a fix in 6.48beta48, which fixed the issues for me.
My 3,7km Link is stable again with 6.48beta48. It had massive stability issues (very frequent disconnects) with anything above 6.46.6.
This should be fixed now, if you are still experiencing issues - please contact us through support portal, so we can debug even further.

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

Posted: Thu Oct 15, 2020 7:13 pm
by DanAtCommon
I can confirm w60g connections are stable on beta48

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

Posted: Thu Oct 15, 2020 7:59 pm
by LynxChaus
Version 6.48beta48 has been released.
*) interface - added temperature warning and interface disable on overheat for SFP and SFP+ interfaces (CLI only);
Is "interface disable" optional feature?
*) snmp - added information from IPsec "active-peers" menu to MIKROTIK-MIB;
*) snmp - added new LTE monitoring OID's to MIKROTIK-MIB;
Where is new MIB?

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

Posted: Fri Oct 16, 2020 8:16 am
by emils
The MIB file is available on our wiki:
https://wiki.mikrotik.com/wiki/Manual:S ... _.28MIB.29

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

Posted: Fri Oct 16, 2020 1:00 pm
by sid5632
Why don't you link to this from https://mikrotik.com/download instead of burying it away on the Wiki?

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

Posted: Fri Oct 16, 2020 3:34 pm
by LynxChaus
The MIB file is available on our wiki:
https://wiki.mikrotik.com/wiki/Manual:S ... _.28MIB.29
Thnx. Found glitch - mtxrLTEModemInterfaceIndex not returned:

MIKROTIK-MIB::mtxrLTEModemInterfaceIndex = No Such Object available on this agent at this OID
MIKROTIK-MIB::mtxrLTEModemSignalRSSI.1 = INTEGER: 0
MIKROTIK-MIB::mtxrLTEModemSignalRSRP.1 = INTEGER: -114
MIKROTIK-MIB::mtxrLTEModemCellId.1 = INTEGER: 7ad8203
MIKROTIK-MIB::mtxrLTEModemAccessTechnology.1 = INTEGER: eutran(7)
MIKROTIK-MIB::mtxrLTEModemSignalSINR.1 = INTEGER: -2
MIKROTIK-MIB::mtxrLTEModemEntry.8.1 = INTEGER: 503170
MIKROTIK-MIB::mtxrLTEModemEntry.9.1 = INTEGER: 3
MIKROTIK-MIB::mtxrLTEModemEntry.10.1 = INTEGER: 9720
MIKROTIK-MIB::mtxrLTEModemEntry.11.1 = STRING: "355654090805867"
MIKROTIK-MIB::mtxrLTEModemEntry.12.1 = STRING: "250026939347786"
MIKROTIK-MIB::mtxrLTEModemEntry.13.1 = STRING: "897010269393477862ff"
MIKROTIK-MIB::mtxrLTEModemEntry.14.1 = STRING: "Evolved 3G (LTE)"

and mtxrLTEModemEntry improperly described in MIB. smilint show bunch of warnings:
Mikrotik.mib:516: warning: index element `mtxrWlCMRtabAddr' of row `mtxrWlCMRtabEntry' should be not-accessible in SMIv2 MIB
Mikrotik.mib:626: warning: node `mtxrWlCMRtabEapIdent' must be contained in at least one conformance group
Mikrotik.mib:691: warning: node `mtxrWlCMState' must be contained in at least one conformance group
Mikrotik.mib:698: warning: node `mtxrWlCMChannel' must be contained in at least one conformance group
Mikrotik.mib:736: warning: node `mtxrWlCMRemoteName' must be contained in at least one conformance group
Mikrotik.mib:743: warning: node `mtxrWlCMRemoteState' must be contained in at least one conformance group
Mikrotik.mib:750: warning: node `mtxrWlCMRemoteAddress' must be contained in at least one conformance group
Mikrotik.mib:757: warning: node `mtxrWlCMRemoteRadios' must be contained in at least one conformance group
Mikrotik.mib:954: warning: node `mtxrWl60GStaPhyRate' must be contained in at least one conformance group
Mikrotik.mib:961: warning: node `mtxrWl60GStaRssi' must be contained in at least one conformance group
Mikrotik.mib:968: warning: node `mtxrWl60GStaDistance' must be contained in at least one conformance group
Mikrotik.mib:976: warning: current group `mtxrWirelessGroup' is not referenced in this module
Mikrotik.mib:1281: warning: current group `mtxrQueueGroup' is not referenced in this module
Mikrotik.mib:1485: warning: current group `mtxrHealthGroup' is not referenced in this module
Mikrotik.mib:1537: warning: current group `mtxrLincenseGroup' is not referenced in this module
Mikrotik.mib:1724: warning: current group `mtxrHotspotActiveUserGroup' is not referenced in this module
Mikrotik.mib:1758: warning: current group `mtxrDHCPGroup' is not referenced in this module
Mikrotik.mib:1823: warning: current group `mtxrSystemGroup' is not referenced in this module
Mikrotik.mib:1881: warning: current group `mtxrScriptGroup' is not referenced in this module
Mikrotik.mib:1924: warning: current group `mtxrScriptRunGroup' is not referenced in this module
Mikrotik.mib:1999: warning: current group `mtxrNstremeDualGroup' is not referenced in this module
Mikrotik.mib:2091: warning: current group `mtxrNeighborGroup' is not referenced in this module
Mikrotik.mib:2155: warning: current group `mtxrGPSGroup' is not referenced in this module
Mikrotik.mib:2184: warning: current group `mtxrWirelessModemGroup' is not referenced in this module
Mikrotik.mib:2762: warning: current group `mtxrInterfaceStatsGroup' is not referenced in this module
Mikrotik.mib:2911: warning: current group `mtxrPOEGroup' is not referenced in this module
Mikrotik.mib:3064: warning: current group `mtxrLTEModemGroup' is not referenced in this module
Mikrotik.mib:3151: warning: current group `mtxrPartitionGroup' is not referenced in this module
Mikrotik.mib:3192: warning: current group `mtxrOpticalGroup' is not referenced in this module
Mikrotik.mib:3335: warning: current group `mtxrIkeSAGroup' is not referenced in this module
Mikrotik.mib:3544: warning: current group `mtxrTrapGroup' is not referenced in this module

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

Posted: Fri Oct 16, 2020 7:51 pm
by pe1chl
I had reported case SUP-28445 (memory leak in the DNS resolver) and when I now test it, it appears that it is fixed, but I do not remember what the reply size threshold was when I experienced this problem and reported it on the technical support service desk. And there is no mention of this issue in the release notes (that I recognize).
So a general remark: I think support cases should remain browseable for the submitter, even after they have been closed by MikroTik. At this time I do not know if the problem has been solved or if my current test case is below the threshold that I previously reported.

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

Posted: Fri Oct 16, 2020 8:13 pm
by eworm
So a general remark: I think cases should remain browseable for the submitter, even after they have been closed by MikroTik.
I am pretty sure they are. Log in to the support portal and see your closed cases.

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

Posted: Fri Oct 16, 2020 9:08 pm
by pe1chl
So a general remark: I think cases should remain browseable for the submitter, even after they have been closed by MikroTik.
I am pretty sure they are. Log in to the support portal and see your closed cases.
Ok now I see that with even more clicking they can be made visible...
(it would be so much clearer when the cases were visible on the home page of the support portal)

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

Posted: Sat Oct 17, 2020 10:49 am
by honzam
I can confirm w60g connections are stable on beta48
Yes, it very very better

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

Posted: Sun Oct 18, 2020 12:16 am
by hazartilirot
Who could explain me why my phone suffers from intermittent drops. I've updated to the latest version the same issue persists.
It usually happens when my internal DNS server is down. You might tell me - there is no internet connection. However I've got AC68U at hand when my phone connects to it provided the router doesn't have an ISP cable, the phone behaves in an ordinary way . Why does MikroTik drops connections and force it to reconnect? I've recorded a short video.
https://www.youtube.com/watch?v=um9T9K27AAY

#update: strangely enough I've just taken another phone it connects to the MikroTik and doesn't drop a connection. So the problem relates to my phone. The question is why it doesn't have the issue when it connects to AC68U. What makes it drop the connection? a lack of a DNS server?

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

Posted: Sun Oct 18, 2020 11:09 am
by michaels
What's new in 6.48beta48 (2020-Oct-14 10:26):
*) traffic-flow - added NAT event logging support for IPFIX;
this is great. looking forward to the final 6.48 release.
I will test it with nfdump 1.6.21 collector.

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

Posted: Sun Oct 18, 2020 12:17 pm
by pe1chl
Who could explain me why my phone suffers from intermittent drops. I've updated to the latest version the same issue persists.
It usually happens when my internal DNS server is down. You might tell me - there is no internet connection. However I've got AC68U at hand when my phone connects to it provided the router doesn't have an ISP cable, the phone behaves in an ordinary way . Why does MikroTik drops connections and force it to reconnect?
That is not done by your MikroTik router, it is done by the operating system of your phone. When it connects wifi and succeeds, it goes on to perform other tests like DHCP request and then DNS check and when something fails it disconnects and deems the connection unusable.

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

Posted: Mon Oct 19, 2020 11:10 am
by sakirozkan
60 Ghz link up down still

viewtopic.php?f=7&t=166370

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

Posted: Mon Oct 19, 2020 5:12 pm
by honzam
All clients also beta48? If yes, write to support@mikrotik.com

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

Posted: Tue Oct 20, 2020 12:01 am
by lelmus
Ran into a problem with beta48 and SFP modules on CCR1016-12S-1S+. I'm using Intel modules that worked fine until beta48. Some reported data in the SFP fields is wrong like voltage and temperature, but this didn't cause any issues until beta48, and now they are randomly shutting off every few minutes with messages of "disabling sfp6 for 10min due to high module temperature".

The modules temperatures were checked and are between cool and light warm. Some SFP modules give correct voltage and temperature and some don't, but tests show speed and performance is solid on all of them. See enclosed pics of good and bad fields of reported data.

Any way to bypass/disable the disabling of SFP due to high module temperature???

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

Posted: Wed Oct 21, 2020 6:29 am
by Ivoshiee
May we expect the 60G devices to still be broken?
I have talked with Mikrotik's support about this problem for some time.
They have applied a fix in 6.48beta48, which fixed the issues for me.
My 3,7km Link is stable again with 6.48beta48. It had massive stability issues (very frequent disconnects) with anything above 6.46.6.
Interesting, what Mikrotik 60g boxes are 3,7km capable?

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

Posted: Thu Oct 22, 2020 7:16 pm
by fbl
May we expect the 60G devices to still be broken?
I have talked with Mikrotik's support about this problem for some time.
They have applied a fix in 6.48beta48, which fixed the issues for me.
My 3,7km Link is stable again with 6.48beta48. It had massive stability issues (very frequent disconnects) with anything above 6.46.6.
Interesting, what Mikrotik 60g boxes are 3,7km capable?
None are. At least not officially.
However, it is possible to establish a Link over at least 3,7km with a pair of LHG60. But it is extreamly sensible to bad weather and should have a backup of some kind if reliability is important.
https://twitter.com/fblaese/status/1259139628755451907

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

Posted: Sun Oct 25, 2020 4:20 am
by radionerd
Tried 6.48beta48
L2TP IPSec using certificates is still broken for my clients.
Searched the forums, but haven't found any resolution.

My L2TP/IPSec clients failed after 6.47, was able to downgrade back to 6.46.6 and everything worked ok again.

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

Posted: Sun Oct 25, 2020 10:36 am
by msatter
Tried 6.48beta48
L2TP IPSec using certificates is still broken for my clients.
Searched the forums, but haven't found any resolution.

My L2TP/IPSec clients failed after 6.47, was able to downgrade back to 6.46.6 and everything worked ok again.
Did you already contact Mikrotik support on this? e-mail: support@mikrotik.com