Community discussions

MikroTik App
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

v6.48 [stable] is released!

Wed Dec 23, 2020 12:01 pm

RouterOS version 6.48 has been released in public "stable" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.48 (2020-Dec-22 11:20):

*) arm - added support for automatic CPU frequency stepping for IPQ4018/IPQ4019 devices;
*) arm - improved system stability;
*) arm - improved watchdog and kernel panic reporting in log after reboots on IPQ4018/IPQ4019 devices;
*) arm64 - improved reboot reason reporting in log;
*) bgp - fixed VPNV4 RD byte order;
*) bonding - added LACP monitoring;
*) branding - fixed LCD logo loading from new style branding package;
*) bridge - added "multicast-router" monitoring value for bridge interface;
*) bridge - added fixes and improvements for IGMP and MLD snooping;
*) bridge - added minor fixes and improvements for IGMP snooping with HW offloading;
*) bridge - added warning message when port is disabled by the BPDU guard;
*) bridge - allow to exclude interfaces from extended ports;
*) bridge - automatically remove extended interfaces when deleting PE device from CB;
*) bridge - correctly filter packets by L2MTU size;
*) bridge - correctly remove dynamic VLAN assignment for bridge ports;
*) bridge - fixed "multicast-router" setting on bridge enable;
*) bridge - fixed MDB entry removal when using bridge port "fast-leave" property;
*) 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 link-local multicast forwarding when IGMP snooping and HW offloading is enabled;
*) bridge - fixed local MAC address removal from host table when deleting bridge interface;
*) bridge - fixed multicast table printing;
*) bridge - improved BPDU guard logging;
*) bridge - increased multicast table size to 4K entries;
*) bridge - show "H" flag for extended bridge ports;
*) bridge - show error when switch do not support controlling bridge or port extension;
*) bridge - use "frame-types=admit-all" by default for extended bridge ports;
*) cap - fixed L2MTU setting from CAPsMAN;
*) certificate - clear challenge password on renew;
*) certificate - fixed CRL URL length limit;
*) certificate - fixed private key verification for CA certificate during signing process;
*) certificate - generate CRL even when CRL URL not specified;
*) certificate - properly flush expired SCEP OTP entries;
*) chr - fixed SSH key import on Azure;
*) chr - fixed VLAN tagged packet transmit on bridge for Hyper-V installations;
*) chr - improved interface loading on startup on XEN;
*) chr - improved system stability when changing flow control settings on e1000;
*) cloud - improved backup generation process;
*) conntrack - automatically reduce connection tracking timeouts when table is full;
*) console - allow "once" parameter for bonding monitoring;
*) crs3xx - added initial Bridge Port Extender support;
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - added switch-cpu port VLAN filtering (switch-cpu port is now mapped with bridge interface VLAN membership when vlan-filtering is enabled);
*) crs3xx - correctly filter packets by L2MTU size;
*) crs3xx - fixed "custom-drop-packet" and "not-learned" switch stats for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed "mirror-source" property on switch port disable for CRS305, CRS326-24G-2S+, CRS328, CRS318 devices;
*) crs3xx - fixed "storm-rate" traffic limiting for switch-cpu port on CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed "switch-cpu" VLAN membership on bridge disable;
*) crs3xx - fixed CDP packet forwarding for CRS305, CRS318, CRS326-24G-2S+, CRS328 devices;
*) crs3xx - fixed duplicate host entries when creating static switch hosts;
*) 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 switch "copy-to-cpu" property for CRS305, CRS318, CRS326-24G-2S+, CRS328 devices;
*) crs3xx - fixed switch "not-learned" stats for CRS305, CRS326-24G-2S+, CRS328-24P-4S+, CRS328-4C-20S-4S+, CRS318 devices;
*) crs3xx - improved system stability on CRS354 devices;
*) crs3xx - improved system stability when receiving large frames for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (introduced in v6.47.5);
*) defconf - fixed default configuration loading on RBcAP-2nD and RBwAP-2nD;
*) defconf - fixed static IP address setting in case default configuration loading fails;
*) defconf - improved CAP interface bridging;
*) defconf - improved default configuration generation on devices with non-default wireless interface names;
*) detnet - fixed malformed dummy DHCP User Class option;
*) detnet - use MAC address from bridge interface instead of slave port;
*) dhcp - fixed DHCP packet forwarding to IPsec policies;
*) dhcpv4-server - improved "client-id" value parsing;
*) dhcpv6 server - added support for "Delegated-IPv6-Prefix" for PPP services;
*) dhcpv6-server - added ability to generate binding on first request;
*) dhcpv6-server - added support for "option18" and "option37" for RADIUS managed clients;
*) dhcpv6-server - allow loose static binding "pool" parameter (introduced in v6.46.8);
*) dhcpv6-server - make sure that calling station ID always contains DUID;
*) discovery - added "lldp-med-net-policy-vlan" property for assigning VLAN ID;
*) discovery - allow choosing which discovery protocol is used;
*) 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 - send the same "Chassis ID" on all interfaces for LLDP packets;
*) discovery - use interface MAC address when sending MNDP from slave port;
*) disk - fixed external EXT3 disk mounting on x86 systems;
*) dns - added IPv6 support for DoH;
*) dns - do not use type "A" for static entries with unspecified type;
*) dns - end ongoing queries when changing DoH configuration;
*) dns - fixed listening for DNS queries when only dynamic static entries exist (introduced in v6.47);
*) dot1x - accept priority tagged (VLAN 0) EAP packets on dot1x client;
*) dot1x - fixed reauthentication after server rejects a client into VLAN;
*) dot1x - fixed unicast destination EAP packet receiving when a client is running on a bridge port;
*) dude - fixed configuration menu presence on ARM64 devices;
*) export - fixed RouterBOARD USB "type" parameter export;
*) filesystem - fixed repartition on RB4011 series devices;
*) filesystem - fixed repartition on non-first partition;
*) 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 - added support for captive portal advertising using DHCP (RFC7710);
*) hotspot - fixed "html-directory" parameter export;
*) hotspot - improved management service stability when receiving bogus packets;
*) ike1 - fixed "my-id=address" parameter usage together with certificate authentication;
*) ike1 - fixed 'rsa-signature-hybrid' authentication method;
*) ike1 - fixed memory leak on multiple CR payloads;
*) 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 - added support for IKEv2 Message Fragmentation (RFC7383);
*) ike2 - fixed EAP MSK length validation;
*) ike2 - fixed too small payload parsing;
*) ike2 - improved EAP message integrity checking;
*) ike2 - improved child SA rekeying process;
*) interface - added temperature warning and interface disable on overheat for SFP and SFP+ interfaces (CLI only);
*) interface - fixed pwr-line running state (introduced in v6.45);
*) ipsec - added SHA384 hash algorithm support for phase 1;
*) ipsec - do not kill connection when peer's "name" or "comment" is changed;
*) ipsec - fixed client certificate usage when certificate is renewed with SCEP;
*) ipsec - fixed multiple warning message display for peers;
*) ipsec - inactivate peer's policy on disconnect;
*) ipsec - refresh peer's DNS only when phase 1 is down;
*) kidcontrol - allow creating static device entries without assigned user;
*) led - fixed state persistence after device reboot on NetMetal 5 ac devices;
*) lora - fixed device going into "ERROR" state caused by FSK modulated downlinks;
*) lora - limited output power in RU region for range 868.7 MHz - 869.2 MHz according to regulations;
*) lte - added "age" column and "max-age" parameter to "cell-monitor" (CLI only);
*) lte - added "comment" parameter for APN profiles;
*) lte - added support for Alcatel IK41VE1;
*) lte - fixed "band" value reporting;
*) lte - increased "at+cops" reply timeout to 90 seconds;
*) m33g - added support for "/system gpio" menu (CLI only);
*) metarouter - allow creating RouterOS metarouter instances on devices with 16MB flash storage;
*) metarouter - fixed memory leak when tearing down metarouter instance;
*) ppp - added "bridge-learning" parameter support;
*) ppp - added "ipv6-routes" parameter to "secrets" menu;
*) ppp - added support for "Framed-IPv6-Route" RADIUS attribute;
*) ppp - store "last-caller-id" for PPP secrets;
*) ppp - store "last-disconnect-reason" for PPP secrets;
*) profile - added "lcd" process classificator;
*) 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;
*) route - improved stability when 6to4 interface is configured with disabled IPv6 package;
*) 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;
*) snmp - fixed value types for "dot1dStp";
*) snmp - fixed value types for "dot1qPvid";
*) ssh - fixed returned output saving to file when "output-to-file" parameter is used;
*) ssh - skip interactive authentication when not running in interactive mode;
*) supout - added bonding interface monitor information;
*) supout - improved autosupout.rif file generation process;
*) timezone - updated timezone information from "tzdata2020d" release;
*) tr069-client - added "X_MIKROTIK_MimoRSRP" parameter for LTE RSRP value reporting;
*) tr069-client - added LTE model and revision parameters;
*) tr069-client - added additional wireless registration table parameters;
*) tr069-client - added branding package build time parameter;
*) tr069-client - added wireless "noise-floor" and "overall-tx-ccq" information parameters;
*) tr069-client - allow passing LTE firmware update URL as XML;
*) tr069-client - fixed RouterOS downgrade procedure;
*) tr069-client - fixed TotalBytesReceived parameter value;
*) tr069-client - send correct "ConnectionRequestURL" when using IPv6;
*) traffic-flow - added "sys-init-time" parameter support;
*) traffic-flow - added NAT event logging support for IPFIX;
*) traffic-generator - fixed 32Gbps limitation;
*) user-manager - do not allow creating limitation that crosses midnight;
*) user-manager - updated PayPal's root certificate authorities;
*) webfig - allow hiding QuickSet mode selector;
*) webfig - allow hiding and renaming inline buttons;
*) webfig - fixed default value presence when creating new entries under "IP/Kid Control";
*) webfig - properly stop background processes when switching away from QuickSet tab;
*) winbox - added "src-mac-address" parameter under "IP/DHCP-Server/Leases" menu;
*) winbox - added missing IGMP Snooping settings to "Bridge" menu;
*) winbox - added missing MSTP settings to "Bridge" menu;
*) winbox - added support for LTE Cell Monitor;
*) winbox - allow adding bonding interface with one slave interface;
*) winbox - allow performing "USB Power Reset" on "0" bus on RBM33G;
*) winbox - do not show "network-mode" parameter for LTE interfaces that do not support it;
*) winbox - fixed "IP->Kid Control->Devices" table automatic refreshing;
*) winbox - fixed "interface" and "on-interface" parameter presence under "Bridge/Hosts" menu;
*) winbox - fixed "receive-errors" setting persistence under "Wireless/Wireless Sniffer/Settings" menu;
*) winbox - fixed "tls-version" parameter setting under "IP/Services" menu;
*) winbox - fixed minor typo in "Users" menu;
*) winbox - provide sane default values for bridge "VLAN IDs" parameter;
*) winbox - use health values reported by gauges for "System/Health" menu;
*) wireless - added U-NII-2 support for US and Canada country profiles for mANTBox series devices;
*) wireless - create "connect-list" rule when address specified for "setup-repeater";
*) wireless - do not override MTU and ARP values from CAPsMAN with local forwarding;
*) wireless - improved WPS process stability;
*) wireless - increased "group-key-update" maximum value to 1 day;
*) wireless - updated "indonesia5" regulatory domain information;
*) wireless - updated "no_country_set" regulatory domain information;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this particular RouterOS release.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

***temp***

Wed Dec 23, 2020 1:24 pm

Nice Christmas present :)
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.48 [stable] is released!

Wed Dec 23, 2020 1:40 pm

Trusted checkbox appears twice in Bridge -> Ports -> <interface> -> General
 
kd2pm2
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Wed Nov 14, 2012 7:14 am
Location: New Jersey, USA

Re: v6.48 [stable] is released!

Wed Dec 23, 2020 1:49 pm

Upgraded my 2011 and 4011....time to test and see what happens.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.48 [stable] is released!

Wed Dec 23, 2020 3:35 pm

dns - fixed listening for DNS queries when only dynamic static entries exist (introduced in v6.47);
Only dynamic static?..
 
User avatar
tomaskir
Trainer
Trainer
Posts: 1162
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: v6.48 [stable] is released!

Wed Dec 23, 2020 3:51 pm

That's one huge changelog - the stability fixes for ARM are much welcomed.

After the upgrade, "/export compact" without any reconfiguration shows 2 new changes from "default":

Image
...
Image

What has changed in the defaults for user groups and neighbor discovery?
 
TimothyKoval
just joined
Posts: 2
Joined: Wed Jun 10, 2020 1:51 am

Re: v6.48 [stable] is released!

Wed Dec 23, 2020 9:14 pm

Setting firmware auto upgrade to each no or yes crashes my RB3011, working fine on cAP ac and CRS112
/system routerboard settings set auto-upgrade=yes
 
erlinden
Forum Guru
Forum Guru
Posts: 1900
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: v6.48 [stable] is released!

Wed Dec 23, 2020 10:03 pm

I see the following error in the log (every 30 min):
IPsec-SA expired before finishing rekey
Haven't seen this issue in the current LTS and the 6.47.x releases.

Found this answer in the topic, hope it helps:
viewtopic.php?f=2&t=159536&p=783686&hil ... ey#p784468
Last edited by erlinden on Wed Dec 23, 2020 10:56 pm, edited 1 time in total.
 
MartijnVdS
Frequent Visitor
Frequent Visitor
Posts: 93
Joined: Wed Aug 13, 2014 9:36 am

Re: v6.48 [stable] is released!

Wed Dec 23, 2020 10:18 pm

Do these multicast fixes mean IPv6 will work better again?

Because my routers keep forgetting to respond to IPv6 neighbor solicitations over multicast after a while. Meaning it _seems_ to work for a while.. and then when you leave it breaks.
 
Guscht
Member Candidate
Member Candidate
Posts: 236
Joined: Thu Jul 01, 2010 5:32 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 12:18 am

*) branding - fixed LCD logo loading from new style branding package;
How can we add a LCD logo? It would be great to add a custom image with our company logo and the Router-Name.
 
kevinb361
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Wed Jul 01, 2020 5:02 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 1:54 am

Just updated the following all working great so far!

CCR 1009, CSR 326, and two wAP AC's
 
dadoremix
Member Candidate
Member Candidate
Posts: 133
Joined: Sat May 14, 2011 11:31 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 2:14 am

we are waiting for 6.48.5 .. stable release is beta channel
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 2:27 am

What has changed in the defaults for user groups and neighbor discovery?
I'm not sure about neighbor discovery, but in user groups it appears that the group "full" does not have the "dude" policy enabled by default.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 2:42 am

*) tr069-client - send correct "ConnectionRequestURL" when using IPv6;
I am a bit puzzled by this fix as even though our clients are mostly dual stack, and our ACS URL has both A and AAAA records and is listening on IPv4 and IPv6, I've never seen the clients ever attempt to connect to the ACS via IPv6, only IPv4. Until now I assumed that the TR069 client on MikroTik had support for IPv4 only and not IPv6. Under what circumstances will the TR069 client attempt a connection via IPv6?
 
User avatar
krafg
Forum Guru
Forum Guru
Posts: 1020
Joined: Sun Jun 28, 2015 7:36 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 3:20 am

Updated all my devices and for now all is working fine.

Regards.
 
User avatar
dioeyandika
just joined
Posts: 19
Joined: Fri Feb 08, 2019 11:30 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 3:57 am

hem after upgrade system health not showing voltage and temperature RB 750G r3 Image
 
User avatar
G2Dolphin
Member Candidate
Member Candidate
Posts: 164
Joined: Sun May 17, 2015 6:03 pm
Location: Moscow, Russia

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 4:09 am

*) m33g - added support for "/system gpio" menu (CLI only);
I don't have M33g, but... does that allow us to play with unused GPIOs for simple stuff like turning some load on and off with relays or having additional status LEDs? That would be awesome! :D
 
psybernoid
just joined
Posts: 12
Joined: Sat Oct 22, 2011 11:32 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 8:21 am

On my CRS326-24G-2S+ after updating I no longer have any interfaces nor will the device reboot cleanly.

This is the output from terminal:
[admin@CRS326] > /interface
[admin@CRS326] /interface> print
Flags: D - dynamic, X - disabled, R - running, S - slave
 #     NAME                                TYPE       ACTUAL-MTU L2MTU
[admin@CRS326] /interface> /system reboot
Reboot, yes? [y/N]:
y
system will reboot shortly

Rebooting...
failed to stop ipsec: std failure: timeout (13)
failed to stop route: std failure: timeout (13)
 
jcmerg
just joined
Posts: 2
Joined: Sat Apr 07, 2018 6:28 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 10:19 am

On my CRS326-24G-2S+ after updating I no longer have any interfaces nor will the device reboot cleanly.

This is the output from terminal:
[admin@CRS326] > /interface
[admin@CRS326] /interface> print
Flags: D - dynamic, X - disabled, R - running, S - slave
 #     NAME                                TYPE       ACTUAL-MTU L2MTU
[admin@CRS326] /interface> /system reboot
Reboot, yes? [y/N]:
y
system will reboot shortly

Rebooting...
failed to stop ipsec: std failure: timeout (13)
failed to stop route: std failure: timeout (13)
Same Issue here, i've removed all lacp bonding interfaces from the bridge, after that, the switch worked fine, so i downgraded to the last 6.47.x

I've also tried a factory reset and reconfiguration with a export backup .... same issue.
 
DarkNate
Forum Veteran
Forum Veteran
Posts: 997
Joined: Fri Jun 26, 2020 4:37 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 10:30 am

RB450Gx4. Smooth upgrade, no problems, no errors, nothing. Perfect.
 
elbob2002
Member Candidate
Member Candidate
Posts: 252
Joined: Tue May 15, 2018 8:15 pm
Location: Ireland

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 1:04 pm

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)
Same here on my RB3011. My WAN port was on ether 2 and kept flapping.

Moved it to ether10 and now have a stable WAN connection again but obviously the flapping issue isn't resolved.

Before moving to ether 10 I turned autonegotiation off but no luck.
 
psybernoid
just joined
Posts: 12
Joined: Sat Oct 22, 2011 11:32 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 1:37 pm

Same Issue here, i've removed all lacp bonding interfaces from the bridge, after that, the switch worked fine, so i downgraded to the last 6.47.x

I've also tried a factory reset and reconfiguration with a export backup .... same issue.
Ahh. I have 3 LACP bonds on mine. I may well be having the same issue then.

Though how did you remove the bonds if the interfaces where not showing?
 
User avatar
R00tKit
just joined
Posts: 9
Joined: Fri Nov 07, 2014 12:24 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 2:15 pm

Sadly I confirm the problem with Several RB3011. The switch chip of ports 1-5 works erratically after the upgrade.
All my PPPoE connections on those ports (usually 1,2) started flapping.
Switching to ports 6-10 worked for me, but this is kind of serious.

Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS. I think I will revert to the older version for now
Last edited by R00tKit on Tue Dec 29, 2020 10:38 am, edited 1 time in total.
 
nimbo78
Frequent Visitor
Frequent Visitor
Posts: 80
Joined: Tue Jan 14, 2014 9:09 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 2:42 pm

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)
same here
bridge with rstp and hw offload, rb3011 with upgraded RouterBoard
on ether6-ether10 all good

"stable" :)
Last edited by nimbo78 on Thu Dec 24, 2020 2:53 pm, edited 1 time in total.
 
biomesh
Long time Member
Long time Member
Posts: 561
Joined: Fri Feb 10, 2012 8:25 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 2:48 pm

I upgraded the following without any issues:

Crs326-24g-2s+ (with lacp bond), crs317, ccr1009, cap ac, wap ac, hap ac2, hap mini, chr, rb921gs.
 
User avatar
andkar
newbie
Posts: 47
Joined: Tue Aug 11, 2020 9:20 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 3:01 pm

Hi,

Hap AC2 - ok so far.
RB3011 - port flapping (like others noted)

Software QA.needs improvements.
 
staticsafe
just joined
Posts: 6
Joined: Sun Dec 28, 2014 6:42 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 3:45 pm

Time for me to ask again, is the bug with the SFP ports not working fixed in this version?

I really want to upgrade my hAP ac to latest :)
 
shavenne
just joined
Posts: 16
Joined: Wed Dec 11, 2019 4:27 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 4:01 pm

