Indeed, MikroTik is really going on the wrong track lately.
A bit more of this and we are better off running a plain Linux system and configure everything from scratch using config files and shell scripts native to Linux.
(and no longer be confronted with situations where the underlying system can do things that are hidden by the config layer, even after years of asking for additions)
There really should be internal discussion on what is the way to go.
Want to try containers but Waiting on the new release due to these new bugs… How does something like netwatch disappear from cli or start running the wrong scripts just because some extra advanced fields were added, that seems very strange..?
Anyone else having issues with L2TP on these more recent beta versions? (I’m IPSEC encrypted with config set in ip/ipsec rather than under the L2TP client and server config).
Client and server both running 7.4beta4, I get (on the client):
16:02:24 l2tp,ppp,info peter_home_l2tp: initializing…
16:02:24 l2tp,ppp,info peter_home_l2tp: connecting…
16:02:24 l2tp,debug tunnel 56 entering state: wait-ctl-reply
16:02:24 l2tp,debug tunnel 56 entering state: established
16:02:24 l2tp,debug session 58 entering state: wait-reply
16:02:24 l2tp,debug session 58 entering state: established
16:02:24 l2tp,ppp,debug peter_home_l2tp: LCP lowerup
16:02:24 l2tp,ppp,debug peter_home_l2tp: LCP open
16:02:24 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:27 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:30 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:33 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:36 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:39 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:42 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:45 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:48 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:51 l2tp,ppp,debug peter_home_l2tp: PPP received non-LCP packet (0xc223) when LCP not open
16:02:54 l2tp,ppp,debug peter_home_l2tp: LCP lowerdown
16:02:54 l2tp,ppp,debug peter_home_l2tp: CCP close
16:02:54 l2tp,ppp,debug peter_home_l2tp: BCP close
16:02:54 l2tp,ppp,debug peter_home_l2tp: IPCP close
16:02:54 l2tp,ppp,debug peter_home_l2tp: IPV6CP close
16:02:54 l2tp,ppp,debug peter_home_l2tp: MPLSCP close
16:02:54 l2tp,ppp,info peter_home_l2tp: terminating…
16:02:54 l2tp,debug session 58 entering state: stopping
16:02:54 l2tp,ppp,debug peter_home_l2tp: LCP lowerdown
16:02:54 l2tp,ppp,debug peter_home_l2tp: LCP down event in starting state
16:02:54 l2tp,ppp,info peter_home_l2tp: disconnected
16:02:55 l2tp,debug tunnel 56 entering state: dead
16:02:55 l2tp,debug session 58 entering state: dead
On the server side, the error relates to the client not responding to its CHAP challenge
On client side, error messages suggest the CHAP packets (0xc223) are being dropped due to “LCP not open”, despite the log line immediately prior declaring “LCP open”.
I am only running L2TP/IPsec connections on 7.4 on the client side, server is 6.49.x, and I have no such issues here.
Can confirm that beta4 fixes the boot-loop. IPv6 NAT netmap still broken though 
It is really nice how finally a RouterOS device that gets its IP via SLAAC will show that IP under IPv6->Addresses, thank you for finally doing this (I realize it was done in 7.3.x and not 7.4.x, but still, it is a new feature that I have been requesting for years now).
However, the default route being received through SLAAC is still not being displayed in the routing table. Are there plans to address this in 7.4.x?
My RB5009 running 7.3.1 and firmware 7.2.3 refused to boot after upgrading to 7.4Beta4. Only a netinstall back to 7.3.1 resurrected it.
No supout - it never booted. I also struggled for about 3 hours just to get Netinstall working. Only Neinstall 7.2.3 seemed to work for me - I had to run Wireshark and see which versions would send the code via BOOTP without failing halfway through with “port unreachable” after block 2763.
Once I managed to force 7.3.1 back onto it, it came back. It’s really hard to diagnose the 5009 given its lack of a serial port for the pre-boot environment.
"this has been addressed in v7.3 , using pe-ce bgp , however run this in the lab before any live deployments "
CE :
[admin@bank] > routing/route/print
Flags: A - ACTIVE; c, b, y - COPY; H - HW-OFFLOADED
Columns: DST-ADDRESS, GATEWAY, AFI, DISTANCE, SCOPE, TARGET-SCOPE, IMMEDIATE-GW
DST-ADDRESS GATEWAY AFI DISTANCE SCOPE TARGET-SCOPE IMMEDIATE-GW
b 1.1.1.1/32 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ab 1.1.1.1/32 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
b 2.2.2.2/32 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ab 2.2.2.2/32 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
Ac 3.3.3.3/32 loopback0 ip4 0 10 loopback0
Ab 8.8.8.8/32 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
b 8.8.8.8/32 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
b 100.64.0.0/31 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ab 100.64.0.0/31 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
b 100.64.0.2/31 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ab 100.64.0.2/31 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
b 100.64.0.4/31 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ab 100.64.0.4/31 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
b 100.64.0.6/31 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ab 100.64.0.6/31 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
Ab 100.64.0.8/31 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
b 100.64.0.8/31 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ab 100.64.0.10/31 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
b 100.64.0.10/31 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
b 203.0.113.0/30 203.0.113.1 ip4 20 40 10 203.0.113.1%ether1
Ac 203.0.113.0/30 ether1 ip4 0 10 ether1
b 203.0.113.4/30 203.0.113.5 ip4 20 40 10 203.0.113.5%ether2
Ac 203.0.113.4/30 ether2 ip4 0 10 ether2
Ac fe80::%ether1/64 ether1 ip6 0 10 ether1
Ac fe80::%ether2/64 ether2 ip6 0 10 ether2
Ac fe80::%loopback0/64 loopback0 ip6 0 10 loopback0
A H ether1 link 0
A H ether2 link 0
A H ether3 link 0
A H ether4 link 0
A H ether5 link 0
A H ether6 link 0
A H ether7 link 0
A H ether8 link 0
A H loopback0 link 0
[admin@bank] > tool/traceroute 1.1.1.1 src-address=3.3.3.3
Columns: ADDRESS, LOSS, SENT, LAST, AVG, BEST, WORST, STD-DEV, STATUS
1 100% 46 timeout
2 192.0.2.14 0% 45 5.2ms 4.8 2.8 9.2 1.5 <MPLS:L=21,E=0 L=35,E=0,T=1>
3 192.0.2.8 0% 45 3.4ms 4.8 2.5 13.2 2.3 <MPLS:L=22,E=0 L=35,E=0,T=1>
4 100.64.0.0 0% 45 2.4ms 3.9 1.6 28.7 3.9 MPLS:L=35,E=0
5 1.1.1.1 0% 45 2.8ms 4.2 2.1 10.6 1.8
[admin@bank] >
PE:
[admin@p7.mikey.rsco] > routing/route/print where routing-table=bank
Flags: A - ACTIVE; c, b, y - COPY; H - HW-OFFLOADED
Columns: DST-ADDRESS, GATEWAY, AFI, DISTANCE, SCOPE, TARGET-SCOPE, IMMEDIATE-GW
DST-ADDRESS GATEWAY AFI DISTANCE SCOPE TARGET-SCOPE IMMEDIATE-GW
Ay 1.1.1.1/32 198.51.100.101 ip4 0 40 30 192.0.2.14%ether2
Ay 2.2.2.2/32 198.51.100.106 ip4 0 40 30 192.0.2.19%ether1
Ab 3.3.3.3/32 203.0.113.2@bank ip4 20 40 10 203.0.113.2%ether3
Ay 8.8.8.8/32 198.51.100.109 ip4 0 40 30 192.0.2.14%ether2
Ay 100.64.0.0/31 198.51.100.101 ip4 0 40 30 192.0.2.14%ether2
Ay 100.64.0.2/31 198.51.100.106 ip4 0 40 30 192.0.2.19%ether1
Ay 100.64.0.4/31 198.51.100.101 ip4 0 40 30 192.0.2.14%ether2
Ay 100.64.0.6/31 198.51.100.106 ip4 0 40 30 192.0.2.19%ether1
Ay 100.64.0.8/31 198.51.100.109 ip4 0 40 30 192.0.2.14%ether2
Ay 100.64.0.10/31 198.51.100.110 ip4 0 40 30 192.0.2.19%ether1
b 203.0.113.0/30 203.0.113.2@bank ip4 20 40 10 203.0.113.2%ether3
Ac 203.0.113.0/30 ether3@bank ip4 0 10 ether3
Ab 203.0.113.4/30 203.0.113.2@bank ip4 20 40 10 203.0.113.2%ether3
Ac fe80::%ether3/64 ether3@bank ip6 0 10 ether3
A H ether3 link 0
[admin@p7.mikey.rsco] >
The terminal inkey timeout parameter is not working since around v7.3. In a few scripts I have that loop until a key press, they now get stuck on this command, endlessly waiting for a keypress.
When I run the following command on a MikroTik Chateau LTE12 on v7.3.1 stable or a Chateau 5G on v7.4beta4, it does not timeout after 5 seconds:
:put [ :terminal inkey timeout=5 ]
With earlier firmware versions such as 7.2, it would continue after waiting 5 seconds.
Recently upgraded the RB4011 of my house to the v7.4b4 and had the need of connect by ethernet, because the wlan2 5Ghz radio was disabled by default after the reboot… enabling the radio, all work great again!
New beta today with BFD support, full VRF support and reported bug fixes?
CCR2004-16G v7.4beta4; Using the device usb interface, if I insert the usb3.0 USB flash drive, the system and smb services will be unstable, and the device cannot automatically recognize the USB flash drive after restarting the device. If I use a usb2.0 USB flash drive, everything is normal. The brand of the USB flash drive is SanDisk.
What’s new in 7.4beta5 (2022-Jun-27 10:39):
*) container - added support for running Docker ™ containers on ARM, ARM64 and x86;
*) dhcpv4-server - disallowed overriding message type option;
*) dhcpv4-server - log message when user option updates existing option;
*) dhcpv4-server - placed option 53 as the first one in the packet;
*) health - fixed requesting data from sensor when issuing “get” command;
*) health - fixed voltage reporting on some RBmAP-2nD devices;
*) lte - validate LTE attached IP type in MBIM mode;
*) netwatch - added support for more advanced probing;
*) poe - hide “poe-voltage” parameter on devices that do not support it;
*) route - expose all valid routes to route select filter from OSPF and RIP;
*) route-filter - fixed route select filter rules;
*) upgrade - ignore same version packages during upgrade procedure;
*) wifiwave2 - added initial support for roaming (802.11r) between local AP interfaces;
*) winbox - added “name” parameter under “Routing/BGP/Session” menu;
*) winbox - added “to-address” and “to-ports” parameters under “IPv6/Firewall/NAT” menu;
*) winbox - added support for “Routing/GMP” menu;
*) winbox - added support for “veth” interface types;
*) winbox - fixed “inactive” flag naming under “MPLS/Local Mapping” menu;
*) winbox - fixed minor typo under “Interface” stats;
*) winbox - fixed units for “reachable-time” parameter under “IPv6/ND” menu;
*) winbox - removed “TLS Host” parameter from “IP/Firewall/NAT” menu;
*) winbox - removed duplicate signal strength column under “Wireless/Registration Table” menu;
Just ugpraded my hAP ac^3 to 7.4beta5
Netwatch terminal issue fixed.
Some of those changes are present in the previous beta too, what gives?
*) container - added support for running Docker ™ containers on ARM, ARM64 and x86;
*) netwatch - added support for more advanced probing;
*) wifiwave2 - added initial support for roaming (802.11r) between local AP interfaces;
Or they contain fixes over the previous implementation?
LE: ok, netwatch script on-down is fixed, the rest of the reported issues are still present (regarding netwatch).
LE2: I don’t know if containers existed in WinBox but it exists now.
LE3: netwatch config is visible in export, so this is fixed too.
envlist changed syntax: https://forum.mikrotik.com/viewtopic.php?t=178342&start=300#p942131
It seems “list” is now “name” and “name” is now “key” . Thanks @daaf
envlist is not migrated to new syntax, so make a backup and readd them with the new syntax.
Adding comments to containers seem to be fixed…
Veth interfaces still can’t be edited, any change to address or gateway require a reboot, or removing the interface and recreating it…
This was mentioned in the previous beta, yet you’re saying this is new in beta5. Has something changed?
For what action specifically? I know dst-nat already had it, src-nat maybe? It still seems to be missing for netmap though. Which itself is also still broken in this version as well.
what is Routing/GMP?
EDIT: just found the wiki page.. never heard of this before
https://help.mikrotik.com/docs/display/ROS/Group+Management+Protocol
Group Management Protocol(GMP)
ac2 upgraded to 7.4beta5.