Only dynamic static?..dns - fixed listening for DNS queries when only dynamic static entries exist (introduced in v6.47);
/system routerboard settings set auto-upgrade=yes
IPsec-SA expired before finishing rekey
How can we add a LCD logo? It would be great to add a custom image with our company logo and the Router-Name.*) branding - fixed LCD logo loading from new style branding package;
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.What has changed in the defaults for user groups and neighbor discovery?
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?*) tr069-client - send correct "ConnectionRequestURL" when using IPv6;
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*) m33g - added support for "/system gpio" menu (CLI only);
[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.xOn my CRS326-24G-2S+ after updating I no longer have any interfaces nor will the device reboot cleanly.
This is the output from terminal:Code: Select all[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 here on my RB3011. My WAN port was on ether 2 and kept flapping.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! ;)
Ahh. I have 3 LACP bonds on mine. I may well be having the same issue then.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.
same hereAfter 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! ;)
will remain, right??Tried the same with 6.48rc1 today. Still the same problem :(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?
Downgraded to 6.47.8 and it works again immediately.
# 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
Simply unplug all bond members and boot the switch, the issue occures only when the bond interfaces in the bridge are up and activeAhh. I have 3 LACP bonds on mine. I may well be having the same issue then.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.
Though how did you remove the bonds if the interfaces where not showing?
Difficult to know what this means, can anyone clarify?What's new in 6.48 (2020-Dec-22 11:20):
(...)
*) interface - fixed pwr-line running state (introduced in v6.45);
I can confirm the problem on RB750Gr3 and RB760iGS .hem after upgrade system health not showing voltage and temperature RB 750G r3
HiWhat are "Port Extensions"
No single word in any Mikrotik wiki...
confirmed on our RouterBOARD 3011UiASAfter 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! ;)
Hi @rushliferb3011 flapping, 1500 linkdowns for about 30 minutes
rb4011 seems to be fine
Do not worry,Hi @rushliferb3011 flapping, 1500 linkdowns for about 30 minutes
rb4011 seems to be fine
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, yeahHi @rushliferb3011 flapping, 1500 linkdowns for about 30 minutes
rb4011 seems to be fine
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
Go to your Mikrotik account,How can we add a LCD logo? It would be great to add a custom image with our company logo and the Router-Name.*) branding - fixed LCD logo loading from new style branding package;
So, i could consider lucky that i forget to update FW (second reboot)hi, yeahHi @rushliferb3011 flapping, 1500 linkdowns for about 30 minutes
rb4011 seems to be fine
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
firmware was also upgraded to 6.48
I was having same problem on CRS309-1G-8S+. After a while SFP+ port started constantly flapping every few seconds.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! ;)
RBD53iG-5HacD2HnD - the same bug.I can confirm the problem on RB750Gr3 and RB760iGS .hem after upgrade system health not showing voltage and temperature RB 750G r3
I am having the exact same problem here.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've seen same behavior on Gigaset N300A IP after upgrading my mom's 951Ui-2HnD to 6.48After 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
why are you upgrading to beta-version?
it has been repeatedly said that
"long-term" = Stable
"stable" = Beta
"testing" = Alpha
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 againI've seen same behavior on Gigaset N300A IP after upgrading my mom's 951Ui-2HnD to 6.48After 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
After downgrading to 6.46.8 issue got resolved.
In our setup we have 2 WAN ports "ether1 and ether2" and port flapping was present after the upgrade.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
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.Now on rekey childs mikrotik send and want proposals without pfs despite pfs-group=ecp521 configured. Similar issue has Windows 7 time ago.
Mine is indeed older, factory firmware is 3.27.Our 3011 is old but maybe not as old as yours it was shipping with firmware 3.41
My current settings: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.
/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
Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?I've seen same behavior on Gigaset N300A IP after upgrading my mom's 951Ui-2HnD to 6.48After 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
After downgrading to 6.46.8 issue got resolved.
What transport do you use for SIP (UDP, TCP, TLS)?Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?
Thanks, saved my day! Got it working!!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.
Transport was set to Automatic, but setting it to UDP only or TCP only doesn't make a difference.What transport do you use for SIP (UDP, TCP, TLS)?Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?
Is the SIP conntrack helper active? (/ip firewall service-port print)
Same here bugtik rb3011I have the same problem with eth1 and eth2 dropping every hour approximately on my RB3011, downgrading solved the problem as well.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! ;)
Hope this will be corrected
Same problems with SIP.Same on Gigaset S850A. Seems this update breaks SIP on multiple phones... any solution, or is downgrading the only option?
Moral of this story:I think the moral to this story is to avoid majors (6.48) and wait until the first minor (6.48.1)
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.Mine is indeed older, factory firmware is 3.27.Our 3011 is old but maybe not as old as yours it was shipping with firmware 3.41
nope, link is ok.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.
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).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.
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.nope, link is ok.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.
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.
Any information regarding this?hotspot - added support for captive portal advertising using DHCP (RFC7710)
Thats odd - I've got pfs set in phase 2 and the IKEv2 tunnel establishes correctly: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.
# 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
Your issue might be depending on the type of SFP you use,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 )
No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devicesIGMP 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.
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 :(No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devicesIGMP 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.
I'm using IGMP version 2I 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 :(No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devicesIGMP 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.
With 6.47.8 was all ok
Yes, they establish correctly. But do they rekey without issue? Have a look at your log...Thats odd - I've got pfs set in phase 2 and the IKEv2 tunnel establishes correctly:
Have a look above, IPSec issues have been discussed before.Please help if you experiencing similar issues as I have no idea where to even start troubleshooting.
Customer is always right. Why customer can't use as it marked as stable?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.
I send already.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?
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.I confirm the problem with SIP connections on this firmware.
I have a bundle of Gigaset C610A IP + RBD52G-5HacD2HnD.
SUP-33662osc86, 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?
done, SUP-37406ksaa, 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.
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 routerYour issue might be depending on the type of SFP you use,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 )
I have 4pc of RB962UiGS-5HacT2HnT with Mikrotik SFP's and they work fine
You should contact support directly ....
Thank you, I've read it all but nothing that would cover my case with IKEv1Have a look above, IPSec issues have been discussed before.Please help if you experiencing similar issues as I have no idea where to even start troubleshooting.
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.Same here on my RB3011. My WAN port was on ether 2 and kept flapping.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! ;)
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.
+1Sorry 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 issues here :(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
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.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).
tomaskir - Is this on a router that was just reset?
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.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.
/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
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.LLDP should not be forwarded from port to port under any circumstances
You are right. SA expires before rekey. Set pfs to none and will monitor..Yes, they establish correctly. But do they rekey without issue? Have a look at your log...Thats odd - I've got pfs set in phase 2 and the IKEv2 tunnel establishes correctly:
What that use for?Trusted checkbox appears twice in Bridge -> Ports -> <interface> -> General
Hmm, you can guess from the graph when I turned on DoH!!DoH related memory leak reported in SUP-31833 is not fixed in this release.
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 routerYour issue might be depending on the type of SFP you use,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 )
I have 4pc of RB962UiGS-5HacT2HnT with Mikrotik SFP's and they work fine
You should contact support directly ....
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.6.48 is the same as rc1 I guess? So this =>will remain, right??Tried the same with 6.48rc1 today. Still the same problem :(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?
Downgraded to 6.47.8 and it works again immediately.
This is my config:(exported from v6.47.8)Code: Select all# 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
Thank you, it helped me :-)Go to your Mikrotik account,How can we add a LCD logo? It would be great to add a custom image with our company logo and the Router-Name.*) branding - fixed LCD logo loading from new style branding package;
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.
with this release fans on the CRS312-4C+8XG-RM are running at max :/ any idea how ic an reduce the speed?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.
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 =)Have a look above, IPSec issues have been discussed before.Please help if you experiencing similar issues as I have no idea where to even start troubleshooting.
only a narcissist would say this.Moral of this story:I think the moral to this story is to avoid majors (6.48) and wait until the first minor (6.48.1)
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
Error I'm getting on mikrotik is: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).
[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...
m33g - added support for "/system gpio" menu (CLI only);
[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.
Code: Select all[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...
dhcp,debug,packet MikroTik: DHCP-Main received request with id 2264044792 from 192.168.10.230
dhcp,debug MikroTik: DHCP-Main received request id 212743147 from 192.168.10.230 '1:c4:ad:34:c3:37:xx'
I have two 3011 and I have none of these issue. Are your sure it is not the connected devices or cable?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.
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.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.
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.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.
Agree, The "stable" channel should be called Beta.we are waiting for 6.48.5 .. stable release is beta channel
Although v6.48 is perfectly stable for my RB450Gx4. I agree with you and the other members here.Agree, The "stable" channel should be called Beta.we are waiting for 6.48.5 .. stable release is beta channel
... or use the Long-term version if you want a more stable version. ;-)Although v6.48 is perfectly stable for my RB450Gx4. I agree with you and the other members here.Agree, The "stable" channel should be called Beta.we are waiting for 6.48.5 .. stable release is beta channel
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.Although v6.48 is perfectly stable for my RB450Gx4. I agree with you and the other members here.Agree, The "stable" channel should be called Beta.we are waiting for 6.48.5 .. stable release is beta channel
Eventually, I will be forced to move to a different vendor with a more reliable "stable" channel for patches/updates.
Did you also upgrade the firmware.6.46.8 LTS --> 6.48 Stable --> 6.46.8 LTS
No i did not upgrade the firmware. The firmware was v6.47.8 (i forgot that I switched to Stable channel ~4 weeks ago.)Did you also upgrade the firmware.6.46.8 LTS --> 6.48 Stable --> 6.46.8 LTS
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.Image
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!!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! ;)
Copy the correct .npk to your RB3011 using Winbox to Files folder.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
/system package downgrade
If you did read this thread, you will see that I posted the same here:This is most likely due to DoH function, because my secondary router wAP ac don't have same problem.
I tried, but don't have the privilege according to forum faq. Thanks anyway.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.Image
I have upgraded my RB750GR3 from 6.47.8 to 6.48 and Winbox 3.27 does show system health information.On RB750gr3, Winbox 3.27 does not show any health information in v6.48. However "/system health print" works fine:
And SIP forwarding toofix port flapping please for 3011 ASAP
Did you upgrade firmware under "/system routerboard"? I have upgraded mine and I wonder if this is the cause.
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
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.
Did you upgrade firmware under "/system routerboard"? I have upgraded mine and I wonder if this is the cause.
It has been this way since DoH has been introduced in 6.47 - see older release threads for details...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.
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 handsetsHi 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
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.
Did you made a rollback from Mikrotik Firmware 6.48 to older one? Does is solve the SIP traffic problem?
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.
+1 same here, worked again after downgrade to long termSame here, switching to long-term channel with v6.46.8 solved the issue with my 3 pwr-line devices.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...).
Run on 6.47.8.
I also ran into this issue. I downgraded back to 6.47.8 and the fan behavior returned to "normal".with this release fans on the CRS312-4C+8XG-RM are running at max :/ any idea how ic an reduce the speed?
A warning in the header would be enough.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?
search.php?keywords=rekey&t=171035&sf=msgonlyany ideas why upgrade causes full of errors regarding IKE2 rekey?
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.search.php?keywords=rekey&t=171035&sf=msgonlyany ideas why upgrade causes full of errors regarding IKE2 rekey?
Search this thread for pfs-group=, you will find some answers.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?
searched twice. Can you, please, post something more specific?Search this thread for pfs-group=, you will find some answers.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?
# 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
/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
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.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.xOn my CRS326-24G-2S+ after updating I no longer have any interfaces nor will the device reboot cleanly.
This is the output from terminal:Code: Select all[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)
I've also tried a factory reset and reconfiguration with a export backup .... same issue.
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:any more specific ideas, regarding that is more that 50 ipsec on the server?
So in my case, when pfs-group is defined on both sides equal to 2048, why there are problems with rekey?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:any more specific ideas, regarding that is more that 50 ipsec on the server?Hence setting pfs-group in proposal to none at both peers should resolve your issue yet not prevent use of PFS for rekeying.
- 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
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.Always was thinking, that proposals must be exactly the same, from both sides of ipsec, am i wrong??
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.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.Always was thinking, that proposals must be exactly the same, from both sides of ipsec, am i wrong??
downgraded server (CHR) to 6.47.8 and no errors. Will wait for the fix of this.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.
I have downgraded to 6.47.8 and the issue is resolved.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.
Got the response from support - this is a BUG, will be fixed in next version of RouterOSany more specific ideas, regarding that is more that 50 ipsec on the server?
Client side
Server side is the same exactlyCode: Select all# 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
Code: Select all/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
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.hEX PoE lost health info in 6.48
hex.PNG
And it's still available in CLI...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.
It often goes like this when a new test version is promoted to stable.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.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...
As you're in 6.48 discussion topic, looks like you don't use long-term release channel...Thus I've removed MT from the center of my network and using them only as access devices. Even there are issues, always.
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.As you're in 6.48 discussion topic, looks like you don't use long-term release channel...Thus I've removed MT from the center of my network and using them only as access devices. Even there are issues, always.
/snmp send-trap oid=2.1.1.1 type=integer value=1
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
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,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 handsetsHi 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
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
My Gigaset could no longer register with my provider. Disable MNDP solved the problem.Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS.
This solution works.My Gigaset could no longer register with my provider. Disable MNDP solved the problem.Edit: After several days I have customers reporting SIP connectivity problems with their Gigaset handsets as well. These have RB2011UiAS.
Gigaset C450 IP + RB2011UAS works here with:
/ip neighbor discovery-settings set protocol=cdp
or
/ip neighbor discovery-settings set protocol=cdp,lldp
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?!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.
but keep in mind that you share your admin account with anyone on the internetIf you need anything MORE stable - go to Zyxel with their zyfwp.
zyfwp is the hard coded account so I think a joke was made here 😁but keep in mind that you share your admin account with anyone on the internetIf you need anything MORE stable - go to Zyxel with their zyfwp.
Mikrotik´s RouterOS is like a Swiss knife. So many different tools.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.
[...]
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).@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.
Likely, yes. Read the above messages. So downgrade to long-term version.Is there a bug on 6.48 for these devices?
Mikrotik should act fast and release a 6.48.1 in stable channel. This is unacceptable to have such a buggy stable release.Likely, yes. Read the above messages. So downgrade to long-term version.Is there a bug on 6.48 for these devices?
I couldn't agree more. Version 6.48 was quite a lemon.Mikrotik should act fast and release a 6.48.1 in stable channel. This is unacceptable to have such a buggy stable release.Likely, yes. Read the above messages. So downgrade to long-term version.Is there a bug on 6.48 for these devices?
update the photos, because the conditions were not levelRemove the DoH server and try again....
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.So far so good ... long uptimes ... the one with 12d has shorter timeup due to power outgage in an external building.
[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 think it is an off-by-one bug, it appears that new posters get posts: 0 after their first post.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
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 ...I think it is an off-by-one bug, it appears that new posters get posts: 0 after their first post.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
In case you missed it, in post #303 above Mikrotik did say something.So MikroTik, please say .. something!
Yes, I missed it.In case you missed it, in post #303 above Mikrotik did say something.So MikroTik, please say .. something!
You have then been here long (since 27 Sep 2013, 11:24) and not posted much :)Proud zero since 2013 ;)
Does the developer Team fell into wintersleep?roadblock
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.Does the developer Team fell into wintersleep?roadblock
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 :-)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.Does the developer Team fell into wintersleep?roadblock
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 updatesI'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) ...
That is my theory too !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?