6.48 is the same as rc1 I guess? So this =>
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 seperate vlan) and nothing else.
Any idea what's going wrong?
Tried the same with 6.48rc1 today. Still the same problem :(
Downgraded to 6.47.8 and it works again immediately.
will remain, right??

This is my config:
# dec/24/2020 14:59:11 by RouterOS 6.47.8
# software id = 76F0-EZPJ
#
# model = CRS328-24P-4S+
# serial number = A1A10A614FF6
/interface bridge
add admin-mac=74:4D:28:D3:63:6B auto-mac=no comment=defconf igmp-snooping=yes \
    name=bridge vlan-filtering=yes
/interface ethernet
set [ find default-name=ether1 ] comment=pi.home
set [ find default-name=ether2 ] comment="Kamera Hof"
set [ find default-name=ether5 ] comment="Deep-Thought Intel-Karte"
set [ find default-name=ether6 ] comment=Slow-Thought
set [ find default-name=ether11 ] comment=TV
set [ find default-name=ether13 ] comment=HTPC
set [ find default-name=ether14 ] comment=AV-Receiver
set [ find default-name=ether22 ] comment="Freifunk Hotspot (Hof)"
set [ find default-name=ether23 ] comment=\
    "Unifi AP + plastikschleuder.home (RPi)"
set [ find default-name=ether24 ] comment="WAN LTE"
set [ find default-name=sfp-sfpplus1 ] comment="Zum Keller"
set [ find default-name=sfp-sfpplus2 ] comment="Deep-Thought 10G"
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/user group
set full policy="local,telnet,ssh,ftp,reboot,read,write,policy,test,winbox,passw\
    ord,web,sniff,sensitive,api,romon,dude,tikapp"
add name=prometheus policy="read,winbox,api,!local,!telnet,!ssh,!ftp,!reboot,!wr\
    ite,!policy,!test,!password,!web,!sniff,!sensitive,!romon,!dude,!tikapp"
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=ether6
add bridge=bridge comment=defconf interface=ether7
add bridge=bridge comment=defconf interface=ether8
add bridge=bridge comment=defconf interface=ether9
add bridge=bridge comment=defconf interface=ether10
add bridge=bridge comment=defconf interface=ether11
add bridge=bridge comment=defconf interface=ether12
add bridge=bridge comment=defconf interface=ether13
add bridge=bridge comment=defconf interface=ether14
add bridge=bridge comment=defconf interface=ether15
add bridge=bridge comment=defconf interface=ether16
add bridge=bridge comment=defconf interface=ether17
add bridge=bridge comment=defconf interface=ether18
add bridge=bridge comment=defconf interface=ether19
add bridge=bridge comment=defconf interface=ether20
add bridge=bridge comment=defconf interface=ether21
add bridge=bridge comment=defconf interface=ether22 pvid=31
add bridge=bridge comment=defconf interface=ether23
add bridge=bridge comment=defconf interface=ether24
add bridge=bridge comment=defconf interface=sfp-sfpplus1
add bridge=bridge comment=defconf interface=sfp-sfpplus2
add bridge=bridge comment=defconf interface=sfp-sfpplus3
add bridge=bridge comment=defconf interface=sfp-sfpplus4
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/interface bridge vlan
add bridge=bridge comment="IPv6 only" tagged=sfp-sfpplus1,ether5 vlan-ids=66
add bridge=bridge comment="WAN Freifunk" tagged=\
    sfp-sfpplus1,ether23,ether24,sfp-sfpplus2,ether13,ether10 vlan-ids=12
add bridge=bridge comment="Freifunk Hotspot" tagged=sfp-sfpplus1,ether5 \
    untagged=ether22 vlan-ids=31
add bridge=bridge comment=VoIP tagged=sfp-sfpplus1,ether23,ether24 vlan-ids=21
add bridge=bridge comment="WAN FTTH1" tagged=sfp-sfpplus1,ether17 vlan-ids=4001
add bridge=bridge comment="WAN FTTH2" tagged=sfp-sfpplus1,ether17 vlan-ids=4002
add bridge=bridge comment="WWW \FCber bridge-pi" tagged=sfp-sfpplus1,ether17 \
    vlan-ids=4050
add bridge=bridge comment="Freifunk Hotspot (Balkon)" tagged=\
    sfp-sfpplus1,ether5 vlan-ids=32
add bridge=bridge comment="IPv6 Pool 2" tagged=sfp-sfpplus1,ether5 vlan-ids=67
add bridge=bridge comment="WAN LTE" tagged=sfp-sfpplus1,ether24 vlan-ids=4010
add bridge=bridge comment=IceCC tagged=ether5,sfp-sfpplus1 vlan-ids=530
/ip address
add address=192.168.90.7/24 interface=bridge network=192.168.90.0
/ip dns
set servers=192.168.90.1
/ip firewall filter
add action=accept chain=output
add action=accept chain=input
/ip route
add distance=1 gateway=192.168.90.1
/system clock
set time-zone-name=Europe/Berlin
/system identity
set name=SW_WohnungOben
/system ntp client
set enabled=yes primary-ntp=62.108.36.235 secondary-ntp=46.165.221.137
/system package update
set channel=testing
/system routerboard settings
set boot-os=router-os
/system swos
set address-acquisition-mode=static allow-from-ports="p1,p2,p3,p4,p5,p6,p7,p8,p9\
    ,p10,p11,p12,p13,p14,p15,p16,p17,p18,p19,p20,p21,p22,p23,p24,p25,p26,p27,p28\
    " identity=SW_WohnungOben static-ip-address=192.168.90.7
(exported from v6.47.8)
 
jcmerg
just joined
Posts: 2
Joined: Sat Apr 07, 2018 6:28 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 4:09 pm

Same Issue here, i've removed all lacp bonding interfaces from the bridge, after that, the switch worked fine, so i downgraded to the last 6.47.x

I've also tried a factory reset and reconfiguration with a export backup .... same issue.
Ahh. I have 3 LACP bonds on mine. I may well be having the same issue then.

Though how did you remove the bonds if the interfaces where not showing?
Simply unplug all bond members and boot the switch, the issue occures only when the bond interfaces in the bridge are up and active
 
guruniverse
just joined
Posts: 1
Joined: Fri Oct 25, 2019 10:57 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 4:18 pm

Did not receive SMS messages in inbox after upgrade anymore. Downgrading to previous stable version (6.46.8) fixed the issue.

Running a RBLTAP-2HND&R11E-LTE (MMIPS architecture).
 
nostromog
Member Candidate
Member Candidate
Posts: 226
Joined: Wed Jul 18, 2018 3:39 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 5:22 pm

What's new in 6.48 (2020-Dec-22 11:20):
(...)
*) interface - fixed pwr-line running state (introduced in v6.45);
Difficult to know what this means, can anyone clarify?

A couple of pwr-line power sources for a couple of mAP Lite routers have stopped a strange behaviour they were showing, flashing all lights in a ~10 seconds pattern (that I had already reported months ago) and was waiting for feedback more than one month ago. Last they sent me a firmware that made disappear the interface...

It is still not working with 6.48, though, even with both pwr-line adaptors in the same extension cord they don't link together... But now at least the behaviour doesn't look broken, just no traffic across the wire...
 
bmatic
just joined
Posts: 20
Joined: Fri Oct 21, 2016 8:40 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 5:32 pm

hem after upgrade system health not showing voltage and temperature RB 750G r3 Image
I can confirm the problem on RB750Gr3 and RB760iGS .
 
mikruser
Long time Member
Long time Member
Posts: 578
Joined: Wed Jan 16, 2013 6:28 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 5:45 pm

why are you upgrading to beta-version?
it has been repeatedly said that
"long-term" = Stable
"stable" = Beta
"testing" = Alpha
 
User avatar
dannym
just joined
Posts: 21
Joined: Sat Oct 19, 2013 2:28 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 5:54 pm

This new release "make" my 24.12 day...
Rb2011 works fine after update
Rb941/ Rb931 works fine after update
Rb 4011 and 3011 are down...
Last stable releases are total mess.
 
User avatar
rushlife
Member Candidate
Member Candidate
Posts: 243
Joined: Thu Nov 05, 2015 12:30 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 6:07 pm

rb3011 flapping, 1500 linkdowns for about 30 minutes

rb4011 seems to be fine
 
Guscht
Member Candidate
Member Candidate
Posts: 236
Joined: Thu Jul 01, 2010 5:32 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 6:27 pm

What are "Port Extensions"?
Image

No single word in any Mikrotik wiki...
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 6:37 pm

What are "Port Extensions"

No single word in any Mikrotik wiki...
Hi
You could find useful info here:
https://help.mikrotik.com/docs/display/ ... t+Extender
 
FurfangosFrigyes
newbie
Posts: 43
Joined: Sun Feb 25, 2018 11:45 am

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 7:15 pm

- RB3011 port flapping
- CRS328 24p 4s+ crashed if the device has bonded interfaces

- RB4011 ok
- CAP AC ok
- HAP AC3 ok
- CHR ok
- HAP AC2 ok
 
deweydb
just joined
Posts: 7
Joined: Mon Dec 14, 2020 10:03 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 7:32 pm

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)
confirmed on our RouterBOARD 3011UiAS
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 10:21 pm

rb3011 flapping, 1500 linkdowns for about 30 minutes

rb4011 seems to be fine
Hi @rushlife
I like to ask you, did you upgrade FW (bios) on your 3011 ?

I ask this because my 3011 is up with v6.48 and it is stable - NULL link down's , all ETH ports 1G, up without problems
but i forgot to update FW (bios), it is still 6.47.8

so now i am afraid to update/reboot because i am remote until next year
 
Ivoshiee
Member
Member
Posts: 483
Joined: Sat May 06, 2006 4:11 pm

Re: v6.48 [stable] is released!

Thu Dec 24, 2020 11:06 pm

Why does a reboot will erase files from the flash? Image file update and erasing that file was a normal, but why some other files need to go?
 
nwa
newbie
Posts: 29
Joined: Sun Aug 17, 2014 3:02 pm

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 12:27 am

this is the reason why you don´t touch an running system on the holidays.... but i do......... my bad...........
3011 is broken, links down... downgrade with trouble... nice.
 
ganewbie
newbie
Posts: 44
Joined: Fri Feb 24, 2012 4:46 pm

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 3:15 am

rb3011 flapping, 1500 linkdowns for about 30 minutes

rb4011 seems to be fine
Hi @rushlife
I like to ask you, did you upgrade FW (bios) on your 3011 ?

I ask this because my 3011 is up with v6.48 and it is stable - NULL link down's , all ETH ports 1G, up without problems
but i forgot to update FW (bios), it is still 6.47.8

so now i am afraid to update/reboot because i am remote until next year
Do not worry,
We had port flapping with a 3011 router that we updated remotely including the firmware was updated.
Not a big deal, we downgraded to 6.47.8 and our client is stable again.
Good luck
 
User avatar
rushlife
Member Candidate
Member Candidate
Posts: 243
Joined: Thu Nov 05, 2015 12:30 pm

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 10:04 am

rb3011 flapping, 1500 linkdowns for about 30 minutes

rb4011 seems to be fine
Hi @rushlife
I like to ask you, did you upgrade FW (bios) on your 3011 ?

I ask this because my 3011 is up with v6.48 and it is stable - NULL link down's , all ETH ports 1G, up without problems
but i forgot to update FW (bios), it is still 6.47.8

so now i am afraid to update/reboot because i am remote until next year
hi, yeah
firmware was also upgraded to 6.48
 
plisken
Forum Guru
Forum Guru
Posts: 2509
Joined: Sun May 15, 2011 12:24 am
Location: Belgium
Contact:

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 10:08 am

*) branding - fixed LCD logo loading from new style branding package;
How can we add a LCD logo? It would be great to add a custom image with our company logo and the Router-Name.
Go to your Mikrotik account,
At the bottom you see other.
Click on branding maker.
Here you can add your logo.
Then you have to load a package into the router.
If this adjustment is loaded in the router.
You can delete it by netinstall. A reset procedure does not delete them.
I wish you a happy holidays and keep it safe.
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 11:43 am

rb3011 flapping, 1500 linkdowns for about 30 minutes

rb4011 seems to be fine
Hi @rushlife
I like to ask you, did you upgrade FW (bios) on your 3011 ?

I ask this because my 3011 is up with v6.48 and it is stable - NULL link down's , all ETH ports 1G, up without problems
but i forgot to update FW (bios), it is still 6.47.8

so now i am afraid to update/reboot because i am remote until next year
hi, yeah
firmware was also upgraded to 6.48
So, i could consider lucky that i forget to update FW (second reboot)
Still working without glitch, all ports on 1G FD, HW Offload, 14 Vlans, 65% port utilization
Was in hurry to replace scripting with " *) ppp - added ipv6-routes parameter to secrets menu" before holidays and now i am hoping that power/UPS will remain until first work day

it was my mistake :(
nice christmas present :(
 
h17
just joined
Posts: 17
Joined: Wed Apr 16, 2014 10:01 pm

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 12:25 pm

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)
I was having same problem on CRS309-1G-8S+. After a while SFP+ port started constantly flapping every few seconds.
Tried with auto-negotiation turned off. No luck. Had to downgrade to v6.47.8.

Surprisingly, v6.48 on CRS305-1G-4S+ works ok (it's at the other end of that flapping link).
 
User avatar
WirtelPL
newbie
Posts: 34
Joined: Sat Nov 11, 2017 11:22 am
Location: Poland

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 1:05 pm

hem after upgrade system health not showing voltage and temperature RB 750G r3 Image
I can confirm the problem on RB750Gr3 and RB760iGS .
RBD53iG-5HacD2HnD - the same bug.
 
stefanosp
Frequent Visitor
Frequent Visitor
Posts: 54
Joined: Tue Mar 01, 2011 1:01 pm
Location: Northern Italy

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 2:42 pm

what 6.48 did to my RBD52G-5HacD2HnD config:
  • resetted both wireless interfaces
  • removed the bridge
  • removed SSTP-client interface
  • ..
too bad for a MT fan.
 
shiyiqiang08
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Wed Dec 05, 2018 7:35 am

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 2:57 pm

@mikrotik
*) arm - added support for automatic CPU frequency stepping for IPQ4018/IPQ4019 devices;
The frequency of automatic adjustment CPU can only be up to 716, but it can be manually adjusted to 896 in routerboard
 
User avatar
Hominidae
Member
Member
Posts: 309
Joined: Thu Oct 19, 2017 12:50 am

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 3:02 pm

...no problems here after upgrading 24hrs ago, for

- RB4011, running capsman
- CRS326-24G-2S+-RM, including bond-Interface, VLANs and SFP+ (AOC connect to RB4011)
- cAP-ac
 
complex1
Frequent Visitor
Frequent Visitor
Posts: 54
Joined: Wed Jan 04, 2017 9:55 pm
Location: NL-NH

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 6:46 pm

Sorry i report a problem with PwrLine. After upgrade to 6.48, my two devices (model PL7411-2nD) don't pair.
After reboot, change settings, more and more.. nothing. Downgrade to long term, all change to ok. Untill 6.47.8 everything works fine.
ps: ether1, pwr-line1, wlan (off) all on bridge-local with no protocol (stp, rstp, etc...).
I am having the exact same problem here.
 
joedoelv
just joined
Posts: 2
Joined: Mon Apr 06, 2020 2:03 pm

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 8:13 pm

After upgrading my 962UiGS-5HacT2HnT from 6.47.8 to 6.48 I have constant troubles with my SIP phone. When switching on or reconfiguring, it connects to my Asterisk and after some minutes disconnects. Also in Asterisk console I see messages "Peer is lagged/ peer is available" every 30 seconds while the phone is registered. Changing keep alive settings on the phone did not help. After downgrading to 6.46.8 all problems disappeared
I've seen same behavior on Gigaset N300A IP after upgrading my mom's 951Ui-2HnD to 6.48
After downgrading to 6.46.8 issue got resolved.
 
Aytishnikcom
just joined
Posts: 6
Joined: Wed Jan 29, 2014 10:14 pm

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 8:43 pm

Red Hat (long-term) = Stable
CentOS (stable) = Stable
Fedora (testing) = Beta
why are you upgrading to beta-version?
it has been repeatedly said that
"long-term" = Stable
"stable" = Beta
"testing" = Alpha
 
sterod
just joined
Posts: 22
Joined: Sat Oct 13, 2018 12:13 am

Re: v6.48 [stable] is released!

Fri Dec 25, 2020 10:44 pm

Did this update break anyone else's pwr line setup? I have a pwr line pro and at the other end of pwr line AP and the link between them is now incredibly unstable. I had to downgrade to 6.47.8 to restore connectivity.
 
jult
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Sat Dec 26, 2020 1:16 am

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 1:33 am

- never mind - using a different PC with netinstall worked.
Last edited by jult on Sat Dec 26, 2020 11:52 pm, edited 1 time in total.
 
netraider
just joined
Posts: 4
Joined: Tue May 31, 2016 9:31 am

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 3:13 am

After upgrading my 962UiGS-5HacT2HnT from 6.47.8 to 6.48 I have constant troubles with my SIP phone. When switching on or reconfiguring, it connects to my Asterisk and after some minutes disconnects. Also in Asterisk console I see messages "Peer is lagged/ peer is available" every 30 seconds while the phone is registered. Changing keep alive settings on the phone did not help. After downgrading to 6.46.8 all problems disappeared
I've seen same behavior on Gigaset N300A IP after upgrading my mom's 951Ui-2HnD to 6.48
After downgrading to 6.46.8 issue got resolved.
Confirm this! The 6.48 dropped all SIP accounts in my gigaset IP phones to offline. Also I got the problems with access to phone`s webinterface. After downgrade to 6.47.8 everithing works fine again
Last edited by netraider on Sat Dec 26, 2020 9:40 am, edited 2 times in total.
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 4:06 pm

Hi all,

I have one spare RB3011 in lab, so I tried to upgrade it to 6.48 to see the problem with port flapping others mention here. So I did:

  • upload ROS 6.48 packages to RB3011 with 6.47.7 (both ROS and firmware)
  • sys reb (ROS upgraded)
  • waited 10 minutes, no port flapping occurred
  • upgraded firmware to 6.48 (sys rou up)
  • sys reb (warm restart)
  • waited 10 minutes, no port flapping occurred
  • sys shut
  • power cycle (cold start)
  • waited 10 minutes, no port flapping occurred

So in my case 6.48 on RB3011 does not (yet?) exhibit the port flapping problem even after cold start (when the new firmware becomes fully effective). But this is a very early box, bought just after 3011's introduction; maybe there are other HW versions of 3011.

Ondrej
 
ganewbie
newbie
Posts: 44
Joined: Fri Feb 24, 2012 4:46 pm

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 4:31 pm

So in my case 6.48 on RB3011 does not (yet?) exhibit the port flapping problem even after cold start (when the new firmware becomes fully effective). But this is a very early box, bought just after 3011's introduction; maybe there are other HW versions of 3011.
Ondrej
In our setup we have 2 WAN ports "ether1 and ether2" and port flapping was present after the upgrade.
Our 3011 is old but maybe not as old as yours it was shipping with firmware 3.41
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 4:34 pm

Now on rekey childs mikrotik send and want proposals without pfs despite pfs-group=ecp521 configured. Similar issue has Windows 7 time ago.
With IKEv2 the pfs group is inherited from phase 1, have a look at dh group in profiles. Perfect forward secret should be used even if set to none in proposals.
Correct me if I am wrong, but I think you should set pfs-group to none in proposals on all devices for IKEv2.
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 4:40 pm

Our 3011 is old but maybe not as old as yours it was shipping with firmware 3.41
Mine is indeed older, factory firmware is 3.27.

Ondrej
 
rpingar
Long time Member
Long time Member
Posts: 592
Joined: Fri May 28, 2004 2:46 pm
Location: Italy

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 4:57 pm

still (6.47.8 too) get ccr2004 crashes on pppoe-clinet interface queue.
No matter what queue's kind, the router crashes.

ticket #[SUP-36923] opened
regards
Ros
 
User avatar
kehrlein
newbie
Posts: 48
Joined: Tue Jul 09, 2019 1:35 am

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 5:24 pm

Upgraded several devices without any issues:
- CRS326-24G-2S+ (with bridge, bonding, VLAN, SFP+)
- CRS112-8P-4S (with bridge, bonding, VLAN, SFP)
- RB750GL
- RB760iGS (HeX S)
 
erlinden
Forum Guru
Forum Guru
Posts: 1900
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 5:35 pm

With IKEv2 the pfs group is inherited from phase 1, have a look at dh group in profiles. Perfect forward secret should be used even if set to none in proposals.
Correct me if I am wrong, but I think you should set pfs-group to none in proposals on all devices for IKEv2.
My current settings:
/ip ipsec profile
add dh-group=modp4096 enc-algorithm=aes-256,aes-128 hash-algorithm=sha512 name=site2site-profile
/ip ipsec peer
add address=x.x.x.x comment=site2site exchange-mode=ike2 name=site2site profile=site2site-profile
/ip ipsec proposal
set [ find default=yes ] enc-algorithms=3des
add auth-algorithms=sha512 enc-algorithms=aes-256-cbc name=site2site-proposal pfs-group=[b]modp4096[/b]
/ip ipsec identity
add comment=site2site peer=site2site
/ip ipsec policy
add comment=site2site dst-address=192.168.60.0/24 peer=site2site proposal=site2site-proposal sa-dst-address=x.x.x.x sa-src-address=0.0.0.0 \
    src-address=192.168.50.0/24 tunnel=yes
Are you referring to the highlighted pfs-group?
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 6:22 pm

Yes, that's what should be set to none IMHO.
Look at first line, dh-group=modp4096 is used for dh in phase 1 and for PFS in phase 2.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 6:48 pm

See this and the following posts from emils about the details:
viewtopic.php?f=2&t=147769#p740153
 
Lemahasta
just joined
Posts: 14
Joined: Wed Dec 30, 2015 9:52 am

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 7:23 pm

After upgrade from 6.47.8 IPSEC-IKEV2 from windows 10 client -> mikrotik CCR 1009 using eap-radius stopped working.

After downgrade everything works fine again. RADIUS sends access-accept, windows client tries connecting for some time than just times out.
No errors in mikrotik. Just doesn't work.

Downgrade to 6.47.8 fixes issue.

IPSEC-IKEV2 using strongswan client (for android) works fine in both versions (6.47.8 and 6.48).
 
mhaluska
just joined
Posts: 22
Joined: Sat Jun 13, 2020 1:20 pm

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 8:29 pm

-- deleted --
Last edited by mhaluska on Wed Feb 03, 2021 9:40 pm, edited 1 time in total.
 
mikelaurense
just joined
Posts: 9
Joined: Mon Dec 03, 2018 9:14 am

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 8:43 pm

After upgrading my 962UiGS-5HacT2HnT from 6.47.8 to 6.48 I have constant troubles with my SIP phone. When switching on or reconfiguring, it connects to my Asterisk and after some minutes disconnects. Also in Asterisk console I see messages "Peer is lagged/ peer is available" every 30 seconds while the phone is registered. Changing keep alive settings on the phone did not help. After downgrading to 6.46.8 all problems disappeared
I've seen same behavior on Gigaset N300A IP after upgrading my mom's 951Ui-2HnD to 6.48
After downgrading to 6.46.8 issue got resolved.
Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 9:13 pm

Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?
What transport do you use for SIP (UDP, TCP, TLS)?
Is the SIP conntrack helper active? (/ip firewall service-port print)
 
erlinden
Forum Guru
Forum Guru
Posts: 1900
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 10:07 pm

Yes, that's what should be set to none IMHO.
Look at first line, dh-group=modp4096 is used for dh in phase 1 and for PFS in phase 2.
Thanks, saved my day! Got it working!!
 
shahani
newbie
Posts: 26
Joined: Wed Jan 02, 2019 11:29 pm

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 11:12 pm

1x CCR1036-12G-4S-149
1x CRS328_24p_4s_rm
1x RB4011iGS+5HacQ2HnD-IN
2x RB2011UiAS-2HnD-IN
1x RB952Ui-5ac2nD
upgrading 60hrs ago without any issues
 
mikelaurense
just joined
Posts: 9
Joined: Mon Dec 03, 2018 9:14 am

Re: v6.48 [stable] is released!

Sat Dec 26, 2020 11:30 pm

Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?
What transport do you use for SIP (UDP, TCP, TLS)?
Is the SIP conntrack helper active? (/ip firewall service-port print)
Transport was set to Automatic, but setting it to UDP only or TCP only doesn't make a difference.
I used to have the SIP helper set to on, disabled it today, but that makes no difference as well.

This setup has been working for years, and only broke today after updating to 6.48. I see no other option than downgrading until this bug is fixed.

[edit]
Downgraded to 6.47.8 and the problem is gone
Last edited by mikelaurense on Sun Dec 27, 2020 1:53 am, edited 1 time in total.
 
sterod
just joined
Posts: 22
Joined: Sat Oct 13, 2018 12:13 am

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 6:42 am

I think the moral to this story is to avoid majors (6.48) and wait until the first minor (6.48.1)
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 9:52 am

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)
I have the same problem with eth1 and eth2 dropping every hour approximately on my RB3011, downgrading solved the problem as well.
Hope this will be corrected
Same here bugtik rb3011
 
Ozon
just joined
Posts: 3
Joined: Wed May 10, 2017 10:30 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 11:47 am

Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?
Same problems with SIP.

Stopped working:
on hAP ac
on hAP lite x2
on RB951G-2HnD

multiple Gigaset device with and without virtual PBX

all lost connection to PBX

Only helped reverting to 6.48.7

Stuck with downgrading hAP ac - shows 13MB used out of 16 MB
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 12:04 pm

I think the moral to this story is to avoid majors (6.48) and wait until the first minor (6.48.1)
Moral of this story:

1. MKT was forced by sales department to release "new" (7b/6b) versions before christmas without testing
2. Never trust blindly and install anything on holiday season
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 12:08 pm

To someone having problems with SIP phones: Could you please check log of the router with ROS 6.48, whether there are unexpected flapping events (link down/up) or not?

Since the linkdowns last between 1 and 2 seconds (as observed in my lab), it could cause "Lagged" state in Asterisk when qualify probe hits the linkdown state. Maybe the problem is more general and not SIP-specific, although SIP qualify probes can detect short communication outages.
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 12:10 pm

Our 3011 is old but maybe not as old as yours it was shipping with firmware 3.41
Mine is indeed older, factory firmware is 3.27.
Finally, my old 3011 started to flap with another NIC connected, so the problem seems to be dependent on connected NIC (or its PHY?) as well.
 
Ozon
just joined
Posts: 3
Joined: Wed May 10, 2017 10:30 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 12:41 pm

To someone having problems with SIP phones: Could you please check log of the router with ROS 6.48, whether there are unexpected flapping events (link down/up) or not?

Since the linkdowns last between 1 and 2 seconds (as observed in my lab), it could cause "Lagged" state in Asterisk when qualify probe hits the linkdown state. Maybe the problem is more general and not SIP-specific, although SIP qualify probes can detect short communication outages.
nope, link is ok.

upd.

downgraded last 2 devices to 6.47.8

@ MTK - never please release new firmware during holidays. Luck that today is weekend, and everybody is out of office. In another way we could get huge problem without all telephone services working.
 
biomesh
Long time Member
Long time Member
Posts: 561
Joined: Fri Feb 10, 2012 8:25 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 2:52 pm

Are these gigaset devices having issues with the lldp med options added?

My asterisk, grandstream, and obihai (polycom) devices all work fine.
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 5:55 pm

With IKEv2 the pfs group is inherited from phase 1, have a look at dh group in profiles. Perfect forward secret should be used even if set to none in proposals.
Correct me if I am wrong, but I think you should set pfs-group to none in proposals on all devices for IKEv2.
Just to clarify, in IKEv2, phase 2 PFS group is not inherited from phase 1. During IKE SA init phase, when phase 1 keying material is negotiated (using group configured at the phase 1 level) and also phase 2 "create child SA" is requested, this time the phase 2 derives its keys from phase 1 keying material, so in this case there's really no need to negotiate PFS group at the phase 2 level (for example Strongswan is quite liberal here and matches proposals from both peers even if their PFS groups don't match).

Different situation is during phase 2 rekeying, when peers are required to have common PFS group, as there's need to negotiate new keys from scratch. Or, if both peers have PFS group unconfigured, rekeying is done based on previously used keying material, lacking advantage of PFS.

Thus, in IKEv2, the PFS group configured at the phase 2 level is used the same way as in IKEv1 except the initial contact.

6.47.8 and 6.48 send different proposals during phase 2 rekey, 6.48 omits the configured PFS group in proposal sent, 6.47.8 includes it (can be seen in Strongswan logs at the other side).

Setting PFS group to none makes the rekeying work with 6.48, although the rekey process is then weaker due to lacking PFS.
 
samasd
just joined
Posts: 8
Joined: Tue Jul 30, 2019 12:37 am

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 8:12 pm

updated all my routers there was a weird problem in one of 750g routers bridge port , all the clients could ping the upper router except the router itself ! had to remove bridge and its ports and add it again, the arp was good and it was working with no problem with 6.47.8
 
zandhaas
Frequent Visitor
Frequent Visitor
Posts: 73
Joined: Tue Dec 11, 2018 11:02 pm
Location: The Netherlands

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 10:04 pm

Upgrade on my 750Gr3 OK Also the system health is showing power and temp
Upgrade on HAP ac2 is also OK
 
Kindis
Member
Member
Posts: 434
Joined: Tue Nov 01, 2011 6:54 pm
Location: Sweden

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 10:23 pm

To someone having problems with SIP phones: Could you please check log of the router with ROS 6.48, whether there are unexpected flapping events (link down/up) or not?

Since the linkdowns last between 1 and 2 seconds (as observed in my lab), it could cause "Lagged" state in Asterisk when qualify probe hits the linkdown state. Maybe the problem is more general and not SIP-specific, although SIP qualify probes can detect short communication outages.
nope, link is ok.

upd.

downgraded last 2 devices to 6.47.8

@ MTK - never please release new firmware during holidays. Luck that today is weekend, and everybody is out of office. In another way we could get huge problem without all telephone services working.
You cannot be serious with this. How are they responsible for anyone deploying this in production just before the holiday's? Testing fine but not actual prod. We freeze all prod equipment around 18th of Dec to 11th of Jan and do not allow any upgrades/changes unless it is an emergency.
If it is this important I recommend you use Long-term instead as they tend to be better in term of version change but always test first.
 
Guscht
Member Candidate
Member Candidate
Posts: 236
Joined: Thu Jul 01, 2010 5:32 pm

Re: v6.48 [stable] is released!

Sun Dec 27, 2020 11:11 pm

hotspot - added support for captive portal advertising using DHCP (RFC7710)
Any information regarding this?
Is there a new option somewhere in the HotSpot section or in the DHCP section? Or is this a "hidden" background feature?
 
Trunkz
just joined
Posts: 5
Joined: Mon Dec 02, 2019 5:44 pm

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 1:51 am

Yes, that's what should be set to none IMHO.
Look at first line, dh-group=modp4096 is used for dh in phase 1 and for PFS in phase 2.
Thats odd - I've got pfs set in phase 2 and the IKEv2 tunnel establishes correctly:
# model = RB4011iGS+5HacQ2HnD
# serial number = xxxx
/ip ipsec profile
add dh-group=ecp521 enc-algorithm=aes-256 name=xxxx
/ip ipsec peer
add address=xxxx/32 exchange-mode=ike2 name=xxxx profile=xxxx
/ip ipsec proposal
add enc-algorithms=aes-256-cbc name=xxxx pfs-group=ecp521
/ip ipsec identity
add peer=xxxx secret=xxxx
/ip ipsec policy
add dst-address=xxxx/24 peer=xxxx proposal=xxxx sa-dst-address=xxxx sa-src-address=xxxx src-address=xxxx/25 tunnel=yes
 
spiritamokk
just joined
Posts: 1
Joined: Fri Jul 01, 2016 12:05 am

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 4:44 am

After upgrading all our routers (mix of different models: CCR, RB1100AHx4 and CHR) bumped into an issue that IPSec tunnels (GRE based) after Phase 1 is expired Phase 2 fails to form. Before upgrade those tunnels were rock solid for the last 3+ years and survived multiple upgrades.

Active peer shows expired and established Phase 1, but new phase is not passing any traffic. Phase 2 is till shows as associated with expired phase 1
https://prntscr.com/wb5rda

On the Phase 2 (Policies) it looks like it doesn't have info on what flow to encrypt.
https://prnt.sc/wb5u4a

Tunnel configuration on both ends is the same and tunnel is built from behind the firewall with dedicated 1:1 NAT on both ends of the tunnel.

/interface gre
add !keepalive name=GRE-VPN-WEST remote-address=XX.XX.XX.XX

/ip ipsec peer
add address=XX.XX.XX.XX/32 name=VPN-WEST-PEER profile=\
"Default EMS PHASE 1"

/ip ipsec policy
add dst-address=XX.XX.XX.XX/32 peer=VPN-WEST-PEER proposal=\
"Default EMS PHASE 2" src-address=YY.YY.YY.YY/32 (public NAT)

/ip ipsec profile
add dh-group=modp6144 enc-algorithm=aes-256 hash-algorithm=sha512 name=\
"Default EMS PHASE 1"

/ip ipsec proposal
set [ find default=yes ] enc-algorithms=aes-192-cbc lifetime=1h
add enc-algorithms=aes-192-cbc lifetime=1h name="Default EMS PHASE 2"

Please help if you experiencing similar issues as I have no idea where to even start troubleshooting.

Thanks
 
valemal
just joined
Posts: 7
Joined: Wed Jul 08, 2020 12:56 am

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 9:42 am

Time for me to ask again, is the bug with the SFP ports not working fixed in this version?

(my MikroTik hAP ac RB962UiGS-5HacT2HnT View this servicedesk in support portal )
 
eddieb
Member
Member
Posts: 305
Joined: Thu Aug 28, 2014 10:53 am
Location: Netherlands

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:00 am

Time for me to ask again, is the bug with the SFP ports not working fixed in this version?

(my MikroTik hAP ac RB962UiGS-5HacT2HnT View this servicedesk in support portal )
Your issue might be depending on the type of SFP you use,
I have 4pc of RB962UiGS-5HacT2HnT with Mikrotik SFP's and they work fine
You should contact support directly ....
 
dg1kwa
just joined
Posts: 19
Joined: Tue Aug 17, 2010 12:32 pm
Location: Monheim

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:06 am

IGMP Snooping not work correct with this release.

4x rb2011, 1x CRS106 and 1x HeX

After some minutes the MDB-table is empthy and the multicast flood to all ports :(

Try different settings, not help.
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:29 am

IGMP Snooping not work correct with this release.

4x rb2011, 1x CRS106 and 1x HeX

After some minutes the MDB-table is empthy and the multicast flood to all ports :(

Try different settings, not help.
No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devices
 
dg1kwa
just joined
Posts: 19
Joined: Tue Aug 17, 2010 12:32 pm
Location: Monheim

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:39 am

IGMP Snooping not work correct with this release.

4x rb2011, 1x CRS106 and 1x HeX

After some minutes the MDB-table is empthy and the multicast flood to all ports :(

Try different settings, not help.
No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devices
I switch igmp snooping on, set version to v3. Then the MDB Table start to filling and 1-2 minute later mdb table is empty and multicast traffic flood to all ports :(

With 6.47.8 was all ok
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:42 am

IGMP Snooping not work correct with this release.

4x rb2011, 1x CRS106 and 1x HeX

After some minutes the MDB-table is empthy and the multicast flood to all ports :(

Try different settings, not help.
No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devices
I switch igmp snooping on, set version to v3. Then the MDB Table start to filling and 1-2 minute later mdb table is empty and multicast traffic flood to all ports :(

With 6.47.8 was all ok
I'm using IGMP version 2
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:47 am

Thats odd - I've got pfs set in phase 2 and the IKEv2 tunnel establishes correctly:
Yes, they establish correctly. But do they rekey without issue? Have a look at your log...
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:52 am

Please help if you experiencing similar issues as I have no idea where to even start troubleshooting.
Have a look above, IPSec issues have been discussed before.
 
Ozon
just joined
Posts: 3
Joined: Wed May 10, 2017 10:30 pm

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 12:23 pm

You cannot be serious with this. How are they responsible for anyone deploying this in production just before the holiday's? Testing fine but not actual prod. We freeze all prod equipment around 18th of Dec to 11th of Jan and do not allow any upgrades/changes unless it is an emergency.
If it is this important I recommend you use Long-term instead as they tend to be better in term of version change but always test first.
Customer is always right. Why customer can't use as it marked as stable?

Anyway i'm in contact with support now, they suggested to turn off LLDP
/ip neighbor discovery-settings set protocol=cdp,mndp

UPD:
this doesn't help
Last edited by Ozon on Mon Dec 28, 2020 3:18 pm, edited 2 times in total.
 
User avatar
strods
MikroTik Support
MikroTik Support
Posts: 1616
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 12:27 pm

osc86, mducharme, dioeyandika, psybernoid, jcmerg, brbsh, elbob2002, R00tKit, nimbo78, andkar, newrealsprl, nostromog, bmatic, rushlife, FurfangosFrigyes, deweydb, nwa, FabioA, ganewbie, h17, WirtelPL, complex1, sterod, ganewbie, kombinat, jwelstead, mafiosa, OndrejHolas - Thank you for your reports. These issues will be resolved in the upcoming RouterOS releases.

tomaskir - Is this on a router that was just reset?
TimothyKoval - What do you mean exactly by "crashes"?
MartijnVdS, staticsafe - Have you reported this to support with more details (supout file, pcap files, etc.)?
guruniverse - Can you please provide a supout file from such a router that would be generated right after the router should have received an SMS?
Ivoshiee - If the device has a directory named "flash" in its file list, then files which you want to be kept after system reboot/power cycle must be stored within it. As anything outside of it is kept within a RAM disk and will be lost upon reboot. Note: this does not include .npk upgrade files as they will be applied by the upgrade process before the system discards the RAM drive content.
IYARINDRA, tabareco, netraider, Lemahasta, mikelaurense, samasd, dg1kwa - Can you please provide supout file to support@mikrotik.com from this problematic router?
ksaa, joedoelv, netraider, Ozon, OndrejHolas - Can you please provide supout file to support support@mikrotik.com if you have not done that already? We are currently looking into this.
stefanosp - Did the router simply rever to the default configuration? Is it possible that the reset button is stuck?
npeca75 - No, this is not why we did release new free RouterOS versions for you.
valemal - To which support ticket do you refer to?
 
User avatar
nithinkumar2000
Member Candidate
Member Candidate
Posts: 157
Joined: Wed Sep 11, 2019 7:42 am
Location: Coimbatore
Contact:

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 1:40 pm

For Delegated-IPv6-Prefix - any chance of adding the feature address-change-immediate-update like in Juniper? https://kb.juniper.net/InfoCenter/index ... id=KB31659

You already are doing RADIUS accounting for the DHCPv6-PD session for a PPPoE tunnel, but it is a different session. The address-change-immediate-update setting causes that Delegated-IPv6-Prefix to be copied to the PPPoE session itself. Then the DHCPv6-PD prefix is linked to the PPPoE session as well in RADIUS rather than only being a separate session.

Same Request from me also....
 
dg1kwa
just joined
Posts: 19
Joined: Tue Aug 17, 2010 12:32 pm
Location: Monheim

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 2:22 pm

osc86, mducharme, dioeyandika, psybernoid, jcmerg, brbsh, elbob2002, R00tKit, nimbo78, andkar, newrealsprl, nostromog, bmatic, rushlife, FurfangosFrigyes, deweydb, nwa, FabioA, ganewbie, h17, WirtelPL, complex1, sterod, ganewbie, kombinat, jwelstead, mafiosa, OndrejHolas - Thank you for your reports. These issues will be resolved in the upcoming RouterOS releases.

tomaskir - Is this on a router that was just reset?
TimothyKoval - What do you mean exactly by "crashes"?
MartijnVdS, staticsafe - Have you reported this to support with more details (supout file, pcap files, etc.)?
guruniverse - Can you please provide a supout file from such a router that would be generated right after the router should have received an SMS?
Ivoshiee - If the device has a directory named "flash" in its file list, then files which you want to be kept after system reboot/power cycle must be stored within it. As anything outside of it is kept within a RAM disk and will be lost upon reboot. Note: this does not include .npk upgrade files as they will be applied by the upgrade process before the system discards the RAM drive content.
IYARINDRA, tabareco, netraider, Lemahasta, mikelaurense, samasd, dg1kwa - Can you please provide supout file to support@mikrotik.com from this problematic router?
ksaa, joedoelv, netraider, Ozon, OndrejHolas - Can you please provide supout file to support support@mikrotik.com if you have not done that already? We are currently looking into this.
stefanosp - Did the router simply rever to the default configuration? Is it possible that the reset button is stuck?
npeca75 - No, this is not why we did release new free RouterOS versions for you.
valemal - To which support ticket do you refer to?
I send already.
Two new information:
1. MDB Table at all router full (more than 1048 entrys from IPv6-address) then next moment it is empthy
2. on one Router I disable IPv6. Now I have only 5 ipv4 address at mdb table at igmp snopping still work

In not use IPv6-Multicast for IP-TV!
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 2:33 pm

I confirm the problem with SIP connections on this firmware.
I have a bundle of Gigaset C610A IP + RBD52G-5HacD2HnD.
Did you bother to read a few posts before your own? It was suggested to disable LLDP and (at least for some users) this fixes the SIP problem with Gigaset phones.
 
valemal
just joined
Posts: 7
Joined: Wed Jul 08, 2020 12:56 am

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 2:39 pm

osc86, mducharme, dioeyandika, psybernoid, jcmerg, brbsh, elbob2002, R00tKit, nimbo78, andkar, newrealsprl, nostromog, bmatic, rushlife, FurfangosFrigyes, deweydb, nwa, FabioA, ganewbie, h17, WirtelPL, complex1, sterod, ganewbie, kombinat, jwelstead, mafiosa, OndrejHolas - Thank you for your reports. These issues will be resolved in the upcoming RouterOS releases.
valemal - To which support ticket do you refer to?
SUP-33662
 
Ozon
just joined
Posts: 3
Joined: Wed May 10, 2017 10:30 pm

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 3:16 pm

ksaa, joedoelv, netraider, Ozon, OndrejHolas - Can you please provide supout file to support support@mikrotik.com if you have not done that already? We are currently looking into this.
done, SUP-37406
 
valemal
just joined
Posts: 7
Joined: Wed Jul 08, 2020 12:56 am

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 4:52 pm

Time for me to ask again, is the bug with the SFP ports not working fixed in this version?

(my MikroTik hAP ac RB962UiGS-5HacT2HnT View this servicedesk in support portal )
Your issue might be depending on the type of SFP you use,
I have 4pc of RB962UiGS-5HacT2HnT with Mikrotik SFP's and they work fine
You should contact support directly ....
The SFP module has been tested on MikroTik RB4011iGS + 5HacQ2HnD-IN and has no such issue. But at the same time, there is a problem in the MikroTik hAP ac RB962UiGS-5HacT2HnT router. therefore, I think that the problem is in the RB962UiGS-5HacT2HnT router
 
spiritamokk
just joined
Posts: 1
Joined: Fri Jul 01, 2016 12:05 am

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 5:52 pm

Please help if you experiencing similar issues as I have no idea where to even start troubleshooting.
Have a look above, IPSec issues have been discussed before.
Thank you, I've read it all but nothing that would cover my case with IKEv1
 
hci
Long time Member
Long time Member
Posts: 674
Joined: Fri May 28, 2004 5:10 pm

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 7:00 pm

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)
Same here on my RB3011. My WAN port was on ether 2 and kept flapping.

Moved it to ether10 and now have a stable WAN connection again but obviously the flapping issue isn't resolved.

Before moving to ether 10 I turned autonegotiation off but no luck.
We experienced port flapping on RB3011 too. Flapped about every 10 seconds or so. Were only using ethernet ports 1 and 10. Moved device in port 10 to port 5 and issue went away. Port 10 was in bridge group with an EoiP tunnel.
 
hatred
just joined
Posts: 21
Joined: Tue Sep 01, 2015 10:23 pm
Location: Belarus, Minsk

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 9:27 pm

DoH related memory leak reported in SUP-31833 is not fixed in this release.
You do not have the required permissions to view the files attached to this post.
Last edited by hatred on Sun Jan 03, 2021 10:14 pm, edited 1 time in total.
 
User avatar
raystream
Frequent Visitor
Frequent Visitor
Posts: 67
Joined: Tue Mar 20, 2018 6:56 pm
Location: Germany
Contact:

Re: v6.48 [stable] is released!

Mon Dec 28, 2020 10:56 pm

Port Flapping on RB3011.
great now i am trying to get around but the suggested workaround is not working for me.

that is not really a stable release.
the statement: improved arm stability is wrong.

never had such a bad update from mikrotik.

will go back to long term version
 
dad2312
Frequent Visitor
Frequent Visitor
Posts: 73
Joined: Sun Nov 17, 2019 12:55 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 12:21 am

Sorry i report a problem with PwrLine. After upgrade to 6.48, my two devices (model PL7411-2nD) don't pair.
After reboot, change settings, more and more.. nothing. Downgrade to long term, all change to ok. Untill 6.47.8 everything works fine.
ps: ether1, pwr-line1, wlan (off) all on bridge-local with no protocol (stp, rstp, etc...).
+1
 
NTESNick
just joined
Posts: 1
Joined: Tue Dec 29, 2020 12:43 am

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 12:51 am

Port Flapping on RB3011.
great now i am trying to get around but the suggested workaround is not working for me.

that is not really a stable release.
the statement: improved arm stability is wrong.

never had such a bad update from mikrotik.

will go back to long term version
Same issues here :(
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 1:12 am

Has anybody tried the LLDP-MED support yet? The only device I have to test with at home is an old antique Cisco 7941 phone, and although it gets the VLAN ID through LLDP-MED, after it connects to the voice VLAN and gets an IP there, it goes back to the main VLAN, then proceeds to flap back and forth between the default VLAN and the voice VLAN specified through LLDP-MED. However, I'm not sure if it is something weird that this old phone is doing, or whether there is actually an issue with the LLDP-MED implementation.

It is a rather simple setup - just an RB4011 with the phone plugged in to one of the ports, no bridge VLAN filtering used, and a voice VLAN on the bridge.
 
netraider
just joined
Posts: 4
Joined: Tue May 31, 2016 9:31 am

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 1:45 am

I confirm the problem with SIP connections on this firmware.
I have a bundle of Gigaset C610A IP + RBD52G-5HacD2HnD. When upgrading to 6.48 started constant disconnections with SIP servers. Unfortunately, the Gigaset C610A IP doesn't provide any additional information about the problems (logs). After downgrading to 6.46.8 everything was normal (as been).
I have exactly the same situation. In Asterisk logs there are disconnections without any reasons and there are no new attempts to reconnects. It looks like Mikrotik is dropping them. Rolling back to previous RouterOS is fully solve the problem.
Also I see a lot of posts about this problem on other network related forums.
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18959
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 1:53 am

) defconf - improved CAP interface bridging;

What does this mean???
 
User avatar
tomaskir
Trainer
Trainer
Posts: 1162
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 2:04 am

tomaskir - Is this on a router that was just reset?

No reset, this was a fully configured router on an older version updated to 6.48 without any changes.
Before and after upgrade an "/export compact" was taken, and these 2 were diff-ed.

This resulted in the changeset you see - looks like the defaults changed in 6.48.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 2:17 am

It is a rather simple setup - just an RB4011 with the phone plugged in to one of the ports, no bridge VLAN filtering used, and a voice VLAN on the bridge.
Update - I figured out the issue. Every minute or so, the router was sending out an LLDP packet to the phone on both the bridge itself (untagged) and the VLAN interface. The packet from the VLAN interface came just after the packet from the bridge itself.

Normally, the extra LLDP packet that is tagged with the VLAN tag wouldn't cause a major issue, but in this case, it seems that MikroTik is for some reason including the LLDP-MED info only in the packet from "bridge" and not in the packet from the "Voice_VLAN" VLAN interface. Presumably, this is to prevent Q-in-Q or something along those lines. The problem is, however, that the phone interprets this tagged LLDP packet with no LLDP-MED voice vlan specified as an indication that there is no voice VLAN. So that makes it go back to the main untagged VLAN. Once it is on the main untagged VLAN, it is only a matter of time until it gets another LLDP packet from "bridge" with LLDP-MED specified, which makes it go back to the voice VLAN. Now that is back on the voice VLAN, it is only a matter of time until it gets an LLDP packet from the voice vlan with LLDP-MED missing, which makes it think there is no voice VLAN and it switches to untagged. This results in the flapping behaviour that I observed.

For now I have worked around this by purposely creating an interface list that excludes the voice VLAN, so that when the phone is on the VLAN, it only receives the one LLDP packet from "bridge" rather than two LLDP packets from both "bridge" and "Voice_VLAN". It seems that because the Voice_VLAN packet arrives slightly after the packet from bridge, the Voice_VLAN packet with missing voice VLAN ID wins, which causes the phone to flap.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 2:57 am

One further update: If I create a second VLAN on the bridge, the phone starts flapping again between untagged and voice vlan tagged. It appears that once it is on the voice vlan, it starts to process any VLAN tagged LLDP packets, even those that are for a completely unrelated VLAN (i.e. it is ignoring the VLAN ID in the tag and just processing LLDP packets tagged for any VLAN). The workaround of using an interface list to prevent this issue then has to include all VLAN interfaces, not just the voice VLAN, otherwise the phone sees the LLDP packet tagged for the other VLAN and decides to switch back to untagged.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 3:43 am

Another issue - the bridging by default forwards LLDP frames from other devices. The issue is that if the VoIP phone receives one of these (and mine has), it will flap back to untagged VLAN since the other device's LLDP frame is missing the LLDP-MED Network Policy VLAN. IMO, it would be ideal if there was a relatively easy way of stopping this. Maybe if bridge VLAN filtering is enabled, it will behave differently (I'm not sure if LLDP/CDP frames from other devices are forwarded when bridge vlan filtering is enabled), but it would be great if this were better documented.

EDIT: I tried enabling bridge vlan filtering, it didn't change anything regarding the behavior of LLDP and CDP. I was able to partially work around the issue by disabling hardware offload on all ports and creating a bridge filter as follows:
/interface bridge filter
add action=drop chain=forward comment="Block LLDP forwarding" mac-protocol=lldp
add action=drop chain=forward comment="Block CDP forwarding" dst-mac-address=01:00:0C:CC:CC:CC/FF:FF:FF:FF:FF:FF
But this is not an obvious solution, and this isn't suitable for the CRS switch line where software bridging is much too slow, and also I'm not sure this will help to prevent CDP/LLDP packets with VLAN tags from being forwarded to other ports. It would be ideal if there was a more comprehensive solution for bridges to prevent the forwarding of LLDP or CDP packets from port to port without having to disable hardware offload to accomplish it.

According to this HPE document, LLDP should not be forwarded from port to port under any circumstances: https://techhub.hpe.com/eginfolib/netwo ... 06s12.html

It would make sense to adjust bridging to behave in a similar way so that LLDP is not forwarded.
 
nevolex
Member Candidate
Member Candidate
Posts: 167
Joined: Mon Apr 20, 2020 1:09 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 9:52 am

Hi guys

@emils

Updated my Audience to 6.48 and secondary wifi 5Ghz band is now not working at all (1733 Mbit/s one) I was using it as my primary network not as mesh

Please see that some setting are now missing for the band 5500 (1733 wirelss network compare to regular 5ghz)

Please fix

https://ibb.co/q1KcY6j
 
dbeyzade
just joined
Posts: 23
Joined: Sat Jan 06, 2018 11:11 am

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 11:07 am

Testing the new Delegated-IPv6-Prefix via PPPoE software version 6.48

First PPPoE authentication is successful - prefix is assigned from RADIUS

When a second user dials up. There is an error:

could not add dhcpv6 server with pool : server with such name already exists (7)

This seems to stem from the fact the dynamically created DHCPv6 server has no name. Any ideas?
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 11:51 am

LLDP should not be forwarded from port to port under any circumstances
Agreed. AFAIK, special L2 control protocols (especially those using multicast addresses 01-80-C2-00-00-00 to 01-80-C2-00-00-0F), including LLDP, are intended to be "bridge-to-bridge" and their frames should not be forwarded in any case.

Since LLDP provides information about physical port and its capabilities, LLDP encapsulated in frame with 802.1Q VLAN tag makes no sense and can have unexpected results on buggy or incomplete LLDP implementations.

LLDP(-MED) implementation in ROS is very basic from configuration perspective. No control over TLVs sent, no control over accepting LLDP frames (security policy in some organizations require switches to only transmit basic information to identify ports and discard any discovery information received), no support for multiple voice VLANs on single box, no support for additional media VLANs (signalling, video etc.).
 
Trunkz
just joined
Posts: 5
Joined: Mon Dec 02, 2019 5:44 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 1:51 pm

Thats odd - I've got pfs set in phase 2 and the IKEv2 tunnel establishes correctly:
Yes, they establish correctly. But do they rekey without issue? Have a look at your log...
You are right. SA expires before rekey. Set pfs to none and will monitor..
 
likaon
just joined
Posts: 1
Joined: Sat Dec 26, 2020 9:45 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 1:59 pm

Updating the hap AC2 device went quickly and well.

whether this update was intended to fix an Accesspoint problem and fix getting IP with wireless clients. I'm saying that I have two Accesspoint TL-WA854RE and asus rp-ac5 devices that cannot broadcast IP.
 
tomislav91
Member
Member
Posts: 303
Joined: Fri May 26, 2017 12:47 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 2:42 pm

Trusted checkbox appears twice in Bridge -> Ports -> <interface> -> General
What that use for?
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 2:57 pm

DoH related memory leak reported in SUP-31833 is not fixed in this release.
Hmm, you can guess from the graph when I turned on DoH!!
Open space at the end is when I upgraded to 6.48 and you see memory goes up after upgrade as well.
memory.jpg
You do not have the required permissions to view the files attached to this post.
Last edited by Jotne on Tue Dec 29, 2020 4:14 pm, edited 1 time in total.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26287
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 3:04 pm

I fixed upload permissions for this section, you can now attach files again
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18959
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 3:21 pm

Jotne, thanks for sharing your near death experience graph from the hospital. ;-)
 
Heavy
just joined
Posts: 2
Joined: Mon Dec 21, 2020 6:59 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 3:29 pm

Port flapping on RB3011 for me too after upgrade to 6.48, i've just opened a support ticket to send the supout file
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 4:17 pm

DoH Turned off, so will see after some days if memory stabilise it self.

@Normis. Thanks, Image uploaded :)
 
staticsafe
just joined
Posts: 6
Joined: Sun Dec 28, 2014 6:42 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 6:13 pm

Time for me to ask again, is the bug with the SFP ports not working fixed in this version?

(my MikroTik hAP ac RB962UiGS-5HacT2HnT View this servicedesk in support portal )
Your issue might be depending on the type of SFP you use,
I have 4pc of RB962UiGS-5HacT2HnT with Mikrotik SFP's and they work fine
You should contact support directly ....
The SFP module has been tested on MikroTik RB4011iGS + 5HacQ2HnD-IN and has no such issue. But at the same time, there is a problem in the MikroTik hAP ac RB962UiGS-5HacT2HnT router. therefore, I think that the problem is in the RB962UiGS-5HacT2HnT router

I am on a hAP AC, the SFP is ALCATELLUCENT G010SP.

Last time I upgraded from v6.46.6, the SFP interface doesn't get link. I can't replace the SFP with a different one as I believe Bell Canada locks the connection to the specific SFP they provide (if I'm incorrect, somebody let me know because then I can try a Mikrotik or other SFP).

AFAIK, Mikrotik is aware of this issue already, it was reported them a while back when 6.47 was first released.
 
shavenne
just joined
Posts: 16
Joined: Wed Dec 11, 2019 4:27 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 6:31 pm

6.48 is the same as rc1 I guess? So this =>
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 seperate vlan) and nothing else.
Any idea what's going wrong?
Tried the same with 6.48rc1 today. Still the same problem :(
Downgraded to 6.47.8 and it works again immediately.
will remain, right??

This is my config:
# dec/24/2020 14:59:11 by RouterOS 6.47.8
# software id = 76F0-EZPJ
#
# model = CRS328-24P-4S+
# serial number = A1A10A614FF6
/interface bridge
add admin-mac=74:4D:28:D3:63:6B auto-mac=no comment=defconf igmp-snooping=yes \
    name=bridge vlan-filtering=yes
/interface ethernet
set [ find default-name=ether1 ] comment=pi.home
set [ find default-name=ether2 ] comment="Kamera Hof"
set [ find default-name=ether5 ] comment="Deep-Thought Intel-Karte"
set [ find default-name=ether6 ] comment=Slow-Thought
set [ find default-name=ether11 ] comment=TV
set [ find default-name=ether13 ] comment=HTPC
set [ find default-name=ether14 ] comment=AV-Receiver
set [ find default-name=ether22 ] comment="Freifunk Hotspot (Hof)"
set [ find default-name=ether23 ] comment=\
    "Unifi AP + plastikschleuder.home (RPi)"
set [ find default-name=ether24 ] comment="WAN LTE"
set [ find default-name=sfp-sfpplus1 ] comment="Zum Keller"
set [ find default-name=sfp-sfpplus2 ] comment="Deep-Thought 10G"
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/user group
set full policy="local,telnet,ssh,ftp,reboot,read,write,policy,test,winbox,passw\
    ord,web,sniff,sensitive,api,romon,dude,tikapp"
add name=prometheus policy="read,winbox,api,!local,!telnet,!ssh,!ftp,!reboot,!wr\
    ite,!policy,!test,!password,!web,!sniff,!sensitive,!romon,!dude,!tikapp"
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=ether6
add bridge=bridge comment=defconf interface=ether7
add bridge=bridge comment=defconf interface=ether8
add bridge=bridge comment=defconf interface=ether9
add bridge=bridge comment=defconf interface=ether10
add bridge=bridge comment=defconf interface=ether11
add bridge=bridge comment=defconf interface=ether12
add bridge=bridge comment=defconf interface=ether13
add bridge=bridge comment=defconf interface=ether14
add bridge=bridge comment=defconf interface=ether15
add bridge=bridge comment=defconf interface=ether16
add bridge=bridge comment=defconf interface=ether17
add bridge=bridge comment=defconf interface=ether18
add bridge=bridge comment=defconf interface=ether19
add bridge=bridge comment=defconf interface=ether20
add bridge=bridge comment=defconf interface=ether21
add bridge=bridge comment=defconf interface=ether22 pvid=31
add bridge=bridge comment=defconf interface=ether23
add bridge=bridge comment=defconf interface=ether24
add bridge=bridge comment=defconf interface=sfp-sfpplus1
add bridge=bridge comment=defconf interface=sfp-sfpplus2
add bridge=bridge comment=defconf interface=sfp-sfpplus3
add bridge=bridge comment=defconf interface=sfp-sfpplus4
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/interface bridge vlan
add bridge=bridge comment="IPv6 only" tagged=sfp-sfpplus1,ether5 vlan-ids=66
add bridge=bridge comment="WAN Freifunk" tagged=\
    sfp-sfpplus1,ether23,ether24,sfp-sfpplus2,ether13,ether10 vlan-ids=12
add bridge=bridge comment="Freifunk Hotspot" tagged=sfp-sfpplus1,ether5 \
    untagged=ether22 vlan-ids=31
add bridge=bridge comment=VoIP tagged=sfp-sfpplus1,ether23,ether24 vlan-ids=21
add bridge=bridge comment="WAN FTTH1" tagged=sfp-sfpplus1,ether17 vlan-ids=4001
add bridge=bridge comment="WAN FTTH2" tagged=sfp-sfpplus1,ether17 vlan-ids=4002
add bridge=bridge comment="WWW \FCber bridge-pi" tagged=sfp-sfpplus1,ether17 \
    vlan-ids=4050
add bridge=bridge comment="Freifunk Hotspot (Balkon)" tagged=\
    sfp-sfpplus1,ether5 vlan-ids=32
add bridge=bridge comment="IPv6 Pool 2" tagged=sfp-sfpplus1,ether5 vlan-ids=67
add bridge=bridge comment="WAN LTE" tagged=sfp-sfpplus1,ether24 vlan-ids=4010
add bridge=bridge comment=IceCC tagged=ether5,sfp-sfpplus1 vlan-ids=530
/ip address
add address=192.168.90.7/24 interface=bridge network=192.168.90.0
/ip dns
set servers=192.168.90.1
/ip firewall filter
add action=accept chain=output
add action=accept chain=input
/ip route
add distance=1 gateway=192.168.90.1
/system clock
set time-zone-name=Europe/Berlin
/system identity
set name=SW_WohnungOben
/system ntp client
set enabled=yes primary-ntp=62.108.36.235 secondary-ntp=46.165.221.137
/system package update
set channel=testing
/system routerboard settings
set boot-os=router-os
/system swos
set address-acquisition-mode=static allow-from-ports="p1,p2,p3,p4,p5,p6,p7,p8,p9\
    ,p10,p11,p12,p13,p14,p15,p16,p17,p18,p19,p20,p21,p22,p23,p24,p25,p26,p27,p28\
    " identity=SW_WohnungOben static-ip-address=192.168.90.7
(exported from v6.47.8)
Tested it now with the final 6.48. Problem still persists. Sniffed with wireshark now: The only packets I'm getting are the MNDP from my router.
Can somebody tell me if it's a bug or not? Or is it just working 'by accident' with old versions and I have misconfigured something?! Doesn't seem like that actually.

/edit: It begins to work again if I disable IGMP snooping. So something is wrong with IGMP/MLD snooping I guess??
 
tomislav91
Member
Member
Posts: 303
Joined: Fri May 26, 2017 12:47 pm

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 8:42 pm

Does this affect some Stellaris microcontrollers, because i am having some issue with communication? Maybe some have information?
 
User avatar
evince
Member
Member
Posts: 353
Joined: Thu Jul 05, 2012 12:11 pm
Location: Harzé - Belgique
Contact:

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 10:43 pm

*) branding - fixed LCD logo loading from new style branding package;
How can we add a LCD logo? It would be great to add a custom image with our company logo and the Router-Name.
Go to your Mikrotik account,
At the bottom you see other.
Click on branding maker.
Here you can add your logo.
Then you have to load a package into the router.
If this adjustment is loaded in the router.
You can delete it by netinstall. A reset procedure does not delete them.
I wish you a happy holidays and keep it safe.
Thank you, it helped me :-)

By the way, is there any solution to fix it as default screen? The goal is to display only a logo.

Thank you in advance :)
 
benoitc
Member Candidate
Member Candidate
Posts: 169
Joined: Wed Jul 08, 2020 12:33 am

Re: v6.48 [stable] is released!

Tue Dec 29, 2020 11:27 pm

RouterOS version 6.48 has been released in public "stable" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.48 (2020-Dec-22 11:20):

*) arm - added support for automatic CPU frequency stepping for IPQ4018/IPQ4019 devices;
*) arm - improved system stability;
*) arm - improved watchdog and kernel panic reporting in log after reboots on IPQ4018/IPQ4019 devices;
*) arm64 - improved reboot reason reporting in log;
*) bgp - fixed VPNV4 RD byte order;
*) bonding - added LACP monitoring;
*) branding - fixed LCD logo loading from new style branding package;
*) bridge - added "multicast-router" monitoring value for bridge interface;
*) bridge - added fixes and improvements for IGMP and MLD snooping;
*) bridge - added minor fixes and improvements for IGMP snooping with HW offloading;
*) bridge - added warning message when port is disabled by the BPDU guard;
*) bridge - allow to exclude interfaces from extended ports;
*) bridge - automatically remove extended interfaces when deleting PE device from CB;
*) bridge - correctly filter packets by L2MTU size;
*) bridge - correctly remove dynamic VLAN assignment for bridge ports;
*) bridge - fixed "multicast-router" setting on bridge enable;
*) bridge - fixed MDB entry removal when using bridge port "fast-leave" property;
*) 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 link-local multicast forwarding when IGMP snooping and HW offloading is enabled;
*) bridge - fixed local MAC address removal from host table when deleting bridge interface;
*) bridge - fixed multicast table printing;
*) bridge - improved BPDU guard logging;
*) bridge - increased multicast table size to 4K entries;
*) bridge - show "H" flag for extended bridge ports;
*) bridge - show error when switch do not support controlling bridge or port extension;
*) bridge - use "frame-types=admit-all" by default for extended bridge ports;
*) cap - fixed L2MTU setting from CAPsMAN;
*) certificate - clear challenge password on renew;
*) certificate - fixed CRL URL length limit;
*) certificate - fixed private key verification for CA certificate during signing process;
*) certificate - generate CRL even when CRL URL not specified;
*) certificate - properly flush expired SCEP OTP entries;
*) chr - fixed SSH key import on Azure;
*) chr - fixed VLAN tagged packet transmit on bridge for Hyper-V installations;
*) chr - improved interface loading on startup on XEN;
*) chr - improved system stability when changing flow control settings on e1000;
*) cloud - improved backup generation process;
*) conntrack - automatically reduce connection tracking timeouts when table is full;
*) console - allow "once" parameter for bonding monitoring;
*) crs3xx - added initial Bridge Port Extender support;
*) crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - added switch-cpu port VLAN filtering (switch-cpu port is now mapped with bridge interface VLAN membership when vlan-filtering is enabled);
*) crs3xx - correctly filter packets by L2MTU size;
*) crs3xx - fixed "custom-drop-packet" and "not-learned" switch stats for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed "mirror-source" property on switch port disable for CRS305, CRS326-24G-2S+, CRS328, CRS318 devices;
*) crs3xx - fixed "storm-rate" traffic limiting for switch-cpu port on CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed "switch-cpu" VLAN membership on bridge disable;
*) crs3xx - fixed CDP packet forwarding for CRS305, CRS318, CRS326-24G-2S+, CRS328 devices;
*) crs3xx - fixed duplicate host entries when creating static switch hosts;
*) 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 switch "copy-to-cpu" property for CRS305, CRS318, CRS326-24G-2S+, CRS328 devices;
*) crs3xx - fixed switch "not-learned" stats for CRS305, CRS326-24G-2S+, CRS328-24P-4S+, CRS328-4C-20S-4S+, CRS318 devices;
*) crs3xx - improved system stability on CRS354 devices;
*) crs3xx - improved system stability when receiving large frames for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (introduced in v6.47.5);
*) defconf - fixed default configuration loading on RBcAP-2nD and RBwAP-2nD;
*) defconf - fixed static IP address setting in case default configuration loading fails;
*) defconf - improved CAP interface bridging;
*) defconf - improved default configuration generation on devices with non-default wireless interface names;
*) detnet - fixed malformed dummy DHCP User Class option;
*) detnet - use MAC address from bridge interface instead of slave port;
*) dhcp - fixed DHCP packet forwarding to IPsec policies;
*) dhcpv4-server - improved "client-id" value parsing;
*) dhcpv6 server - added support for "Delegated-IPv6-Prefix" for PPP services;
*) dhcpv6-server - added ability to generate binding on first request;
*) dhcpv6-server - added support for "option18" and "option37" for RADIUS managed clients;
*) dhcpv6-server - allow loose static binding "pool" parameter (introduced in v6.46.8);
*) dhcpv6-server - make sure that calling station ID always contains DUID;
*) discovery - added "lldp-med-net-policy-vlan" property for assigning VLAN ID;
*) discovery - allow choosing which discovery protocol is used;
*) 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 - send the same "Chassis ID" on all interfaces for LLDP packets;
*) discovery - use interface MAC address when sending MNDP from slave port;
*) disk - fixed external EXT3 disk mounting on x86 systems;
*) dns - added IPv6 support for DoH;
*) dns - do not use type "A" for static entries with unspecified type;
*) dns - end ongoing queries when changing DoH configuration;
*) dns - fixed listening for DNS queries when only dynamic static entries exist (introduced in v6.47);
*) dot1x - accept priority tagged (VLAN 0) EAP packets on dot1x client;
*) dot1x - fixed reauthentication after server rejects a client into VLAN;
*) dot1x - fixed unicast destination EAP packet receiving when a client is running on a bridge port;
*) dude - fixed configuration menu presence on ARM64 devices;
*) export - fixed RouterBOARD USB "type" parameter export;
*) filesystem - fixed repartition on RB4011 series devices;
*) filesystem - fixed repartition on non-first partition;
*) 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 - added support for captive portal advertising using DHCP (RFC7710);
*) hotspot - fixed "html-directory" parameter export;
*) hotspot - improved management service stability when receiving bogus packets;
*) ike1 - fixed "my-id=address" parameter usage together with certificate authentication;
*) ike1 - fixed 'rsa-signature-hybrid' authentication method;
*) ike1 - fixed memory leak on multiple CR payloads;
*) 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 - added support for IKEv2 Message Fragmentation (RFC7383);
*) ike2 - fixed EAP MSK length validation;
*) ike2 - fixed too small payload parsing;
*) ike2 - improved EAP message integrity checking;
*) ike2 - improved child SA rekeying process;
*) interface - added temperature warning and interface disable on overheat for SFP and SFP+ interfaces (CLI only);
*) interface - fixed pwr-line running state (introduced in v6.45);
*) ipsec - added SHA384 hash algorithm support for phase 1;
*) ipsec - do not kill connection when peer's "name" or "comment" is changed;
*) ipsec - fixed client certificate usage when certificate is renewed with SCEP;
*) ipsec - fixed multiple warning message display for peers;
*) ipsec - inactivate peer's policy on disconnect;
*) ipsec - refresh peer's DNS only when phase 1 is down;
*) kidcontrol - allow creating static device entries without assigned user;
*) led - fixed state persistence after device reboot on NetMetal 5 ac devices;
*) lora - fixed device going into "ERROR" state caused by FSK modulated downlinks;
*) lora - limited output power in RU region for range 868.7 MHz - 869.2 MHz according to regulations;
*) lte - added "age" column and "max-age" parameter to "cell-monitor" (CLI only);
*) lte - added "comment" parameter for APN profiles;
*) lte - added support for Alcatel IK41VE1;
*) lte - fixed "band" value reporting;
*) lte - increased "at+cops" reply timeout to 90 seconds;
*) m33g - added support for "/system gpio" menu (CLI only);
*) metarouter - allow creating RouterOS metarouter instances on devices with 16MB flash storage;
*) metarouter - fixed memory leak when tearing down metarouter instance;
*) ppp - added "bridge-learning" parameter support;
*) ppp - added "ipv6-routes" parameter to "secrets" menu;
*) ppp - added support for "Framed-IPv6-Route" RADIUS attribute;
*) ppp - store "last-caller-id" for PPP secrets;
*) ppp - store "last-disconnect-reason" for PPP secrets;
*) profile - added "lcd" process classificator;
*) 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;
*) route - improved stability when 6to4 interface is configured with disabled IPv6 package;
*) 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;
*) snmp - fixed value types for "dot1dStp";
*) snmp - fixed value types for "dot1qPvid";
*) ssh - fixed returned output saving to file when "output-to-file" parameter is used;
*) ssh - skip interactive authentication when not running in interactive mode;
*) supout - added bonding interface monitor information;
*) supout - improved autosupout.rif file generation process;
*) timezone - updated timezone information from "tzdata2020d" release;
*) tr069-client - added "X_MIKROTIK_MimoRSRP" parameter for LTE RSRP value reporting;
*) tr069-client - added LTE model and revision parameters;
*) tr069-client - added additional wireless registration table parameters;
*) tr069-client - added branding package build time parameter;
*) tr069-client - added wireless "noise-floor" and "overall-tx-ccq" information parameters;
*) tr069-client - allow passing LTE firmware update URL as XML;
*) tr069-client - fixed RouterOS downgrade procedure;
*) tr069-client - fixed TotalBytesReceived parameter value;
*) tr069-client - send correct "ConnectionRequestURL" when using IPv6;
*) traffic-flow - added "sys-init-time" parameter support;
*) traffic-flow - added NAT event logging support for IPFIX;
*) traffic-generator - fixed 32Gbps limitation;
*) user-manager - do not allow creating limitation that crosses midnight;
*) user-manager - updated PayPal's root certificate authorities;
*) webfig - allow hiding QuickSet mode selector;
*) webfig - allow hiding and renaming inline buttons;
*) webfig - fixed default value presence when creating new entries under "IP/Kid Control";
*) webfig - properly stop background processes when switching away from QuickSet tab;
*) winbox - added "src-mac-address" parameter under "IP/DHCP-Server/Leases" menu;
*) winbox - added missing IGMP Snooping settings to "Bridge" menu;
*) winbox - added missing MSTP settings to "Bridge" menu;
*) winbox - added support for LTE Cell Monitor;
*) winbox - allow adding bonding interface with one slave interface;
*) winbox - allow performing "USB Power Reset" on "0" bus on RBM33G;
*) winbox - do not show "network-mode" parameter for LTE interfaces that do not support it;
*) winbox - fixed "IP->Kid Control->Devices" table automatic refreshing;
*) winbox - fixed "interface" and "on-interface" parameter presence under "Bridge/Hosts" menu;
*) winbox - fixed "receive-errors" setting persistence under "Wireless/Wireless Sniffer/Settings" menu;
*) winbox - fixed "tls-version" parameter setting under "IP/Services" menu;
*) winbox - fixed minor typo in "Users" menu;
*) winbox - provide sane default values for bridge "VLAN IDs" parameter;
*) winbox - use health values reported by gauges for "System/Health" menu;
*) wireless - added U-NII-2 support for US and Canada country profiles for mANTBox series devices;
*) wireless - create "connect-list" rule when address specified for "setup-repeater";
*) wireless - do not override MTU and ARP values from CAPsMAN with local forwarding;
*) wireless - improved WPS process stability;
*) wireless - increased "group-key-update" maximum value to 1 day;
*) wireless - updated "indonesia5" regulatory domain information;
*) wireless - updated "no_country_set" regulatory domain information;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this particular RouterOS release.
with this release fans on the CRS312-4C+8XG-RM are running at max :/ any idea how ic an reduce the speed?
 
acidvenom
just joined
Posts: 14
Joined: Thu Aug 14, 2014 9:12 pm

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 12:05 am

RB3011 - ports 6-10 flapping every 5 seconds.
IKEv2 policy problem with "no generate" option. Server drops random connection if there are 2 IKEv2 tunnels from single client IP address.
 
spiritamokk
just joined
Posts: 1
Joined: Fri Jul 01, 2016 12:05 am

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 4:46 am

Please help if you experiencing similar issues as I have no idea where to even start troubleshooting.
Have a look above, IPSec issues have been discussed before.
Downgraded from "Stable" 6.48 to Long-Term 6.46.8 and IPSec IKEv1 issues disappeared. I guess I was just lucky not getting problems for 3 years, so no more "Stable" releases for me. Will stick to less "feature rich" upgrades =)
 
Heavy
just joined
Posts: 2
Joined: Mon Dec 21, 2020 6:59 pm

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 12:29 pm

i've received a reply from the support, they solve the 3011 port flapping on the next 6.48.xx
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 12:56 pm

DoH does definitely have a memory problem. After turning it off for one day, this is how my memory logs looks like on my hEX.
Support case created. SUP-37699
.
memory2.jpg
You do not have the required permissions to view the files attached to this post.
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

LLDP on RB941-2nD

Wed Dec 30, 2020 1:46 pm

Also noticed that after upgrade to 6.48 the hAP lite (RB941-2nD - smips) stopped transmitting LLDP frames (neither periodic nor after receiving MED probe from phone), although it still processes received LLDP frames (discovered phones are visible in /ip nei pr); all three discovery protocols are enabled, MNDP and CDP frames are transmitted, but not LLDP.

6.47.8 with the same configuration transmits periodic LLDP frames as expected.
 
CTSsean
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Fri Sep 15, 2017 12:56 pm

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 3:07 pm

I think the moral to this story is to avoid majors (6.48) and wait until the first minor (6.48.1)
Moral of this story:

1. MKT was forced by sales department to release "new" (7b/6b) versions before christmas without testing
2. Never trust blindly and install anything on holiday season
only a narcissist would say this.
 
Lemahasta
just joined
Posts: 14
Joined: Wed Dec 30, 2015 9:52 am

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 6:39 pm

After upgrade from 6.47.8 IPSEC-IKEV2 from windows 10 client -> mikrotik CCR 1009 using eap-radius stopped working.

After downgrade everything works fine again. RADIUS sends access-accept, windows client tries connecting for some time than just times out.
No errors in mikrotik. Just doesn't work.

Downgrade to 6.47.8 fixes issue.

IPSEC-IKEV2 using strongswan client (for android) works fine in both versions (6.47.8 and 6.48).
Error I'm getting on mikrotik is:
invalid MSK length

I suppose that's caused by the patch note:
*) ike2 - fixed EAP MSK length validation;

I don't know, doesn't seem fixed if standard windows 10 client is now invalid, but worked before.
Changing on windows client EAP from EAP-PEAP to EAP-MSCHAP2 fixes ("=>EAP MSK (size 0x20))" is in debug. But this setting is not preferred.
You do not have the required permissions to view the files attached to this post.
 
tesme33
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Mon May 26, 2014 10:25 pm

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 9:40 pm

Hi
just want to add some information to the Multicast related discussions.
Upgraded my CRS326 to 6.48 and MDB was not filling. Enabling Multicast snooping (which was disabled) --> MDB was filling.
But still no Multicast traffic going through. How do i know ?
Easy answer my SatIP setup is no longer working. The clients no longer see the SatIP server.

[admin@CRS326] /system routerboard> print
                ;;; Firmware upgraded successfully, please reboot for changes
                    to take effect!
       routerboard: yes
             model: CRS326-24G-2S+
     serial-number: 94550966B962
     firmware-type: dx3230L
  factory-firmware: 6.42.7
  current-firmware: 6.47.8
  upgrade-firmware: 6.48

[admin@CRS326] /interface bridge> print
Flags: X - disabled, R - running
 0 R name="bridge" mtu=auto actual-mtu=1500 l2mtu=1592 arp=enabled
     arp-timeout=auto mac-address=B8:69:F4:8D:F3:76 protocol-mode=none
     fast-forward=yes igmp-snooping=yes multicast-router=temporary-query
     multicast-querier=no startup-query-count=2 last-member-query-count=2
     last-member-interval=1s membership-interval=4m20s querier-interval=4m15s
     query-interval=2m5s query-response-interval=10s
     startup-query-interval=31s250ms igmp-version=2 mld-version=1 auto-mac=no
     admin-mac=B8:69:F4:8D:F3:76 ageing-time=5m vlan-filtering=no
     dhcp-snooping=no


[admin@CRS326] /interface bridge mdb> print
GROUP                                                VID PORTS      BRIDGE
239.255.255.250                                          sfp-sfp... bridge
                                                         ether23...
                                                         sfp-sfp...
                                                         ether3
                                                         ether1 ...
                                                         ether9 ...
                                                         ether12...
                                                         ether19...
ff02::fb                                                 ether1 ... bridge
                                                         ether12...
Last edited by tesme33 on Thu Dec 31, 2020 9:37 am, edited 1 time in total.
 
techdude
just joined
Posts: 1
Joined: Mon Oct 08, 2018 2:38 pm

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 10:12 pm

Applied the 6.48 on my CRS354 in my fully functional environment. After i could not access the device and it created loops so the entire network went down until i turned the CRS354 off. I'm running MSTP that was working 100% in 6.47.8. After downgrade back to 6.47.8 everything works. I run two bonding interfaces with 802.3ad that works in 6.47.8, i suspect the loops could be related to those but i haven't had time to do more testing as it cost me a few hours just to fix this downgrade and troubleshoot. I will wait until a more stable release before i try again, i might configure the device from scratch next time to see whats causing issues.
 
MikeRoTik
just joined
Posts: 21
Joined: Wed Jul 08, 2020 4:47 am

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 11:01 pm

m33g - added support for "/system gpio" menu (CLI only);



Could we please, please, please have the documentation for the RBM33G Header and instructions on how to trigger the gpio pins as inputs? (Pull up, pull down, resistor?, etc...)

Did I say PLEASE?
 
tesme33
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Mon May 26, 2014 10:25 pm

Re: v6.48 [stable] is released!

Wed Dec 30, 2020 11:41 pm

After reboot and new firmware it is working.
Lets see if it stops after some time. As mentioned in a post before.


[admin@CRS326] /system routerboard> print
       routerboard: yes
             model: CRS326-24G-2S+
     serial-number: 94550966B962
     firmware-type: dx3230L
  factory-firmware: 6.42.7
  current-firmware: 6.48
  upgrade-firmware: 6.48
Hi
just want to add some information to the Multicast related discussions.
Upgraded my CRS326 to 6.48 and MDB was not filling. Enabling Multicast snooping (which was disabled) --> MDB was filling.
But still no Mulricast traffic going through. How do i know ?
Easy answer my SatIP setup is no longer working. The clients no longer see the SatIP server.

[admin@CRS326] /system routerboard> print
                ;;; Firmware upgraded successfully, please reboot for changes
                    to take effect!
       routerboard: yes
             model: CRS326-24G-2S+
     serial-number: 94550966B962
     firmware-type: dx3230L
  factory-firmware: 6.42.7
  current-firmware: 6.47.8
  upgrade-firmware: 6.48

...
                                                         ether12...
                                                         ether19...
ff02::fb                                                 ether1 ... bridge
                                                         ether12...
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Thu Dec 31, 2020 8:10 am

Found change in logging that was not mention in the DHCP logs.

&MT Please also list these type of changes as well, since my Splunk for Mikrotik did stop showing DHCP logs due to this.
Its positive that you finally have stated to clean up the logs mess :) viewtopic.php?t=124291

Old format
dhcp,debug,packet MikroTik: DHCP-Main received request with id 2264044792 from 192.168.10.230
New format
dhcp,debug MikroTik: DHCP-Main received request id 212743147 from 192.168.10.230 '1:c4:ad:34:c3:37:xx'
packet is removed and mac added to this log line
MikroTik: is a prefix I have added.

What other logs has changed?
 
User avatar
herger
newbie
Posts: 49
Joined: Tue Aug 18, 2020 2:48 pm

Re: v6.48 [stable] is released!

Thu Dec 31, 2020 2:32 pm

I noticed that when using a CRS317 as Port Controller and a CRS309 as Port Extender, once the link between the two devices fails the Port Controller completely stops forwarding and is not accessible anymore. It stays in the locked up state until the link to the Port Extender is restored. This behavior makes it some what risky to use this new feature but i hope this will be fixed in future versions.
 
TheSirStumfy
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Sun Oct 14, 2018 7:54 pm

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 10:25 am

Really hope they fix the RB3011 finally.

Mine has been flapping for years, I have 2 years of logs to prove it. Some updates ware better some worse, but none fixed it truly.

set X cpu-flow-control=no name="Switch x" does help a bit, but never really went away, just went from many flaps a day to some flaps per week.

Im honestly half way to asking for a refund, since the product just does not work in the current state. It has caused corrupted backups in the past when the flap landed on the backup schedule.
 
Kindis
Member
Member
Posts: 434
Joined: Tue Nov 01, 2011 6:54 pm
Location: Sweden

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 11:05 am

Really hope they fix the RB3011 finally.

Mine has been flapping for years, I have 2 years of logs to prove it. Some updates ware better some worse, but none fixed it truly.

set X cpu-flow-control=no name="Switch x" does help a bit, but never really went away, just went from many flaps a day to some flaps per week.

Im honestly half way to asking for a refund, since the product just does not work in the current state. It has caused corrupted backups in the past when the flap landed on the backup schedule.
I have two 3011 and I have none of these issue. Are your sure it is not the connected devices or cable?

I use to have a flapping issue on my RB750gr3 but after I disabled EEE on the port in the Zyxel switch this issue went away.
 
notToNew
Member Candidate
Member Candidate
Posts: 174
Joined: Fri Feb 19, 2016 3:15 pm

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 11:28 am

I have two 3011 and I have none of these issue. Are your sure it is not the connected devices or cable?

I use to have a flapping issue on my RB750gr3 but after I disabled EEE on the port in the Zyxel switch this issue went away.
same here. IT was not mikrotik. at anotzer location I had serious electrical Problems. I needed to use a special cat2 safety poweradapter to get rid of the Port disconnects.
 
TheSirStumfy
Frequent Visitor
Frequent Visitor
Posts: 90
Joined: Sun Oct 14, 2018 7:54 pm

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 12:06 pm

Hm.. the only thing honestly that could be a problem is a SFP module. Ok thanks for the idea guys, Ill play around with switching if for a different one, perhaps it could be causing problems.. Did not try that, because it works fine.
 
User avatar
zervan
Member
Member
Posts: 329
Joined: Fri Aug 20, 2010 10:43 pm
Location: Slovakia
Contact:

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 12:09 pm

Did this update break anyone else's pwr line setup? I have a pwr line pro and at the other end of pwr line AP and the link between them is now incredibly unstable. I had to downgrade to 6.47.8 to restore connectivity.
Yes, there is a bug at least in PWR-LINE AP: The problem is that interface "pwr-line" is reported as not running despite the fact that it is sending and receiving frames, see the screenshot from WinBox. If the interface is part of bridge, then it is reported as invalid.
You do not have the required permissions to view the files attached to this post.
 
User avatar
Masyanich
Frequent Visitor
Frequent Visitor
Posts: 50
Joined: Mon Jan 21, 2013 8:19 am
Location: Russian province
Contact:

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 1:29 pm

ccr 1016-12g
resetted all ppp secrets after upgrade
this build is a pure disaster
 
erlinden
Forum Guru
Forum Guru
Posts: 1900
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 2:07 pm

I absolute love the wireless improvement I'm experiencing. More stability and higher speeds.

Unfortunately I noticed periodic "link down", strangely enough only between my RB4011 and my CRS112-8P-4S. This is not occurring between the RB4011 and a cAP ac and not between CRS112-8P-4S and the cAP ac and wAP ac. Have not excluded possible cable problems, but on the other hand, I never noticed it on the LTS I was running previously.
Last edited by erlinden on Sat Jan 02, 2021 12:05 am, edited 1 time in total.
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1275
Joined: Tue Jun 23, 2015 2:35 pm

Re: v6.48 [stable] is released!

Fri Jan 01, 2021 11:49 pm

*) ppp - store "last-caller-id" for PPP secrets;

how that one works?
 
randomwalk
just joined
Posts: 10
Joined: Sun Apr 21, 2013 3:40 am
Location: Canada

Re: v6.48 [stable] is released!

Sat Jan 02, 2021 10:21 am

DNS regression after 6.48 update
RB450Gx4
edited --> 6.46.8 (FW 6.46.8) LTS --> 6.47.8 (FW 6.47.8) Stable --> 6.48 (FW 6.47.8) Stable --> 6.46.8 (FW 6.46.8) <--- edited

1. CPU utilization during reboot spiked higher, and stayed high for much longer.
2. RouterOS took 15 min to parse ~83,000 static DNS records at reboot compared to <1 min before.
3. Idle CPU utilization after update increased from 0% to 2%
4. DNS service was unavailable for 15 minutes after reboot.
5. Router downtime ~15 min upon reboot is not acceptable. Compare it to <1 min before.

My configuration includes ~83,000 static DNS records, so I had to downgrade to 6.46.8 LTS.
After downgrade, the CPU utilization went back to normal, with less than 1 minute downtime again.

See some screenshots:
Image
https://pasteboard.co/JHKgyOC.png

Image
https://pasteboard.co/JHKlz5U.png
Last edited by randomwalk on Sun Jan 03, 2021 1:55 am, edited 1 time in total.
 
randomwalk
just joined
Posts: 10
Joined: Sun Apr 21, 2013 3:40 am
Location: Canada

Re: v6.48 [stable] is released!

Sat Jan 02, 2021 10:33 am

we are waiting for 6.48.5 .. stable release is beta channel
Agree, The "stable" channel should be called Beta.
 
DarkNate
Forum Veteran
Forum Veteran
Posts: 997
Joined: Fri Jun 26, 2020 4:37 pm

Re: v6.48 [stable] is released!

Sat Jan 02, 2021 10:44 am

we are waiting for 6.48.5 .. stable release is beta channel
Agree, The "stable" channel should be called Beta.
Although v6.48 is perfectly stable for my RB450Gx4. I agree with you and the other members here.

Eventually, I will be forced to move to a different vendor with a more reliable "stable" channel for patches/updates.
 
complex1
Frequent Visitor
Frequent Visitor
Posts: 54
Joined: Wed Jan 04, 2017 9:55 pm
Location: NL-NH

Re: v6.48 [stable] is released!

Sat Jan 02, 2021 12:30 pm

we are waiting for 6.48.5 .. stable release is beta channel
Agree, The "stable" channel should be called Beta.
Although v6.48 is perfectly stable for my RB450Gx4. I agree with you and the other members here.

Eventually, I will be forced to move to a different vendor with a more reliable "stable" channel for patches/updates.
... or use the Long-term version if you want a more stable version. ;-)
 
acidvenom
just joined
Posts: 14
Joined: Thu Aug 14, 2014 9:12 pm

Re: v6.48 [stable] is released!

Sat Jan 02, 2021 12:42 pm

we are waiting for 6.48.5 .. stable release is beta channel
Agree, The "stable" channel should be called Beta.
Although v6.48 is perfectly stable for my RB450Gx4. I agree with you and the other members here.

Eventually, I will be forced to move to a different vendor with a more reliable "stable" channel for patches/updates.
OK then find equal vendor with handy console, cheap devices with support and a lot of features.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Sat Jan 02, 2021 9:46 pm

6.46.8 LTS --> 6.48 Stable --> 6.46.8 LTS
Did you also upgrade the firmware.
 
randomwalk
just joined
Posts: 10
Joined: Sun Apr 21, 2013 3:40 am
Location: Canada

Re: v6.48 [stable] is released!

Sun Jan 03, 2021 1:22 am

6.46.8 LTS --> 6.48 Stable --> 6.46.8 LTS
Did you also upgrade the firmware.
No i did not upgrade the firmware. The firmware was v6.47.8 (i forgot that I switched to Stable channel ~4 weeks ago.)
Here is my exact (more accurate) update path:
6.46.8 (FW 6.46.8) LTS --> 6.47.8 (FW 6.47.8) Stable --> 6.48 (FW 6.47.8) Stable --> 6.46.8 (FW 6.46.8)
So in the end i rolled back both the firmware and routeros to LTS.

P.S. To mikrotik developers: here is another snapshot some 16 hrs later.
It appears that 6.48 memory usage is better than 6.47.8, but neither can match 6.46.8 which is better in both: CPU and RAM usage
Image
https://pasteboard.co/JHQqX4v.png
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Sun Jan 03, 2021 9:32 am

Image
Do not post link to image. Upload them to the forum use the Attachments button below the post window. It will then stay in the forum.
 
zeek01
just joined
Posts: 9
Joined: Mon May 21, 2018 3:44 pm

Re: v6.48 [stable] is released!

Sun Jan 03, 2021 5:10 pm

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)
My RB3011 has flapping ports on both switch groups (1-5) and (6-10), going to roll back now... if I can work out how!!

IF YOU HAVE AN RB3011 DON'T USE THIS FIRMWRE would be my advice.

Steve
 
elbob2002
Member Candidate
Member Candidate
Posts: 252
Joined: Tue May 15, 2018 8:15 pm
Location: Ireland

Re: v6.48 [stable] is released!

Mon Jan 04, 2021 8:49 am

After upgrading on RB3011 ports in switch group 1 (ether1-5) started flapping every 5 minutes. Rolled back on 6.47.8 and all seems ok. So 3011 users, install with care! ;)

My RB3011 has flapping ports on both switch groups (1-5) and (6-10), going to roll back now... if I can work out how!!

IF YOU HAVE AN RB3011 DON'T USE THIS FIRMWRE would be my advice.

Steve
Copy the correct .npk to your RB3011 using Winbox to Files folder.

https://download.mikrotik.com/routeros/ ... 6.47.8.npk

From the terminal in winbox type
/system package downgrade
 
jakubk2
just joined
Posts: 4
Joined: Mon Jan 04, 2021 10:15 am

Re: v6.48 [stable] is released!

Mon Jan 04, 2021 10:28 am

i can confirm massive connectivity issues with Gigaset phones after upgrading to 6.48

rb962UiGS and Gigaset C430 IP
rb951G-2HnD and Gigaset A690 IP (same issues with A580 IP)

i had to downgrade both routers to 6.46.8. After downgrade everything is working fine again.
 
WildRat
just joined
Posts: 7
Joined: Wed Jul 12, 2017 11:52 am

Re: v6.48 [stable] is released!

Mon Jan 04, 2021 1:24 pm

The hAP ac v6.48 router rebooted today due to an existing memory leak issue:
Image
This problem has been present in several recent stable releases:
Image
This is most likely due to DoH function, because my secondary router wAP ac don't have same problem.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Mon Jan 04, 2021 2:14 pm

This is most likely due to DoH function, because my secondary router wAP ac don't have same problem.
If you did read this thread, you will see that I posted the same here:
viewtopic.php?p=837044#p837044

MT will try to fix it for the next release.
 
randomwalk
just joined
Posts: 10
Joined: Sun Apr 21, 2013 3:40 am
Location: Canada

Re: v6.48 [stable] is released!

Tue Jan 05, 2021 2:44 am

Image
Do not post link to image. Upload them to the forum use the Attachments button below the post window. It will then stay in the forum.
I tried, but don't have the privilege according to forum faq. Thanks anyway.
 
aries
just joined
Posts: 12
Joined: Mon Dec 27, 2010 3:50 pm

Re: v6.48 [stable] is released!

Tue Jan 05, 2021 7:46 pm

Hello,
After upgrading to 6.48, dhcp snooping is not working (blocking dhcp requests) on CRS326-24G-2S+ and CRS305-1G-4S+

Best regards.
 
avggeek
newbie
Posts: 48
Joined: Thu Jun 06, 2013 9:33 am

Re: v6.48 [stable] is released!

Wed Jan 06, 2021 5:45 am

On RB750gr3, Winbox 3.27 does not show any health information in v6.48. However "/system health print" works fine:

Image
 
zandhaas
Frequent Visitor
Frequent Visitor
Posts: 73
Joined: Tue Dec 11, 2018 11:02 pm
Location: The Netherlands

Re: v6.48 [stable] is released!

Wed Jan 06, 2021 10:20 am

On RB750gr3, Winbox 3.27 does not show any health information in v6.48. However "/system health print" works fine:
I have upgraded my RB750GR3 from 6.47.8 to 6.48 and Winbox 3.27 does show system health information.
2021-01-06 09_11_33-Keeper Desktop Applet.png
You do not have the required permissions to view the files attached to this post.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v6.48 [stable] is released!

Wed Jan 06, 2021 12:07 pm

fix port flapping please for 3011 ASAP
 
netraider
just joined
Posts: 4
Joined: Tue May 31, 2016 9:31 am

Re: v6.48 [stable] is released!

Thu Jan 07, 2021 12:19 am

fix port flapping please for 3011 ASAP
And SIP forwarding too
 
imadloo
just joined
Posts: 5
Joined: Wed Dec 12, 2018 9:47 pm

Re: v6.48 [stable] is released!

Thu Jan 07, 2021 8:38 am

Hello

Problem after RB493G update. Mikrotik won't let traffic through and keeps crashing after several hours. Duplicate tested.

Other models such as: RB750Gr3, RB960PGS, RB2011iLS, RB750GL all ok.
 
avggeek
newbie
Posts: 48
Joined: Thu Jun 06, 2013 9:33 am

Re: v6.48 [stable] is released!

Thu Jan 07, 2021 10:12 am


I have upgraded my RB750GR3 from 6.47.8 to 6.48 and Winbox 3.27 does show system health information.

2021-01-06 09_11_33-Keeper Desktop Applet.png
Did you upgrade firmware under "/system routerboard"? I have upgraded mine and I wonder if this is the cause.

Update: It doesn't seem to be an issue with the board firmware. I found that if I downgrade to long-term (6.46.8) the system health option works correctly, even with board firmware at 6.48. Upgrading from there to 6.48 Stable breaks it again. So it's something in the 6.48 packages.

Update #2: Well that's bizzare. I selected the system package and clicked Downgrade. Router rebooted and still shows system package version as 6.48 same as other packages. But now System>Health works in Winbox.
 
zandhaas
Frequent Visitor
Frequent Visitor
Posts: 73
Joined: Tue Dec 11, 2018 11:02 pm
Location: The Netherlands

Re: v6.48 [stable] is released!

Thu Jan 07, 2021 11:10 pm


Did you upgrade firmware under "/system routerboard"? I have upgraded mine and I wonder if this is the cause.
No this time I seemed to have forgotten to upgrade the routerboard firmware. Normaly I do it right after the RouterOS. So this is different to your environment.

For now I wait with the upgrade of the routerboard firmware :)
 
mikrotikedoff
newbie
Posts: 29
Joined: Mon Nov 06, 2017 7:27 pm

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 2:57 am

@Mountaineer

Hello and welcome as I see you are new. With Mikrotik you have to treat LT as "stable", stable as beta, testing as alpha, and beta as experimental. This has been a long term gripe from the community. Please be advised sometimes they release a bad/bugged LT version as well so even that tree cant be 100% depended on. Many people end up bouncing between stable and LT tree depending on which is performing better at a given time. For instance, all my production equipment at the moment is on 6.47.7 stable. They also never remove broken software versions they just add the new release when it becomes available. You'll definitely want to consider investing in some equipment to lab with to test new releases with before deployment.

Best regards,
 
OndrejHolas
newbie
Posts: 29
Joined: Mon Jul 30, 2018 5:54 pm

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 11:30 am

RB750GL with 6.48, directly connected Gigaset A540 IP (with latest firmware 42.248), no problems observed. Also checked with discovery turned on for all interfaces, including LLDP, and cold restart of the VoIP base (to achieve full init). Neither ping losses nor lagged/unreachable messages in Asterisk log (qualifyfreq=11) were detected. SIP uses TCP transport. Maybe A540 IP is too basic model and is not affected by LLDP changes - packet capture is missing LLDP-MED probes from the phone, so it seems that A540 IP does not support LLDP at all.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 5:51 pm

It seems static DNS records of type FWD are ignored once a DoH server is added.
Is this a design decision or a bug? If this is not going to change, we'll never be able to use it, because we need conditional forwarding.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 6:04 pm

It seems static DNS records of type FWD are ignored once a DoH server is added.
Is this a design decision or a bug? If this is not going to change, we'll never be able to use it, because we need conditional forwarding.
It has been this way since DoH has been introduced in 6.47 - see older release threads for details...
There has not been an answer from Mikrotik. I hope this is considered a bug and will be fix. I causes a lot of trouble for me as well.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 6:23 pm

I hope we'll get an official statement from a Mikrotik representative. As a workaround I'm currently forwarding all DNS requests to an OpenBSD machine running unbound, which handels DoH and CF just fine. Would be great if this could be done on the router itself.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 6:28 pm

Best is to open a support ticket with the complains.
I did not for 6.47 - in hope anything happens with the details in release thread...

Will open a ticket myself soon.

I had thought about an extra Raspberry Pi for DNS... But that would be a share for Mikrotik routers.
Also this is not an option for "mobile" devices, for example my hAP ac² or wAP ac LTE I carry in my bag...
 
deliveri
just joined
Posts: 1
Joined: Thu Oct 24, 2019 12:15 am

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 7:32 pm

Hi R00tKit,
we are experiencing similar problems, with CCR1016-12S-1S+ , since upgrade to 6.48 .
SIP packets randomly disappear, mainly Siemens Gigaset A510IP A540 IP A690 IP affected.
But RTP (UDP stream) also affected randomly the uploading (going out to internet) packets losts.

Did you made a rollback from Mikrotik Firmware 6.48 to older one? Does is solve the SIP traffic problem?

Sadly I confirm the problem with Several RB3011. The switch chip of ports 1-5 works erratically after the upgrade.
All my PPPoE connections on those ports (usually 1,2) started flapping.
Switching to ports 6-10 worked for me, but this is kind of serious.

Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS. I think I will revert to the older version for now
 
Kindis
Member
Member
Posts: 434
Joined: Tue Nov 01, 2011 6:54 pm
Location: Sweden

Re: v6.48 [stable] is released!

Fri Jan 08, 2021 8:27 pm

Read in this thread about SIP and workaround.. All is written here.
 
korekvin
just joined
Posts: 1
Joined: Sat Jan 09, 2021 1:44 am

Re: v6.48 [stable] is released!

Sat Jan 09, 2021 1:50 am

I have been pulling my hair over the Pwr-line units I have recently purchased.
6.48 indeed breaks pwr-line communication completely.
Installing long-term 6.46.8 solved the issue.
 
fs89
just joined
Posts: 2
Joined: Mon Jan 11, 2021 9:54 am

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 11:21 am

Hey@ALL

After upgrading to version 6.48, I cannot create a new "bridge" or "ppp" connection.
The URL appears in the browser, but the web interface remains empty.

EXAMPLE:
- http://%IP%/webfig/#PPP.Interface.new.OVPN_Client
- http://%IP%/webfig/#Bridge.Bridge.new

THX for help and feedback
 
si458
Frequent Visitor
Frequent Visitor
Posts: 64
Joined: Fri Jun 22, 2012 7:51 pm
Contact:

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 12:36 pm

Hi R00tKit,
we are experiencing similar problems, with CCR1016-12S-1S+ , since upgrade to 6.48 .
SIP packets randomly disappear, mainly Siemens Gigaset A510IP A540 IP A690 IP affected.
But RTP (UDP stream) also affected randomly the uploading (going out to internet) packets losts.

Did you made a rollback from Mikrotik Firmware 6.48 to older one? Does is solve the SIP traffic problem?

Sadly I confirm the problem with Several RB3011. The switch chip of ports 1-5 works erratically after the upgrade.
All my PPPoE connections on those ports (usually 1,2) started flapping.
Switching to ports 6-10 worked for me, but this is kind of serious.

Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS. I think I will revert to the older version for now
i can confirm if you roll back a software update/firmware update to 6.47.8 it does indeed fix the SIP issue with gigaset handsets
if you pinged the devices the pings would drop out randomly at the same time the sip would drop out,
i had spend a full week onsite at a single site trying to fix this issue (even arranged to purchase new handsets cuz i thought they had broken the phones)
then realizing i had done updates a week prior and after checking the comments here others having the same issue i was, i rolled it back and worked straight away!
i havent tried the DISABLE LLDP that others have suggested using the 6.48 update, but i'm hanging fire upgrading again for now until a new update next month
 
User avatar
R00tKit
just joined
Posts: 9
Joined: Fri Nov 07, 2014 12:24 am

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 1:34 pm


Did you made a rollback from Mikrotik Firmware 6.48 to older one? Does is solve the SIP traffic problem?
Hello. Yes, Going back to the previous version fixed all problems. All we can do for now is rollback and wait for the next version.
 
nostromog
Member Candidate
Member Candidate
Posts: 226
Joined: Wed Jul 18, 2018 3:39 pm

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 1:46 pm

I have been pulling my hair over the Pwr-line units I have recently purchased.
6.48 indeed breaks pwr-line communication completely.
Installing long-term 6.46.8 solved the issue.

Not for my pwrline power sources for mAP Lite. Those were fully broken for a number of releases, and 6.48 seem to have changed the behaviour in a positive sense, but breaking connectivity. I'm waiting for a fix in 6.48, my devices have been broken for several months, and they don't work when downgrading and no response from my support ticket.
 
DmitryT
just joined
Posts: 4
Joined: Wed Oct 03, 2018 11:35 am

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 2:58 pm

two 2011 down, port remapped and updown loop
two 3011 down, port remapped, freezes
HEX works but freezes
 
WiesiDeluxe
just joined
Posts: 6
Joined: Wed Jan 15, 2014 9:04 pm
Location: Austria

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 2:59 pm

Sorry i report a problem with PwrLine. After upgrade to 6.48, my two devices (model PL7411-2nD) don't pair.
After reboot, change settings, more and more.. nothing. Downgrade to long term, all change to ok. Untill 6.47.8 everything works fine.
ps: ether1, pwr-line1, wlan (off) all on bridge-local with no protocol (stp, rstp, etc...).
Same here, switching to long-term channel with v6.46.8 solved the issue with my 3 pwr-line devices.
+1 same here, worked again after downgrade to long term
 
Kiasw
just joined
Posts: 1
Joined: Wed Jul 15, 2020 11:07 pm

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 6:12 pm

rb3011 down, freezes vpn clients.
 
Kiasw
just joined
Posts: 1
Joined: Wed Jul 15, 2020 11:07 pm

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 6:16 pm

Rolling back the firmware to stable 6.46.8 solved the problem. Owners of RB3011 are very careful to upgrade to this version.
 
Kiasw
just joined
Posts: 1
Joined: Wed Jul 15, 2020 11:07 pm

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 6:23 pm

On RB951Ui-2nd, RB941-2nd-OK
 
User avatar
Mainale
just joined
Posts: 1
Joined: Mon Jan 11, 2021 7:31 pm

Re: v6.48 [stable] is released!

Mon Jan 11, 2021 7:37 pm

I see I`m not alone with my issues.
 
Ivoshiee
Member
Member
Posts: 483
Joined: Sat May 06, 2006 4:11 pm

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 12:58 pm

The 60GHz link has still issues with traffic stoppage/link down. I just experienced one to see that the link was still up, but the IP-traffic was sopped. I got the supout.rif file and performed disable/enable on the 60Ghz interface. IP-traffic resumed.
 
hajde
newbie
Posts: 32
Joined: Sat Apr 26, 2008 12:55 am
Location: Sarajevo, Bosna and Hercegovina
Contact:

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 4:09 pm

PL7411-2nD after upgrade, dosnt connect over PCL. 5 devices same situation. Downgrade to 6.47.8 solve problem.
 
kaspi4
just joined
Posts: 2
Joined: Tue Apr 24, 2018 1:33 pm

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 4:14 pm

My 3011 started port flapping on sw6-10 since 6.48 is there any ideas?

/interface ethernet switch set switch2 cpu-flow-control=no Does not help

Image


I have sstp_server_binding (saw someone with same issues on gre tunnel)
Last edited by kaspi4 on Tue Jan 12, 2021 4:31 pm, edited 2 times in total.
 
hajde
newbie
Posts: 32
Joined: Sat Apr 26, 2008 12:55 am
Location: Sarajevo, Bosna and Hercegovina
Contact:

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 4:25 pm

Run on 6.47.8.
 
kaspi4
just joined
Posts: 2
Joined: Tue Apr 24, 2018 1:33 pm

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 4:32 pm

Run on 6.47.8.

Will try, thanks!
 
rb9999
just joined
Posts: 24
Joined: Thu Dec 06, 2018 3:09 pm

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 6:12 pm

Maybe just a stupid question... Due to all the issues in 6.48 wouldn't be better for Mikrotik to recall the release? Remove the link from download site and prevent upgrading to it in /system upgrade.
On another note.. any ETA on a release that will fix the major issues, like port flapping, 60ghz issue, memory leak in doh?
 
User avatar
zelthian
just joined
Posts: 16
Joined: Mon Nov 19, 2018 11:24 pm
Location: Aurora, CO

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 8:44 pm

with this release fans on the CRS312-4C+8XG-RM are running at max :/ any idea how ic an reduce the speed?
I also ran into this issue. I downgraded back to 6.47.8 and the fan behavior returned to "normal".
 
Cray
just joined
Posts: 10
Joined: Fri Sep 27, 2013 12:24 pm

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 9:42 pm

Issues I encountered with various MikroTik models after upgrading to 6.48 [stable]:

  • All devices: webfig always forwards after login to the new "Port Mapping" quickset page. Does not prevent config/usage, but very annoying.
  • All devices: IPSec connectivity issues (Phase 1, Phase 2, PFS - varies)
  • RB3011: ethernet port flapping (5 sec cycle)
  • CRS317: stuck at reboot, some internal services failing to start (constant errors logged), (simple .npk package downgrade does not work because all soft reboots fail!) (5 out of 8 upgraded devices failed like this!)
  • CHR: L2TP/IPSec VPN user authentications fail
  • RB4011: Some wireless clients unable to connect (short connection logged; followed by immediate disconnect)
  • + many more minor stability and random error logging issues

All of these can be resolved by downgrading back to 6.47.8; which I did for the devices under my watch. Out of 50+ devices there were only few which could be considered 100% issue free after 6.48 upgrade.

I'd say 6.48 release has to be recalled. Especially in case of CRS switches, 6.48 can brick devices so that they require manual intervention (factory reset + fw downgrade) and can not be recovered remotely.

Historically RouterOS releases have been rock-solid, but this one seems to be a complete quality assurance disaster to put it mildly.
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2394
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: v6.48 [stable] is released!

Tue Jan 12, 2021 11:15 pm

Maybe just a stupid question... Due to all the issues in 6.48 wouldn't be better for Mikrotik to recall the release? Remove the link from download site and prevent upgrading to it in /system upgrade.
On another note.. any ETA on a release that will fix the major issues, like port flapping, 60ghz issue, memory leak in doh?
A warning in the header would be enough.
Known issues is 6.48: port flapping on rb3011.

Is it so hard to inform users? Just one line ....
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:03 pm

With this release on a hAP mini and using a HP Chromebook as a client on the WiFi, I experience regular "stuttering" of the traffic.
It is not apparent when using TCP connections and services that use a lot of buffering (e.g. Youtube), but when using a UDP stream or a TCP connection with little buffering there are regular cut-outs of up to a second in the connection.
That makes it unusable for e.g. VoIP or some of the meeting software in use in the world today.
While I have seen this happen before on certain combinations of releases and devices, this combination worked fine on 6.47 and is now severely affected on 6.48.
The signal is strong, the devices are only about a meter apart. But the connection appears to stall.
(I used a website that allows to test for packet loss and jitter, and it clearly shows the issue)
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:26 pm

any ideas why upgrade causes full of errors regarding IKE2 rekey?
50+ devices upgraded, with correct setup of PFS groups on both sides, and every 30 minutes - rekey failed, OSPF goes down
You do not have the required permissions to view the files attached to this post.
 
erlinden
Forum Guru
Forum Guru
Posts: 1900
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:29 pm

any ideas why upgrade causes full of errors regarding IKE2 rekey?
search.php?keywords=rekey&t=171035&sf=msgonly
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:37 pm

any ideas why upgrade causes full of errors regarding IKE2 rekey?
search.php?keywords=rekey&t=171035&sf=msgonly
reviewed all this, found some problems, where people was wrong setup and using default proposals, and still no answer - in my case PFS group and proposals are setuped correctly, on both sides.
If on both sides in proposals PFS group is 2048 and lifetime 30, is it a mistake?
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:49 pm

reviewed all this, found some problems, where people was wrong setup and using default proposals, and still no answer - in my case PFS group and proposals are setuped correctly, on both sides.
If on both sides in proposals PFS group is 2048 and lifetime 30, is it a mistake?
Search this thread for pfs-group=, you will find some answers.
 
mikruser
Long time Member
Long time Member
Posts: 578
Joined: Wed Jan 16, 2013 6:28 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:51 pm

Mountaineer
I'm sticking to Long Term for future upgrades to any critical equipment.
Mikrotik is not intended for use in any critical equipment or enterprise. Repeatedly spoken about this, for example viewtopic.php?f=2&t=165391

Why hasn't this release been removed from the downloads page?
because they don't care about user problems
 
Kazek
newbie
Posts: 41
Joined: Mon Feb 12, 2018 12:53 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:54 pm

After upgrading to 6.48 I have two RB3011 with flapping ethernet ports. After downgrade to 6.47.8 the issue does not happen.
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 12:58 pm

reviewed all this, found some problems, where people was wrong setup and using default proposals, and still no answer - in my case PFS group and proposals are setuped correctly, on both sides.
If on both sides in proposals PFS group is 2048 and lifetime 30, is it a mistake?
Search this thread for pfs-group=, you will find some answers.
searched twice. Can you, please, post something more specific?

I have same group in profile and in proposal.
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 1:15 pm

any more specific ideas, regarding that is more that 50 ipsec on the server?

Client side
# jan/13/2021 13:02:56 by RouterOS 6.48
# software id = 1R3H-GDJM
#
# model = RBM33G
# serial number = A2FD0C7A4D0D
/ip ipsec policy group
add name=ikev2-group
/ip ipsec profile
add dh-group=modp2048 enc-algorithm=aes-256 hash-algorithm=sha256 name=ikev2-profile
/ip ipsec peer
add address=XXXXXXXXX exchange-mode=ike2 name=datacenter profile=ikev2-profile
/ip ipsec proposal
add auth-algorithms=sha256 enc-algorithms=aes-256-cbc name=ikev2-proposal pfs-group=modp2048
/ip ipsec identity
add auth-method=digital-signature certificate=XXXXXXX generate-policy=port-strict mode-config=request-only peer=datacenter policy-template-group=ikev2-group
/ip ipsec policy
set 0 group=ikev2-group proposal=ikev2-proposal
Server side is the same exactly
/ip ipsec policy group
add name=ikev2-group
/ip ipsec profile
add dh-group=modp2048 enc-algorithm=aes-256 hash-algorithm=sha256 name=ikev2-profile
/ip ipsec peer
add exchange-mode=ike2 local-address=XXXXXXXX name=ikev2-peer passive=yes profile=ikev2-profile
/ip ipsec proposal
add auth-algorithms=sha256 enc-algorithms=aes-256-cbc name=ikev2-proposal pfs-group=modp2048
/ip ipsec identity
add auth-method=digital-signature certificate=XXXXXX generate-policy=port-strict match-by=certificate mode-config=XXXXXX peer=ikev2-peer policy-template-group=ikev2-group \
    remote-certificate=XXXXXXX
/ip ipsec policy
add dst-address=0.0.0.0/0 group=ikev2-group proposal=ikev2-proposal src-address=0.0.0.0/0 template=yes
 
User avatar
hknet
Member Candidate
Member Candidate
Posts: 126
Joined: Sun Jul 17, 2016 6:05 pm
Location: Vienna, Austria
Contact:

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 2:24 pm

On my CRS326-24G-2S+ after updating I no longer have any interfaces nor will the device reboot cleanly.

This is the output from terminal:
[admin@CRS326] > /interface
[admin@CRS326] /interface> print
Flags: D - dynamic, X - disabled, R - running, S - slave
 #     NAME                                TYPE       ACTUAL-MTU L2MTU
[admin@CRS326] /interface> /system reboot
Reboot, yes? [y/N]:
y
system will reboot shortly

Rebooting...
failed to stop ipsec: std failure: timeout (13)
failed to stop route: std failure: timeout (13)
Same Issue here, i've removed all lacp bonding interfaces from the bridge, after that, the switch worked fine, so i downgraded to the last 6.47.x

I've also tried a factory reset and reconfiguration with a export backup .... same issue.
hit the same problem with CRS317 - had to field-replace as remote-recovery was not possible.... this is bad and support didn't even seem to know about this issue.
 
sindy
Forum Guru
Forum Guru
Posts: 10205
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 3:00 pm

any more specific ideas, regarding that is more that 50 ipsec on the server?
My understanding of the references to pfs-group in the current topic and in the one @eworm refers to (in a post which itself does not contain the keyword pfs) is the following:
  • pfs is always used in IKEv2
  • if you set the pfs-group parameter of proposal to none, the same DH group and the same key used during Phase 1 to establish the first Phase 2 SA is used also for all subsequent rekeyings of the Phase 2 SA
  • if you set the pfs-group parameter of proposal to anything else than none, the configured one was used for rekeyings at least until 6.48; even if the DH-group set in the proposal was the same like in profile (for Phase 1), the key used has been regenerated and used for all the rekeyings; this is possibly breaking the IKEv2 RFC
Hence setting pfs-group in proposal to none at both peers should resolve your issue yet not prevent use of PFS for rekeying if exchange-mode=ike2 is used
Last edited by sindy on Wed Jan 13, 2021 3:07 pm, edited 1 time in total.
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 3:06 pm

any more specific ideas, regarding that is more that 50 ipsec on the server?
My understanding of the references to pfs-group in the current topic and in the one @eworm refers to (in a post which itself does not contain the keyword pfs) is the following:
  • pfs is always used in IKEv2
  • if you set the pfs-group parameter of proposal to none, the same DH group and the same key used during Phase 1 to establish the first Phase 2 SA is used also for all subsequent rekeyings of the Phase 2 SA
  • if you set the pfs-group parameter of proposal to anything else than none, the configured one was used for rekeyings at least until 6.48; even if the DH-group set in the proposal was the same like in profile (for Phase 1), the key used has been regenerated and used for all the rekeyings; this is possibly breaking the IKEv2 RFC
Hence setting pfs-group in proposal to none at both peers should resolve your issue yet not prevent use of PFS for rekeying.
So in my case, when pfs-group is defined on both sides equal to 2048, why there are problems with rekey?
I posted my setup already, and readed a lot of cases, still not clear, if from both sides are the same pfs-group in proposal, what is wrong, or what is the purpose to use this group at all.
Always was thinking, that proposals must be exactly the same, from both sides of ipsec, am i wrong??
 
sindy
Forum Guru
Forum Guru
Posts: 10205
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 3:12 pm

Always was thinking, that proposals must be exactly the same, from both sides of ipsec, am i wrong??
Correct, they must be the same at both sides. However, it seems 6.48 has a problem if you ask it not to use the pfs key from the initial establishment of Phase 2 by specifying a value in pfs-group in proposal (albeit the same one as in dh-group in profile), and that this problem doesn't show up if you set pfs-group to none.
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 3:16 pm

Always was thinking, that proposals must be exactly the same, from both sides of ipsec, am i wrong??
Correct, they must be the same at both sides. However, it seems 6.48 has a problem if you ask it not to use the pfs key from the initial establishment of Phase 2 by specifying a value in pfs-group in proposal (albeit the same one as in dh-group in profile), and that this problem doesn't show up if you set pfs-group to none.
So am i right, that it is not my wrong setup, this is bug of 6.48? Already posted those questions in support, because resetup of more than 50 routers, is a huge work, want to be sure, that changing one side proposal pfs to none will solve this issue.
 
sindy
Forum Guru
Forum Guru
Posts: 10205
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 6:26 pm

Changing it at one peer in a pair only will not solve the issue. It must be changed at both peers. Whether it is a bug introduced or a bug fixed is unclear to me.
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Wed Jan 13, 2021 9:33 pm

Changing it at one peer in a pair only will not solve the issue. It must be changed at both peers. Whether it is a bug introduced or a bug fixed is unclear to me.
downgraded server (CHR) to 6.47.8 and no errors. Will wait for the fix of this.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Thu Jan 14, 2021 12:07 pm

With this release on a hAP mini and using a HP Chromebook as a client on the WiFi, I experience regular "stuttering" of the traffic.
I have downgraded to 6.47.8 and the issue is resolved.
Some more detail: when this problem occurs, the connection appears "dead" for 1-2 seconds every 10-15 seconds or so. The traffic just stops, and when it resumes some (but not all) packets are still delivered but by then are over a second late, so normally useless.
After the downgrade there of course is still some jitter, as always on WiFi when an occasional re-try is required, but those dead stop intervals disappear. It looks like maybe the re-try algorithm or timing has been changed in 6.48 with this unfortunate effect.
 
gutekpl
Frequent Visitor
Frequent Visitor
Posts: 92
Joined: Wed Feb 20, 2019 6:31 pm

Re: v6.48 [stable] is released!

Thu Jan 14, 2021 1:58 pm

hEX PoE lost health info in 6.48
hex.PNG
You do not have the required permissions to view the files attached to this post.
 
rkadmins
just joined
Posts: 5
Joined: Wed Apr 25, 2018 3:35 pm

Re: v6.48 [stable] is released!

Thu Jan 14, 2021 2:00 pm

any more specific ideas, regarding that is more that 50 ipsec on the server?

Client side
# jan/13/2021 13:02:56 by RouterOS 6.48
# software id = 1R3H-GDJM
#
# model = RBM33G
# serial number = A2FD0C7A4D0D
/ip ipsec policy group
add name=ikev2-group
/ip ipsec profile
add dh-group=modp2048 enc-algorithm=aes-256 hash-algorithm=sha256 name=ikev2-profile
/ip ipsec peer
add address=XXXXXXXXX exchange-mode=ike2 name=datacenter profile=ikev2-profile
/ip ipsec proposal
add auth-algorithms=sha256 enc-algorithms=aes-256-cbc name=ikev2-proposal pfs-group=modp2048
/ip ipsec identity
add auth-method=digital-signature certificate=XXXXXXX generate-policy=port-strict mode-config=request-only peer=datacenter policy-template-group=ikev2-group
/ip ipsec policy
set 0 group=ikev2-group proposal=ikev2-proposal
Server side is the same exactly
/ip ipsec policy group
add name=ikev2-group
/ip ipsec profile
add dh-group=modp2048 enc-algorithm=aes-256 hash-algorithm=sha256 name=ikev2-profile
/ip ipsec peer
add exchange-mode=ike2 local-address=XXXXXXXX name=ikev2-peer passive=yes profile=ikev2-profile
/ip ipsec proposal
add auth-algorithms=sha256 enc-algorithms=aes-256-cbc name=ikev2-proposal pfs-group=modp2048
/ip ipsec identity
add auth-method=digital-signature certificate=XXXXXX generate-policy=port-strict match-by=certificate mode-config=XXXXXX peer=ikev2-peer policy-template-group=ikev2-group \
    remote-certificate=XXXXXXX
/ip ipsec policy
add dst-address=0.0.0.0/0 group=ikev2-group proposal=ikev2-proposal src-address=0.0.0.0/0 template=yes
Got the response from support - this is a BUG, will be fixed in next version of RouterOS
 
User avatar
Chaosphere64
Frequent Visitor
Frequent Visitor
Posts: 94
Joined: Wed Aug 10, 2016 10:19 pm

Re: v6.48 [stable] is released!

Thu Jan 14, 2021 9:52 pm

hEX PoE lost health info in 6.48
hex.PNG
I can confirm that and add the fact that this has to do with firmware 6.48. RouterOS 6.48 with Firmware 6.47.8 on a hEX PoE has health info as it should.
 
leonardogyn
just joined
Posts: 18
Joined: Wed Dec 04, 2019 4:47 pm

Re: v6.48 [stable] is released!

Thu Jan 14, 2021 11:05 pm

Have tried on different mikrotik boxes, different browsers, and got the same result with all of them: with 6.48, using the web interface, I cannot create new VLANs anymore with Interfaces/VLAN/Add New. Clicking on the "Add New" button changes the URL to "#Interfaces.VLAN.new" and nothing happens. From Interfaces, interface tab, select Add New, choose VLAN on the dropdown menu, the new VLAN screen is presented (with a different URL, now "#Interfaces.Interface.new.VLAN", but always gives "Couldn't add New Interface - unsupported device type (6)" when creating a new one.

With winbox, everything is OK and working as expected. From the web interface, however, I could not create new VLANs at all on 6.48.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.48 [stable] is released!

Fri Jan 15, 2021 11:41 pm

I can confirm that and add the fact that this has to do with firmware 6.48. RouterOS 6.48 with Firmware 6.47.8 on a hEX PoE has health info as it should.
And it's still available in CLI...
 
zsolna
just joined
Posts: 6
Joined: Tue Nov 05, 2013 10:08 pm

Re: v6.48 [stable] is released!

Sun Jan 17, 2021 12:09 pm

After upgrade to 6.48 lost the neighbours.

/interface bridge add fast-forward=no name=br_bone protocol-mode=none pvid=999 vlan-filtering=yes
/interface bridge port add bridge=br_bone frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=sfp2-uplink
/interface bridge vlan add bridge=br_bone tagged=sfp2-uplink vlan-ids=999

=> /interface bridge vlan> print
# BRIDGE VLAN-IDS CURRENT-TAGGED CURRENT-UNTAGGED
0 br_bone 999 sfp2-uplink br_bone

/interface list add name=admin
/interface list member add interface=br_bone list=admin
/ip neighbor discovery-settings set discover-interface-list=admin

We use 4 same CRS326, with same config, the uplink port is the sfp2. All sfp2 connected to a CRS317 (with same bridge config, like the CRS326 for all SFP).
Before the upgrade, over VLAN 999, the discovery worked without any problem.

Any idea?

I tried
- interface list set to all
- turn on/off LLDP
 
nwa
newbie
Posts: 29
Joined: Sun Aug 17, 2014 3:02 pm

Re: v6.48 [stable] is released!

Sun Jan 17, 2021 12:27 pm

is downgrade to long term still the only way to fix the fails with all my rb2011 ?
why the firmware is still available? its broken and has to stop the rollout.
i don't remember that mt handle his problems like that in all the years...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Sun Jan 17, 2021 12:30 pm

is downgrade to long term still the only way to fix the fails with all my rb2011 ?
why the firmware is still available? its broken and has to stop the rollout.
i don't remember that mt handle his problems like that in all the years...
It often goes like this when a new test version is promoted to stable.
As an end-user, remember never upgrade to a 6.xx version when it becomes the new stable, wait for the 6.xx.1 or 6.xx.2 version.
And look in the forum to see how well that is being received.
 
acidvenom
just joined
Posts: 14
Joined: Thu Aug 14, 2014 9:12 pm

Re: v6.48 [stable] is released!

Sun Jan 17, 2021 2:18 pm

is downgrade to long term still the only way to fix the fails with all my rb2011 ?
why the firmware is still available? its broken and has to stop the rollout.
i don't remember that mt handle his problems like that in all the years...
Upload necessary files of v6.47.8 and click "Downgrade" in section "Packages". Check FW after reboot and do not upgrade teel next release.
 
User avatar
LucZWFM
Member Candidate
Member Candidate
Posts: 130
Joined: Tue Dec 26, 2017 10:47 pm
Location: Bergen op Zoom, The Netherlands

Re: v6.48 [stable] is released!

Sun Jan 17, 2021 6:44 pm

For me PPP is broken on a RB 2011, RB3011 and a RB941.
Anyone with the same issue?
 
jebz
Member
Member
Posts: 366
Joined: Sun May 01, 2011 12:03 pm
Location: Australia

Re: v6.48 [stable] is released!

Mon Jan 18, 2021 10:56 am

%UserProfile%\AppData\Roaming\Mikrotik\Winbox
lists 6.48rc2 as the folder for ROS 6.48 data files.
 
Ivoshiee
Member
Member
Posts: 483
Joined: Sat May 06, 2006 4:11 pm

Re: v6.48 [stable] is released!

Tue Jan 19, 2021 10:49 pm

As a general rule then for the MT the select releases are usable and avoid using too large set of "supported" set of functions - one of then shall be broken, granted. Thus I've removed MT from the center of my network and using them only as access devices. Even there are issues, always.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.48 [stable] is released!

Wed Jan 20, 2021 12:58 am

Thus I've removed MT from the center of my network and using them only as access devices. Even there are issues, always.
As you're in 6.48 discussion topic, looks like you don't use long-term release channel...
 
Ivoshiee
Member
Member
Posts: 483
Joined: Sat May 06, 2006 4:11 pm

Re: v6.48 [stable] is released!

Wed Jan 20, 2021 10:44 am

Thus I've removed MT from the center of my network and using them only as access devices. Even there are issues, always.
As you're in 6.48 discussion topic, looks like you don't use long-term release channel...
Majority of my boxes are on v6.36.3 and the v6.48 is set for the 60GHz devices, in hope of the radiolink stability, but it is still failing on that.
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v6.48 [stable] is released!

Wed Jan 20, 2021 7:41 pm

SNMP -> Trap send report an error
/snmp send-trap oid=2.1.1.1 type=integer value=1
log:
error - contact MikroTik support and send a supout file (3)

trap are sent, and correctly received
host: UDP: [169.254.2.2]:59262->[169.254.101.212]:162
ip:   UDP: [169.254.2.2]:59262->[169.254.101.212]:162
.1.3.6.1.2.1.1.3.0 => 25:21:53:43.98
.1.3.6.1.6.3.1.1.4.1.0 => .1.3.6.1.4.1.14988.1.1.9.0.1
.2.1.1.1 => 1
but there is a big RED line in Log
script error: error - contact MikroTik support and send a supout file (3)
 
icsterm
Frequent Visitor
Frequent Visitor
Posts: 58
Joined: Sun Mar 11, 2018 11:11 pm

Re: v6.48 [stable] is released!

Fri Jan 22, 2021 3:40 pm

Waiting patienly for the next "beta" release, the DoH memory leak is painful, every few days my hap ac2 needs restart because the 256MB of RAM is not enough, it sometime eats 10MB per hour, this didn't happen when 6.48 was beta (actual release branch).
 
RiccardoM
just joined
Posts: 1
Joined: Tue Nov 13, 2018 8:39 pm

Re: v6.48 [stable] is released!

Sat Jan 23, 2021 1:31 pm

Hi R00tKit,
we are experiencing similar problems, with CCR1016-12S-1S+ , since upgrade to 6.48 .
SIP packets randomly disappear, mainly Siemens Gigaset A510IP A540 IP A690 IP affected.
But RTP (UDP stream) also affected randomly the uploading (going out to internet) packets losts.

Did you made a rollback from Mikrotik Firmware 6.48 to older one? Does is solve the SIP traffic problem?

Sadly I confirm the problem with Several RB3011. The switch chip of ports 1-5 works erratically after the upgrade.
All my PPPoE connections on those ports (usually 1,2) started flapping.
Switching to ports 6-10 worked for me, but this is kind of serious.

Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS. I think I will revert to the older version for now
i can confirm if you roll back a software update/firmware update to 6.47.8 it does indeed fix the SIP issue with gigaset handsets
if you pinged the devices the pings would drop out randomly at the same time the sip would drop out,
i had spend a full week onsite at a single site trying to fix this issue (even arranged to purchase new handsets cuz i thought they had broken the phones)
then realizing i had done updates a week prior and after checking the comments here others having the same issue i was, i rolled it back and worked straight away!
i havent tried the DISABLE LLDP that others have suggested using the 6.48 update, but i'm hanging fire upgrading again for now until a new update next month
I experienced the same SIP problem with my Siemens handsets A540, went back to 6.47.8 to fix the problems, spent about 4 hours troubleshooting, I have logged a support call with mikrotik,
hopefully others will also log faults to prioritize the fix
 
User avatar
boldsuck
Frequent Visitor
Frequent Visitor
Posts: 60
Joined: Sun Sep 01, 2013 1:07 am
Location: Germany

Re: v6.48 [stable] is released!

Sat Jan 23, 2021 3:39 pm

Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS.
My Gigaset could no longer register with my provider. Disable MNDP solved the problem.
Gigaset C450 IP + RB2011UAS works here with:
/ip neighbor discovery-settings set protocol=cdp
or
/ip neighbor discovery-settings set protocol=cdp,lldp
 
User avatar
Nevon
Frequent Visitor
Frequent Visitor
Posts: 72
Joined: Thu Sep 05, 2013 6:06 pm
Location: Sweden
Contact:

Re: v6.48 [stable] is released!

Mon Jan 25, 2021 10:10 am

Updated our CRS328-4C-20S and CRS326-24S+ and we got problem that randomly freezing connectivity in the network. We notised it by SIP stream and other UDP services that disconnected.
Downgraded to 6.47.8 and no problem notised yet..
 
acidvenom
just joined
Posts: 14
Joined: Thu Aug 14, 2014 9:12 pm

Re: v6.48 [stable] is released!

Mon Jan 25, 2021 7:52 pm

So it's been a month. Any ETA so far?
 
User avatar
TosLin
just joined
Posts: 2
Joined: Tue Sep 25, 2018 11:01 am

Re: v6.48 [stable] is released!

Tue Jan 26, 2021 9:26 am

Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS.
My Gigaset could no longer register with my provider. Disable MNDP solved the problem.
Gigaset C450 IP + RB2011UAS works here with:
/ip neighbor discovery-settings set protocol=cdp
or
/ip neighbor discovery-settings set protocol=cdp,lldp
This solution works.
 
Cray
just joined
Posts: 10
Joined: Fri Sep 27, 2013 12:24 pm

Re: v6.48 [stable] is released!

Tue Jan 26, 2021 9:48 am

It is unbelievable that this release has not been pulled already or fixed version released for a full month.

6.48 breaks so many features on so many different MikroTik device models that it must have a dramatic effect on new customers and new devices being installed.

Most of the posts in this forum talk about RB3011 port flapping issues, but nobody seems to notice that 6.48 (nearly-)bricks CRS3xx devices, breaks VPNs, breaks IPSec tunneling, causes issues with wireless connectivity - and list goes on - on wide range of MikroTik models. Only commonality is that all of these issues can be mitigated by downgrading to 6.47.8. I've encountered these issues first-hand on installed customer devices and not only by reading other peoples posts.

For pro users it is not difficult to analyze the issue and downgrade, but I'm worried about new non-pro buyers who upgrade their new devices. Plus in CRS3xx case downgrade requires manual on-site intervention due to 6.48 reboot bug.

Wake up MikroTik! Issue some kind of statement, pull the release or release wide-ranging fix asap!
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.48 [stable] is released!

Tue Jan 26, 2021 9:50 am

Thinkpad T480s with Windows 10 and Intel Dual Band 8265 (2x2 AC): Lower throughput with cAP ac running v6.48 either 2.4 or 5.0GHz => Back to v6.46.8.
 
shavenne
just joined
Posts: 16
Joined: Wed Dec 11, 2019 4:27 pm

Re: v6.48 [stable] is released!

Tue Jan 26, 2021 2:19 pm

It is unbelievable that this release has not been pulled already or fixed version released for a full month.
I'm new to Mikrotik and I've changed many devices in my network quite (too) fast. Now I'm quite shocked what's called stable here. I'm even not seeing a warning or similar that this release .. well ... sucks basically. Which 'normal user' looks in this forum before he upgrades to this version?!
Not pulling it back, no real statement, and also not giving any ETA seems all very intransparent. Makes me afraid that I totally made the wrong choice.
 
hatred
just joined
Posts: 21
Joined: Tue Sep 01, 2015 10:23 pm
Location: Belarus, Minsk

Re: v6.48 [stable] is released!

Tue Jan 26, 2021 6:02 pm

No one promised that using MikroTik would be easy. Only in struggle network engineer is born.
 
markwien
Frequent Visitor
Frequent Visitor
Posts: 69
Joined: Sun Jul 22, 2018 10:49 am

Re: v6.48 [stable] is released!

Tue Jan 26, 2021 6:16 pm

this realease was not able to perform basic layer 1 features. ARP issues - outage. i had to downgrade to 6.47 now all services are back up.

Mikrotik please test your software!!!
 
Cray
just joined
Posts: 10
Joined: Fri Sep 27, 2013 12:24 pm

Re: v6.48 [stable] is released!

Wed Jan 27, 2021 1:55 am

I'm new to Mikrotik and I've changed many devices in my network quite (too) fast. Now I'm quite shocked what's called stable here. I'm even not seeing a warning or similar that this release .. well ... sucks basically. Which 'normal user' looks in this forum before he upgrades to this version?!
Not pulling it back, no real statement, and also not giving any ETA seems all very intransparent. Makes me afraid that I totally made the wrong choice.

I do not believe that you made wrong choice with MikroTik - but I admit that the situation with 6.48 quality is highly unusual for them. I've been using MikroTik devices professionally for the past decade and have never seen anything like this.

In my experience stable releases have been issue free and generally safe to upgrade as-is. In the case of 6.48 this assumption was wrong - very much so.

As usual, I upgraded lot of devices remotely to "the latest stable" only to scramble to do remote and on-site downgrades as soon as possible due to wide range of connectivity and stability issues that followed. Angry mob calmed and lessons learned.

However, if you want to see how great MikroTik really is (and it is), use 6.47.8 for now. This new release line does not (yet) represent my personal positive experience with MikroTik.
 
acidvenom
just joined
Posts: 14
Joined: Thu Aug 14, 2014 9:12 pm

Re: v6.48 [stable] is released!

Wed Jan 27, 2021 7:37 am

I'm using MT's for past 7 years. VPNs, OSPF, IKEv2, NV2, etc. So much in a box for $40? And a human console? MT is my choice.
Something is broken from release to release, upgrade carefully, grab backup to your computer.
If you need anything MORE stable - go to Zyxel with their zyfwp.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.48 [stable] is released!

Wed Jan 27, 2021 6:38 pm

If you need anything MORE stable - go to Zyxel with their zyfwp.
but keep in mind that you share your admin account with anyone on the internet
 
acidvenom
just joined
Posts: 14
Joined: Thu Aug 14, 2014 9:12 pm

Re: v6.48 [stable] is released!

Wed Jan 27, 2021 8:47 pm

osc86, exactly!
 
Kindis
Member
Member
Posts: 434
Joined: Tue Nov 01, 2011 6:54 pm
Location: Sweden

Re: v6.48 [stable] is released!

Wed Jan 27, 2021 9:52 pm

If you need anything MORE stable - go to Zyxel with their zyfwp.
but keep in mind that you share your admin account with anyone on the internet
zyfwp is the hard coded account so I think a joke was made here 😁
 
CharlyBrown
just joined
Posts: 10
Joined: Tue Jul 17, 2018 7:12 pm

Re: v6.48 [stable] is released!

Wed Jan 27, 2021 10:33 pm

Hi guys..
The feature AUTOUPGRADE doesn't work from 6.47 version.
It may be a good time to rethink this option and be able to use a repository installed on a local server.
In my case, I have many devices on a private network that are not connected to the internet, and it is quite cumbersome to update them manually.
Remote update from DUDE also doesn't work properly and when it fails it removes the packages.

This feature is very usefull, when try to upgrade the devices through a script and don't have Internet connection in remote sites.

Thanks for read.
best regards.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Thu Jan 28, 2021 12:14 pm

I think the AUTOUPGRADE feature (Auto Upgrade under the System menu) has been orphaned long ago.
There is barely any documentation for it.
Instead, the /system package update (with check-for-updates, download and install subcommands) is suggested.
Of course the disadvantage is that it will download from MikroTik servers only, it cannot download from some local repository where you keep your own preferred versions.
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.48 [stable] is released!

Thu Jan 28, 2021 1:01 pm

I'm using MT's for past 7 years. VPNs, OSPF, IKEv2, NV2, etc. So much in a box for $40? And a human console? MT is my choice.
[...]
Mikrotik´s RouterOS is like a Swiss knife. So many different tools.
Of course I can use it to saw a tree. But in most cases it will be better to just use a chainsaw.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.48 [stable] is released!

Thu Jan 28, 2021 7:28 pm

Maybe I'm doing something wrong, but the "contains" filter option doesn't work with "Data" in IP -> DNS -> Cache. If you don't put in the full string you won't get any results. But I guess this is what the "is" option is for.
I only discovered this, because a few minutes ago, adguard handed out their own IP Addresses for Domains they don't own.
Example:
CleanShot 2021-01-28 at 18.05.14.png
CleanShot 2021-01-28 at 18.05.37.png
CleanShot 2021-01-28 at 18.06.41.png
You do not have the required permissions to view the files attached to this post.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Thu Jan 28, 2021 9:19 pm

You cannot use the "contains" filter on IP addresses! You can use the "in" filter (which requires a subnet as value but it can be a single IP address).
The filtering is working on the raw IP address value, not the text you see in the output.
Of course it would be better when options that do not work are not offered in the GUI, i.e. once you select Data you don't get the "contains" option.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.48 [stable] is released!

Fri Jan 29, 2021 12:26 pm

@peichl Thanks for the explanation. I assumed everything you enter there is treated as a string, because Data doesn't necessarily need to be an IP Address, it could also be a domain name, in case it's a CNAME or PTR record.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Fri Jan 29, 2021 12:30 pm

@peichl Thanks for the explanation. I assumed everything you enter there is treated as a string, because Data doesn't necessarily need to be an IP Address, it could also be a domain name, in case it's a CNAME or PTR record.
Yes, probably in that case it would work. The thing you need to understand is that the filter option in winbox does NOT convert all IP addresses from internal storage format into printable strings before applying the match. So a string match on an IP address never works (not only in this window, but everywhere).
I agree it is confusing and probably should be changed. But it is not specific to this RouterOS version and it would probably have to be fixed not in RouterOS but in winbox.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.48 [stable] is released!

Fri Jan 29, 2021 12:35 pm

Got it, thanks 👍
 
Valerio5000
Frequent Visitor
Frequent Visitor
Posts: 88
Joined: Fri Dec 06, 2013 2:38 am

Re: v6.48 [stable] is released!

Fri Jan 29, 2021 7:04 pm

Hi everyone, I bought 3 PWR-LINE APs for friends house and the first thing I did is install ROS 6.48 and update their firmware. After updating I noticed that the "PWR-Line1" interface on all my PWR-LINE APs is detected but they don't go into "Running". Tried to reset with and without default configuration but without success. By installing ROS 6.46.8 LT everything works perfectly. Is there a bug on 6.48 for these devices?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Fri Jan 29, 2021 7:20 pm

Is there a bug on 6.48 for these devices?
Likely, yes. Read the above messages. So downgrade to long-term version.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v6.48 [stable] is released!

Sat Jan 30, 2021 12:10 pm

Is there a bug on 6.48 for these devices?
Likely, yes. Read the above messages. So downgrade to long-term version.
Mikrotik should act fast and release a 6.48.1 in stable channel. This is unacceptable to have such a buggy stable release.
 
User avatar
Paternot
Forum Veteran
Forum Veteran
Posts: 953
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v6.48 [stable] is released!

Sat Jan 30, 2021 4:30 pm

Is there a bug on 6.48 for these devices?
Likely, yes. Read the above messages. So downgrade to long-term version.
Mikrotik should act fast and release a 6.48.1 in stable channel. This is unacceptable to have such a buggy stable release.
I couldn't agree more. Version 6.48 was quite a lemon.
 
User avatar
jimmer
just joined
Posts: 19
Joined: Wed Mar 06, 2019 10:06 am
Location: Tasmania, Australia

Re: v6.48 [stable] is released!

Sun Jan 31, 2021 2:37 am

Also agree, it poor form to have such a buggy release in the stable release tree, it should be either pulled from the repository or a patched version released. For those of us that are familiar with downgrading its a quick but inconvenient step and a few minutes of downtime while doing it.

There hasn't been any fixes making it into the testing stream for the 6.48 release that I've seen. Not the greatest look for those new to Mikrotik who are wondering why certain devices break when upgraded to the latest stable release :(
 
encorer
just joined
Posts: 4
Joined: Sat Mar 23, 2019 10:15 pm

Re: v6.48 [stable] is released!

Sun Jan 31, 2021 4:15 pm

Mikrotik (v.6.48) DNS-server on hap ac2 slower than other DNS-servers, including externals, here are my tests using a directly connected pc and a raspberry pi 4, with pi-hole dns server, based on dnsmasq. I love MikroTik, and use it at work , at home, and recommend it to my friends, so I want it to be the best.
UPD on a level playing field
dns_bench.jpg
dns_bench_stat.jpg
dns-mikrotik.jpg
You do not have the required permissions to view the files attached to this post.
Last edited by encorer on Sun Jan 31, 2021 5:31 pm, edited 3 times in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Sun Jan 31, 2021 4:33 pm

Remove the DoH server and try again....
 
encorer
just joined
Posts: 4
Joined: Sat Mar 23, 2019 10:15 pm

Re: v6.48 [stable] is released!

Sun Jan 31, 2021 5:01 pm

Remove the DoH server and try again....
update the photos, because the conditions were not level
dns_bench-wo-doh.jpg
dns_bench_stat-doh-off.jpg
dns-mikrotik-wo-doh.jpg
You do not have the required permissions to view the files attached to this post.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Sun Jan 31, 2021 5:22 pm

Ok so now there is no difference... which can be expected.
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 2855
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: v6.48 [stable] is released!

Mon Feb 01, 2021 11:12 am

So far so good ... long uptimes ... the one with 12d has shorter uptime due to power outgage in an external building.
CAPSMAN running.
648.PNG
You do not have the required permissions to view the files attached to this post.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Mon Feb 01, 2021 11:37 am

So far so good ... long uptimes ... the one with 12d has shorter timeup due to power outgage in an external building.
In our HAMNET I see several 6.48 routers with uptimes up to 39d. It looks like as long as you are not hit with one of the obvious problems, the release in itself is stable.
I tried it myself on a toy device I use as AP (hAP mini) but the WiFi did not work acceptably so I downgraded. But most of the above mentioned routers do not have WiFi.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.48 [stable] is released!

Mon Feb 01, 2021 6:01 pm

Same here, rock solid on all my devices:
[admin@himalia] > :foreach Device in=[ /ip neighbor find where !(version="") ] do={ :put [ /ip neighbor get $Device uptime ]; }  
5w5d03:40:30
5w5d03:40:30
5w5d02:35:32
5w5d02:35:39
5w5d03:32:51
5w5d03:33:36
5w5d03:37:38
5w5d03:37:49
5w5d03:37:52
5w5d03:36:35
5w5d03:37:48
I do not own one of those having port flapping issues, though. 😜
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26287
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.48 [stable] is released!

Tue Feb 02, 2021 2:28 pm

I feel your pain, we really want to release the fixes, but there is currently a roadblock with our release procedure, which we are actively working on.
The version should be out any moment now, we are working really hard to resolve the issue faster.
 
Spirch
Member Candidate
Member Candidate
Posts: 119
Joined: Sat May 03, 2014 5:04 am

Re: v6.48 [stable] is released!

Tue Feb 02, 2021 3:00 pm

for me i decided to wait a week or 2 after it got released and when i saw all the bad thing i just decided to wait

i will do the same thing with 4.8.1, i'm in no rush to update my device
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Tue Feb 02, 2021 7:25 pm

Hmm, are some wrong with the forum as well? (or just in this thread)

Both Cray, morphema and stevenb are all listed with Posts: 0
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Tue Feb 02, 2021 7:50 pm

Hmm, are some wrong with the forum as well? (or just in this thread)

Both Cray, morphema and stevenb are all listed with Posts: 0
I think it is an off-by-one bug, it appears that new posters get posts: 0 after their first post.
 
User avatar
Chaosphere64
Frequent Visitor
Frequent Visitor
Posts: 94
Joined: Wed Aug 10, 2016 10:19 pm

Re: v6.48 [stable] is released!

Tue Feb 02, 2021 10:12 pm

Hmm, are some wrong with the forum as well? (or just in this thread)

Both Cray, morphema and stevenb are all listed with Posts: 0
I think it is an off-by-one bug, it appears that new posters get posts: 0 after their first post.
But morphema already has 2 posts now and still 0 in the posts counter. But I think we are getting off topic and should focus on getting a 1 behind the current RouterOS release version ...
 
Cray
just joined
Posts: 10
Joined: Fri Sep 27, 2013 12:24 pm

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 9:32 am

Unusually long period of silence from MikroTik. No development releases, no emergency fixes to the 6.48, no communication about the situation whatsoever. And the buggy version is still being distributed to customers as stable. I admit however, that on most - not all - device models the 6.48 runs ok with just minimal default configuration, but as soon as you start using some more professional features the wide range of problems start quickly to pile up.

It almost looks like MikroTik devs dumped everything being worked on in their development code to 6.48 stable release just two days before holidays and ran with it.

Usually features and fixes are seen gradually being iterated to development, stable and then to long-term releases, but given the wide range of instability introduced with 6.48 it almost looks like a build comes directly from development "master branch" without any filter.

Do not get me wrong: I absolutely love MikroTik devices and software and have been using them for the past decade - and I will continue to do so - but even the best of the best make mistakes sometimes.

It's the silence and lack of action that worries me this time.

So MikroTik, please say .. something!

[EDIT] Oh, MT did say something just before my post. Good. My opinion on 6.48 still stands.
Last edited by Cray on Wed Feb 03, 2021 9:44 am, edited 1 time in total.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 9:43 am

So MikroTik, please say .. something!
In case you missed it, in post #303 above Mikrotik did say something.
 
Cray
just joined
Posts: 10
Joined: Fri Sep 27, 2013 12:24 pm

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 9:45 am

So MikroTik, please say .. something!
In case you missed it, in post #303 above Mikrotik did say something.
Yes, I missed it.

Glad they did. It gives us hope.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 9:48 am

Proud zero since 2013 ;)
You have then been here long (since 27 Sep 2013, 11:24) and not posted much :)
If I look at your statistic, you have 6 post , first post 12.01.2021 (But there may be other counting errors)
 
mistry7
Forum Guru
Forum Guru
Posts: 1480
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 10:12 am

roadblock
Does the developer Team fell into wintersleep?
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 10:50 am

roadblock
Does the developer Team fell into wintersleep?
I'm wondering if perhaps they do not intend to release a 6.49 (moving to v7 instead as the next stable release after 6.48) and their existing build process is forcing them to release a 6.49 beta X in order to add the fixes to 6.48, like they normally do. It is just a guess, but it could explain the "roadblock" and therefore the delay.
 
LSan83
Frequent Visitor
Frequent Visitor
Posts: 66
Joined: Fri Aug 10, 2018 11:35 am
Location: Italy

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 11:03 am

Maybe... I hope the roadblock isn't for Covid problems in the team.
 
Kindis
Member
Member
Posts: 434
Joined: Tue Nov 01, 2011 6:54 pm
Location: Sweden

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 11:15 am

roadblock
Does the developer Team fell into wintersleep?
I'm wondering if perhaps they do not intend to release a 6.49 (moving to v7 instead as the next stable release after 6.48) and their existing build process is forcing them to release a 6.49 beta X in order to add the fixes to 6.48, like they normally do. It is just a guess, but it could explain the "roadblock" and therefore the delay.
Read a post on reddit where some people had e-mail support and gotten hold of 6.49Beta build so I suspect that 6.49 is coming. But I would be a fan if they stop development on V6 (just bugfixes) and then putt full focus on V7 in stead. But that is also easy for be to say that have no idea how they develop :-)
 
User avatar
CZFan
Forum Guru
Forum Guru
Posts: 2098
Joined: Sun Oct 09, 2016 8:25 pm
Location: South Africa, Krugersdorp (Home town of Brad Binder)
Contact:

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 11:38 am

I'm wondering if perhaps they do not intend to release a 6.49 (moving to v7 instead as the next stable release after 6.48) ...
I suspect there is a big push to get V7 out, hence the huge change released in Dec 2020, but suspect we will still get a couple V6 updates
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 12:28 pm

They need to get v7 out, since they have sold routers with v7 beta on it. As we all know, beta should not be used in production.
+1 for stop 6.x train and keep focus and get v7 out.
 
User avatar
Paternot
Forum Veteran
Forum Veteran
Posts: 953
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 12:59 pm

Yes, I think that's what they should do: put version 6 on bugfix mode, and all hands on deck to v7. Another thing they should do is one beta v7 each month, warts and all.
 
r00t
Long time Member
Long time Member
Posts: 672
Joined: Tue Nov 28, 2017 2:14 am

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 3:33 pm

v6.49beta is out and it fixes 9 issues introduced in v6.48. Haven't tested it properly yet, but it can't be worse than 6.48.... right? Fingers crossed, hoping it will became actually "stable" ROS version for a change...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.48 [stable] is released!

Wed Feb 03, 2021 4:42 pm

Remember that "stable" in actual use (i.e. it does not crash, it performs the required functions, no critical bugs) has nothing to do with the name "stable" in a software release branch, which means "we are not tinkering with it all the time".
It is similarly confusing as "free", which can be interpreted as "it costs nothing" and "there is freedom to use and look at it".

IMHO such confusing names should not be used, but I do not run the shop.
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2095
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: v6.48 [stable] is released!

Thu Feb 04, 2021 2:14 am

v6.49beta is out and it fixes 9 issues introduced in v6.48. Haven't tested it properly yet, but it can't be worse than 6.48.... right?
That is my theory too !
 
leonardogyn
just joined
Posts: 18
Joined: Wed Dec 04, 2019 4:47 pm

Re: v6.48 [stable] is released!

Thu Feb 04, 2021 4:07 pm

posting on the 6.48 thread and not on 6.49rc1 because I haven't tested it on the RC one. And given what I believe we're seeing (a 32 bit integer overflow), it would take quite a few days (if not weeks or month) for being able to reproduce it on a new firmware anyway. And there's no "queue tree" listed fix on 6.49rc1, so I believe this was unnoticed to now.

on a RB1100AHx2 running 6.48, queue tree packets counter seems to be a signed 32 bit integer and, given enough time for it to reach the signed 32 bit integer limit (2,147,483,647), it's overflowing and becaming a negative number and counting backwards. There's little (or no) reason for those counters not being 64 bit capable.

screenshots were taken a few seconds from each other. Please note that while the bytes counter is increasing, the packets counter is going backwards (and it's a negative number), proving with very little doubt that we had a 32 bit integer overflow here.
.
.
Captura de tela 2021-02-04 105245.jpg
Captura de tela 2021-02-04 105327.jpg
Captura de tela 2021-02-04 105216.jpg
You do not have the required permissions to view the files attached to this post.
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.48 [stable] is released!

Fri Feb 05, 2021 10:52 am

New version 6.48.1 has been released in stable RouterOS channel:

viewtopic.php?f=21&t=172321

Who is online

Users browsing this forum: sirca and 20 guests