v7.2rc4 is released!

emils · Wed Feb 23, 2022 1:02 pm

RouterOS version 7.2rc4 has been released "v7 testing" 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 7.2rc4 (2022-Feb-22 13:37):

*) bgp - fixed VPNv4 route sending to remote peer;
*) bridge - fixed FastPath when using "frame-types=admit-only-untagged-and-priority-tagged" setting;
*) bridge - fixed IP address on untagged bridge interface when vlan-filtering is enabled (introduced in v7.2rc2);
*) bridge - fixed PPPoE packet forwarding when using "use-ip-firewall-for-pppoe" setting;
*) bridge - fixed destination NAT when using "use-ip-firewall" setting;
*) bridge - fixed filter and NAT "set-priority" on ARM64 devices;
*) bridge - fixed filter rules when using interface lists;
*) bridge - fixed priority tagged frame forwarding when using "frame-types=admit-only-untagged-and-priority-tagged" setting;
*) console - fixed terminal repainting on F5 and CTRL+L key press (introduced in v7.2rc2);
*) crs3xx - fixed watchdog timer functionality;
*) crs3xx - improved maximum allowed ACL rule calculation;
*) crs3xx - improved system stability when creating many ACL rules on CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) l2tp - improved system stability when processing L2TP control messages;
*) lte - added MAC address and IPv6 LL address persistence after reboot on EG12 and EG18 modems;
*) lte - made "no" the default value for "use-network-apn" parameter;
*) ntp - allow adding duplicate server address if dynamic entry exists;
*) ntp - fixed multicast mode support;
*) ntp - improved IPv6 address support;
*) ospf - fixed default route origination when "default-originate=if-installed" "redistribute" is enabled;
*) ospf - fixed external LSA not updating after prefix netmask change;
*) ppp - added "comment" option for PPPoE servers;
*) ppp - improved stability when handling large amount of connections simultaneously;
*) queue - improved system stability when using more than 255 unique packet marks;
*) route - fixed ECMP load balancing in FastPath;
*) route - fixed route addition to VRF from BGP;
*) route-filters - renamed "*-set" to "*-list";
*) sms - increased "at-chat" timeout when sending SMS;
*) switch - fixed port-isolation misconfiguration detection when using multiple switches;
*) switch - improved switch chip initialization process on bootup for CCR2004-16g-2s+ devices;
*) ups - fixed UPS support;
*) vxlan - fixed "group" and "interface" setting reset after upgrade (introduced in v7.2rc2);
*) vxlan - fixed running state after reboot when using "interface" and "group" settings;
*) wifiwave2 - added "client-isolation" feature;
*) winbox - added "host-uniq" parameter to PPPoE client interface;
*) winbox - do not show "Antenna Scan" button on devices that do not support it;
*) wireguard - allow same peer's public key for different interfaces;
*) wireguard - fixed IPv6 traffic processing with multiple peers;
*) wireless - added "3gpp-info" parameter to interworking configuration;
*) wireless - added EAP-AKA to interworking's realm configuration;
*) wireless - correctly preserve WMM priority when receiving packets;
*) wireless - improved nv2 link stability;

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.

rtlx · Wed Feb 23, 2022 1:05 pm

How many RC versions are planned before stable release?

msatter · Wed Feb 23, 2022 1:08 pm

Do I take the JUMP????

....wireguard - allow same peer's public key for different interfaces;

Thank you!!!

obscurus · Wed Feb 23, 2022 1:21 pm

No release info on update

mozerd · Wed Feb 23, 2022 1:25 pm

On my CCR1009 the wrong version description is displayed in the window:

7.2rc4.GIF

pe1chl · Wed Feb 23, 2022 1:31 pm

*) bgp - fixed VPNv4 route sending to remote peer;

Only ONE item for BGP fixes? At this rate we need to go to 7.2rc19 before it is ready...

obscurus · Wed Feb 23, 2022 1:32 pm

BGP prefix count still 0.
RB5009,750Gr3 and x86 update is ok

404Network · Wed Feb 23, 2022 1:43 pm

Do I take the JUMP????

....wireguard - allow same peer's public key for different interfaces;

Thank you!!!

Why, according to Mozerds links, its important to have different peer cryptography or did I read that wrong.

I would have preferred the ability to use Firewall Address Lists in routing rules myself!!

Ullinator · Wed Feb 23, 2022 1:45 pm

Is the wrong queue handling for IPv6 already fixed? (IPv6 FW is not working with this...) This bug prevents for me the update on my RB5009....still on 7.0.5 (factory ROS)
I didn´t see anything for this bug in the release notes for any RC versions...

eworm · Wed Feb 23, 2022 1:52 pm

IPv6 with queues is a blocker for me as well... It is not fixed with 7.1.3 😢 - as there's no log entry I guess the same applies for 7.2rc4. 😢

pe1chl · Wed Feb 23, 2022 1:56 pm

Updated my hAP ac2. It has a small BGP test setup. There was a separate routing table:

/routing table
add disabled=no fib name=ampr

and a BGP template using it:

/routing bgp template
add as=4220406101 disabled=no hold-time=15s name=ampr nexthop-choice=\
    force-self router-id=44.137.41.109 routing-table=ampr

After the update, the routing table was gone, and the template listed "16384" in the routing table field.
The routing table itself had routes with table "unknown".
I had to add the routing table again, set it in the template, disable/enable the connection to get it OK again.
Yet another case of "some configuration section lost on reboot/upgrade??" or is it something else?
After another reboot, the newly applied config still remained.

mozerd · Wed Feb 23, 2022 2:01 pm

Why, according to Mozerds links, its important to have different peer cryptography or did I read that wrong.

@404
BEST PRACTICES

The best practices for WireGuard keys are similar to those for SSH keys or client certificates (or any other host-based credentials) — no two hosts should share the same key (even for hosts that are considered simple “clients”). While this takes a little more work to set up, it’s much more maintainable in the long run.

KEY POINT: Additionally, if you operate more than one WireGuard interface on an individual host, it’s an okay practice to use the same key for all the interfaces on the host (it won’t result in a bad user experience) — but the best practice is to use a different key for each individual interface. The same security-practice issues described above also apply when sharing keys among interfaces on the same host (albeit to a lesser degree) — so not sharing keys makes for better/easier auditability, access control, and key rotation.

CTassisF · Wed Feb 23, 2022 2:29 pm

pppoe-client is not being detected as WAN or INTERNET after upgrading to rc4.

[cesar@MikroTik] > /interface/pppoe-client/print detail 
Flags: X - disabled, I - invalid; R - running 
 0  R name="pppoe-client" max-mtu=1492 max-mru=1492 mrru=disabled interface=ether3 user="xxx@xxx" password="xxx" profile=pppoe-client keepalive-timeout=60 service-name="" ac-name="" add-default-route=yes 
      default-route-distance=1 dial-on-demand=no use-peer-dns=no allow=pap,chap 

[cesar@MikroTik] > /interface/list/member/print detail where interface=pppoe-client 
Flags: X - disabled, D - dynamic 
 5   list=WAN interface=pppoe-client dynamic=no 

[cesar@MikroTik] > /interface/detect-internet/state/print detail where name=pppoe-client 

[cesar@MikroTik] >

pe1chl · Wed Feb 23, 2022 2:35 pm

pppoe-client is not being detected as WAN or INTERNET after upgrading to rc4.

I hope you are not really using that feature... just set all "detect internet" interface lists to "none" and add the pppoe-client to list WAN manually.
The way the default firewall is set up, it does not really matter if the WAN list is correct as the rules use !LAN (not LAN) instead of WAN.

DanMos79 · Wed Feb 23, 2022 3:22 pm

IPv6 with queues is a blocker for me as well... It is not fixed with 7.1.3 😢 - as there's no log entry I guess the same applies for 7.2rc4. 😢

I use different chains to mark the connection and the packets for my queue trees.
Maybe this is a workaround for someone else too.

/ipv6 firewall mangle
add action=mark-connection chain=forward connection-mark=no-mark connection-state=new dst-port=80,443 in-interface=LAN new-connection-mark=http-con out-interface=WAN passthrough=yes protocol=tcp
add action=mark-packet chain=prerouting connection-mark=http-con in-interface=LAN new-packet-mark=http-ul-pkt passthrough=no
add action=mark-packet chain=postrouting connection-mark=http-con new-packet-mark=http-dl-pkt out-interface=LAN passthrough=no

MikroTikTack · Wed Feb 23, 2022 3:29 pm

Such a trifle ... That was in previous versions as well.

wojo · Wed Feb 23, 2022 3:31 pm

For those with issues on the RB5009 with different link speeds (2.5G, 10G, see viewtopic.php?t=182691&e=1&view=unread#unread) it seems they may have reproduced the issue locally and a fix is pending:

We reproduced a similar behavior locally. We are looking forward to improving such behavior with different link speeds in further RouterOS releases.

hecatae · Wed Feb 23, 2022 4:01 pm

pppoe-client is not being detected as WAN or INTERNET after upgrading to rc4.

Has not worked since 6.43, what did you upgrade from?

mikegleasonjr · Wed Feb 23, 2022 6:27 pm

Cake has improved a lot, I can get more bandwidth all the while having the same bufferbloat timings.

Still waiting on being able to specify the direction of the flow :P

But a welcome surprise today...

pe1chl · Wed Feb 23, 2022 8:00 pm

Winbox 3.32 cannot connect to 7.2rc4 !
The log shows logged in/logged out in the same second.
But winbox 3.35 is buggy...
Please do not make such version dependencies!

CTassisF · Wed Feb 23, 2022 8:27 pm

Has not worked since 6.43, what did you upgrade from?

IIRC it was working on rc3 (the version I was using before rc4).

Wed Feb 23, 2022 9:21 pm

Winbox 3.32 cannot connect to 7.2rc4 !
The log shows logged in/logged out in the same second.
But winbox 3.35 is buggy...
Please do not make such version dependencies!

Had some other versions in my archive.
Same problem with Winbox 3.31 and Ros 7.2rc4. Towards ROS 7.1.3 works just fine.
AND ... could be me but Webfig doesn't seem to work on 7.2rc4 either ? Works just fine towards a 7.1.3 device.

pe1chl · Wed Feb 23, 2022 9:27 pm

For me the webfig works OK

msatter · Wed Feb 23, 2022 10:17 pm

I took the JUMP and hit the concrete on the bottom with my head!!

WTF Mikrotik!! Erase the routing tables (/routing/table), leaving me with setting about 50 different routing-marks all who are all over the place!!!!!

I started the recovery but ran out off breath doing them all and will think hard over it before trying to go from 7.1.1 to 7.2RC again. I went back to 7.1.1 and then restored the config and all worked again like a well oiled machine. oooooooooooooooooooooooof!

Is there not a better way change routing tables without let us running in to walls??

CTassisF · Wed Feb 23, 2022 10:36 pm

WTF Mikrotik!! Erase the routing tables (/routing/table), leaving me with setting about 50 different routing-marks all who are all over the place!!!!!

I also lost the single custom routing table I had after upgrading from rc3 to rc4 🤡 At least in my case it was easy to fix, but it took me a while to understand what was wrong after the upgrade.

osc86 · Thu Feb 24, 2022 1:04 am

I upgraded a CCR2004-16G-2S+ from 7.2rc3 to 7.2rc4.
After I experienced an issue with one vlan not passing traffic anymore, I restarted the router. This was the second reboot after the upgrade, the first one happened right after the ros update to update routerboot.
The router didn't come back online, so I checked with woobm and my phone what is going on.
Well, the config looked like it was hit by a nuclear warhead.
- all bridges completely gone
- some interfaces got reset to their default values including both sfp-plus and one ethernet interface
- 4 wireguard interfaces, 1 6in4 tunnel interface, 1 eoip tunnel, 1/7 vlan completely gone
- lost some wireguard peers, some had invalid values in their configuration, like only AAAAAAs for the public key
- firewall filter rules (IPv4+6) mostly gone, 4 out of ~60 survived, but all INPUT rules were deleted, WAN interface was still working(!)
- capsman config 90% gone
- lost CA and LE certificates, capsman CA and caps certs survived

Mikrotik please stop working on anything else and fix this bs. Is this all stored in a MS access database on a filesystem that doesn't support cow?
It seems like there is no integrity checking taking place at all.

As for backups (before updating the router):
exports are mostly useless because they don't include certificates, um db, ssh keys, etc. which could easily be done by converting them into base64 and also storing them in the rsc/text file.
binary backups are (currently) also useless, because they store the entire database, and at the time of taking that backup nobody knows if it's already corrupted, and every time you have to restore that file, you'll end up having the same problem.

I took a supout and an export from this mess and I'll file a ticket tomorrow, but really, this needs to stop!

sizz0p · Thu Feb 24, 2022 1:41 am

Many thanks to everyone above who has suffered because of jumping on this hand grenade so that I (and others) didn't need to do so! I'll take one for the team next time!

sirbryan · Thu Feb 24, 2022 2:28 am

I went from 7.1.3 to 7.2rc4 on a CCR2004-1G-12S+2XS to test an L2TP/IPSEC fix and it too felt like a bomb went off.

Fortunately it was the home lab router; unfortunately it was talking to the production network...

While it appears most things were still working, OSPF adjacencies were all over the place, and eventually I caught it telling the rest of the network that it was the best path for everything...

Back-rev'd it to 7.1.3 and, after reinstalling ZeroTier and fixing some MTU issues on the bridge and VLAN interfaces, it settled down.

IntLDaniel · Thu Feb 24, 2022 2:37 am

After upgrade from 7.2rc3 to 7.2rc4 all of routing tables are gone and related mangle rules are broken (RouterBOARD 750G r3)
Edit: Also internet detection is broken!

Kentzo · Thu Feb 24, 2022 2:51 am

*) wireless - correctly preserve WMM priority when receiving packets;

Could you elaborate into this? Specifically, where can this information be seen now?

elgrandiegote · Thu Feb 24, 2022 4:23 am

no changes in ovpn udp? let's get to the rc58 at this rate...

buset1974 · Thu Feb 24, 2022 8:12 am

BGP VRF on MPLS Layer 3 implementation still not works.
Everything works fine in 6.49.2

bgp-v7.2rc4.jpg

how many longer should we wait?
V7 is not beta anymore.

thx

export-list.rsc

infabo · Thu Feb 24, 2022 9:54 am

How many RC versions are planned before stable release?

Better some more...

pe1chl · Thu Feb 24, 2022 10:34 am

no changes in ovpn udp? let's get to the rc58 at this rate...

Priority should be to fix features that already were working in v6 but are broken in v7.

infabo · Thu Feb 24, 2022 12:03 pm

When I look through the changelogs of testing release tree I must admit, that RC releases were released at a way higher pace several years ago. 6.41,6.42,6.43 and so on. New RC releases at least once a week or so. Some even within days. And the changelog within a week was like huge.

pe1chl · Thu Feb 24, 2022 12:07 pm

*) wireless - correctly preserve WMM priority when receiving packets;
Could you elaborate into this? Specifically, where can this information be seen now?

This info should be in the "priority" field present in each packet. That would be transferred to the priority in a VLAN tag, or it can be used (albeit with a detour via packet marks) in a queue tree.

Chupaka · Thu Feb 24, 2022 1:48 pm

I noticed this in rc3, now it's reproducible in rc4. I have a Routing Filter rule that disappears after reboot:

 > routing/filter/rule/export 
# feb/24/2022 14:45:29 by RouterOS 7.2rc4
# software id = 
#
/routing filter rule
add chain=ospf-out disabled=no rule=reject
add chain=ospf-out disabled=no rule="if ( gw-interface ether1 || gw-interface wg-RedShield ) { reject; } accept;"
add chain=ospf-out disabled=no rule=reject

REBOOT...

 > routing/filter/rule/export 
# feb/24/2022 14:48:16 by RouterOS 7.2rc4
# software id = 
#
/routing filter rule
add chain=ospf-out disabled=no rule=reject
add chain=ospf-out disabled=no rule=reject

pe1chl · Thu Feb 24, 2022 1:54 pm

I noticed this in rc3, now it's reproducible in rc4. I have a Routing Filter rule that disappears after reboot:

Did you already do a clean netinstall and import of the old exported config before?
I plan to do that with rc4 now that it is clear that a rc3->rc4 update does not work anyway in a router that uses multiple routing tables.
I hope it is caused by some database corruption that is fixed when a clean start is made... some other reports seem to suggest that.

Chupaka · Thu Feb 24, 2022 1:57 pm

I can't do that, it's CHR instance in Oracle Cloud Free Plan, and I can't create custom disk images anymore

pe1chl · Thu Feb 24, 2022 2:28 pm

Ok... don't know if you can do a full configuration reset e.g. because you have a nearby VM that can serve as RoMON relay (if that is possible in that service), but I already did that before and it did not fully remedy the problem anyway.

IntLDaniel · Thu Feb 24, 2022 3:05 pm

Am I able to download somewhere ROS 7.2rc3 again? Or is it safe to downgrade back to 6.49.3 from 7.2rc4 (what about different routing table config during downgrade)?

pe1chl · Thu Feb 24, 2022 3:12 pm

All older versions can be found on the MikroTik download page.
When you downgrade from v7 to v6 your configuration will revert to what it was when you last had v6, so all changes made since then will be lost.
Of course you can export your config before you downgrade and import it after the downgrade, but it may be that edits in the export are required.
And of course you have to reset to a blank config before you can import an entire config. But maybe you only have a specific section where you made changes, and you can clear and import only that.

IntLDaniel · Thu Feb 24, 2022 3:47 pm

All older versions can be found on the MikroTik download page.
When you downgrade from v7 to v6 your configuration will revert to what it was when you last had v6, so all changes made since then will be lost.
Of course you can export your config before you downgrade and import it after the downgrade, but it may be that edits in the export are required.
And of course you have to reset to a blank config before you can import an entire config. But maybe you only have a specific section where you made changes, and you can clear and import only that.

Thanks but it seems that v 7.2rc3 cannot be downloaded... (or where exactly?) the archive contains only stable releases, not beta and rc?

pe1chl · Thu Feb 24, 2022 4:02 pm

Ok indeed it seems the development release tree has been removed from that.
As always, I recommend to partition the router (if possible, not on 16MB FLASH devices) so you can always go back after an upgrade.
It seems most users do not know about that.

own3r1138 · Thu Feb 24, 2022 4:03 pm

Any ETA or update regarding the usage of DDNS at the WG endpoint and the tunnel would not be established after a reboot?

IntLDaniel · Thu Feb 24, 2022 4:11 pm

Ok indeed it seems the development release tree has been removed from that.
As always, I recommend to partition the router (if possible, not on 16MB FLASH devices) so you can always go back after an upgrade.
It seems most users do not know about that.

Any chance to get it now somewhere? I need mmips version.

Thu Feb 24, 2022 4:12 pm

Ok indeed it seems the development release tree has been removed from that.
As always, I recommend to partition the router (if possible, not on 16MB FLASH devices) so you can always go back after an upgrade.
It seems most users do not know about that.

It's still there, no ?
Copy the link for the latest version, paste in browser and change version to what you need (2 places).
E.g. for arm: https://download.mikrotik.com/routeros/ ... c4-arm.npk
change 7.2rc4 to 7.2rc3
-> https://download.mikrotik.com/routeros/ ... c3-arm.npk

Thu Feb 24, 2022 4:13 pm

Ok indeed it seems the development release tree has been removed from that.
As always, I recommend to partition the router (if possible, not on 16MB FLASH devices) so you can always go back after an upgrade.
It seems most users do not know about that.
Any chance to get it now somewhere? I need mmips version.

https://download.mikrotik.com/routeros/ ... -mmips.npk

memelchenkov · Thu Feb 24, 2022 4:13 pm

Thanks but it seems that v 7.2rc3 cannot be downloaded... (or where exactly?) the archive contains only stable releases, not beta and rc?

You may download it by direct link: https://download.mikrotik.com/routeros/ ... c3-arm.npk (I just replaced "4" from current download link published on the website to "3").

IntLDaniel · Thu Feb 24, 2022 4:14 pm

Any chance to get it now somewhere? I need mmips version.
https://download.mikrotik.com/routeros/ ... -mmips.npk

Thanks!!!! :-)

Kentzo · Thu Feb 24, 2022 5:23 pm

This info should be in the "priority" field present in each packet. That would be transferred to the priority in a VLAN tag, or it can be used (albeit with a detour via packet marks) in a queue tree.

Is it available in a bridge filter rule only or throughout RouterOS (incl. IP filter)? I hope automatic WMM -> VLAN priority is preserved when vlan is configured on a wlan too.

Unfortunately cannot test all of this at this time myself.

pe1chl · Thu Feb 24, 2022 5:49 pm

This info should be in the "priority" field present in each packet. That would be transferred to the priority in a VLAN tag, or it can be used (albeit with a detour via packet marks) in a queue tree.
Is it available in a bridge filter rule only or throughout RouterOS (incl. IP filter)? I hope automatic WMM -> VLAN priority is preserved when vlan is configured on a wlan too.

Yes that should work (unless there are bugs, of course...). The priority field remains with the packet as long as it is forwarded through the device (and is not overridden by some mangle rule), and it does not matter if a VLAN is used. Only when the packet is forwarded outside of the device this comes into play.
Unfortunately there is no option to do the usual DSCP->WMM priority mapping in RouterOS, so one will have to use a firewall mangle rule for that (e.g. "set priority from DSCP high 3 bits"), which when you want to apply it to bridged traffic implies that "use IP firewall for bridge" has to be set. (because bridge filter cannot set priority from DSCP)

sinisa · Thu Feb 24, 2022 7:03 pm

*) ups - fixed UPS support;

How exactly?
Router is hAP ac2. Upgrade to 7.2rc4 went without issues.
I have connected APC BackUPS ES 700G which worked fine with 6.x, but there is no System->UPS menu.
I can see that UPS is connected in System-Resources->USB
1 device="1-1" vendor="APC" name="Back-UPS ES 700G FW:871.O4 .I USB FW:O4 " serial-number="5xxxxxxxx " vendor-id="0x051d"
device-id="0x0002" speed="1.5" usb-version=" 1.10"

Where to go next?

Znevna · Thu Feb 24, 2022 7:36 pm

Ask them to replace whatever they are using for the UPS package with NUT and proper drivers, that should make the UPS package a little more useable.

infabo · Thu Feb 24, 2022 11:29 pm

@sinisa UPS is an extra package.

Znevna · Thu Feb 24, 2022 11:36 pm

I decided to give the 7.2rc* a try mainly to see what this does:
*) pppoe - use default MTU of 1492; (from 7.2rc1 changelog).
But the description of the fix seems wrong.
Findings:
PPPoE client running on ether1, ether1 MTU set to 1500, PPPoE client tries 1492 MTU and sets it right, so far so good.
Setting ether1 MTU to 1508 makes the PPPoE client to try for MTU 1500, so it seems the extra 12 bytes were removed from the math (previously this was happening when ether1 MTU was set to 1520).
BUT, if the client fails to negotiate 1500 for some reason (ISP doesn't support it etc) the PPPoE client falls back to 1480 instead of 1492.
So it seems that only those 12 bytes are gone but 1480 lives on in some part of the code.

noyp · Fri Feb 25, 2022 5:14 am

still dhcp-client is broken when cake queue type is applied in its queue tree interface, status is stuck at searching, strange that fq-codel doesnt have this issue

ormandj · Fri Feb 25, 2022 5:49 am

exports are mostly useless because they don't include certificates, um db, ssh keys, etc. which could easily be done by converting them into base64 and also storing them in the rsc/text file.
binary backups are (currently) also useless, because they store the entire database, and at the time of taking that backup nobody knows if it's already corrupted, and every time you have to restore that file, you'll end up having the same problem.

I think this is a great point. Figure out a way to handle exports with sensitive information in a secure way, but not as a binary backup. This frustrates me to no end when dealing with devices having issues, as I am unsure if I’m dealing with them related to some strange corruption in a backup file, since dealing with exports is so painful when operating under time constraints. Backups have many downsides when dealing with hardware swaps, differing versions, etc. I’m really surprised exports that support sensitive information haven’t been implemented with how easy it would be to generate and restore, and with the lessened support load regarding backups/restores.

osc86 · Fri Feb 25, 2022 9:39 am

you explained that a lot better than me, but it's exactly what I meant.
It was a pain to restore the router yesterday using an export file taken from the same device the night before.
There were some logical / ordering issues within the file, that wouldn't let me restore the config at once.
So I had to sit there with a text editor open and the router running /import .. verbose=yes, watching at which line the import failed, fixing it manually in a terminal and continue with /import .. from-line=x.

pe1chl · Fri Feb 25, 2022 10:50 am

Exactly that! There often are issues in the sequence of the exports and details of the parameters, I wonder if they even test that.
And the lack of a "continue on minor errors" during an import is a pain as well. Just print what is wrong and continue, so at least one has a reasonable config and can work from there.
E.g. older devices had LCD and more LEDs than newer devices, what is the point of aborting an import when a /lcd section is encountered on a device without LCD? Just ignore it!
And when loading in the same device, the messup between things that are not exported and are (or can be) kept when reloading causes problems too.
E.g. when you choose to "keep user information" it also keeps group configuration, but that IS included in a /export so the import fails on "group already exists". Arghh!!

It requires some changes that in fact are just minor touches, but have never been taken up no matter how often it has been discussed.
The procedure of restoring an existing router or migrating a router config to a new device (or a standby device one keeps ready in case there is a problem) is just painful with MikroTik.
The user (or admin) experience could be improved a lot.

sinisa · Fri Feb 25, 2022 10:58 am

@sinisa UPS is an extra package.

Thanks! I assumed it will be in the base package, 7.x being "monolithic" :)

Now I have installed UPS package, and... there is no "usbhid1" device, nor any other device offered in UPS->Add

So back to original question: how to configure APC BackUPS USB on 7.2rc4?

rpingar · Fri Feb 25, 2022 3:42 pm

testing v7.2rc4 as PPPoE server we get an issue describe in ticket [SUP-75504]:
on some cases (fast reauthentication from another parallel pppoe server) the router is not able to assign remote ip address. It is reported 0.0.0.0 in Active connection tab, but there is a remote ip address into the dynamic ppp interface and it is equal to last ip the client had in the parallel pppoe server where it was previously authenticated.

We have this same behavior in 7.1.3

regards
ros

benlg · Fri Feb 25, 2022 4:51 pm

[admin@MikroTik] > /ip/firewall/service-port/disable dccp 
failure: module dccp is built-in and cannot be individually disabled
[admin@MikroTik] > /ip/firewall/service-port/disable sctp 
failure: module sctp is built-in and cannot be individually disabled
[admin@MikroTik] > /ip/firewall/service-port/disable udplite 
failure: module udplite is built-in and cannot be individually disabled

SUP-75572 created accordingly.

benlg · Fri Feb 25, 2022 4:58 pm

Strange issue on RB5009 where the following rule does not handle the related ARP traffic :

/interface ethernet switch rule add dst-address=192.168.192.200/32 new-vlan-id=100 ports=ether2 switch=switch1

No issue on (for example) CRS317.
SUP-74646 created accordingly.

benlg · Fri Feb 25, 2022 6:59 pm

Strange issue on RB5009 where the following rule does not handle the related ARP traffic :
Code: Select all
/interface ethernet switch rule add dst-address=192.168.192.200/32 new-vlan-id=100 ports=ether2 switch=switch1
No issue on (for example) CRS317.
SUP-74646 created accordingly.

Finally, RB5009 switch chip is simply not able to handle dst-address related ARP traffic, while CRS317 has more advanced switch features, and so properly handles it.
Thank you for the explanation MikroTik support !

pe1chl · Fri Feb 25, 2022 7:27 pm

You probably will have more luck matching the MAC address to determine the VLAN...

mducharme · Fri Feb 25, 2022 11:12 pm

This version appears to fix the serious mipsbe 5ghz issues detailed here: viewtopic.php?t=182058

Why is there seemingly nothing in the changelog about this? It is like it was fixed silently. It was not working in 7.2rc3 and 7.1.3.

realmark · Sat Feb 26, 2022 12:08 am

*) switch - improved switch chip initialization process on bootup for CCR2004-16g-2s+ devices;

Please keep this forum topic strictly related to this particular RouterOS release.

Any word on what this initialization issue / change is? I've got some evidence that the CCR2004-16g-2s+ (running 7.1.1) is providing an open "dumb" switch for a short while during reboots. I haven't dug into this too far because I've got other things to deal with, but it'd be useful to know if it's a known issue with a fix in the pipeline.

manojlovicl · Sat Feb 26, 2022 10:16 am

Hi!

*) ppp - improved stability when handling large amount of connections simultaneously;

I am still having problems with PPP sessions - CCR that is running as PPP Server (OVPN) suddenly starts to duplicate sessions without eliminating old ones ... I found out that also configuration changes that are made when router is already making this problems are lost after reboot - like it does not permanently stores them...
I have 160+ OVPN Client connections (from MikroTik routers).

Luka

ssbaksa · Sat Feb 26, 2022 1:11 pm

Upgraded pair of RB750G routers from 7.2rc3 to 7.2rc4. Upgrade vent well but now I have this error message.
feb/26/2022 09:27:40 system,error,critical,,,,,,,,,radius error while running customized default configuration script: std failure: timeout (13)

Radius is not configured on any of those two routers. They are used for test only. VRRP and OpenVPN is configured on both of them.
BTW OpenVPN and VRRP don't play well together or I should say that they don't perform what I have expected.
When I simulate port failure on switch behind routers, connection is transferred but OpenVPN process is stuck to the port on main router and it newer goes down.
I know that I can script and do transfer that way but that isn't elegant way.

And what is critical in one second change? And console crashed to.
feb/26/2022 09:25:13 system,info,critical Firmware upgraded successfully, please reboot for changes to take effect!
feb/26/2022 09:27:40 system,error,critical,,,,,,,,,radius error while running customized default configuration script: std failure: timeout (13)
feb/26/2022 09:28:36 system,critical,info ntp change time Feb/26/2022 09:27:53 => Feb/26/2022 09:28:36
feb/26/2022 09:44:38 system,critical,info ntp change time Feb/26/2022 09:44:38 => Feb/26/2022 09:44:39
[admin@Test-Backup] >
Console has crashed; please log in again.

gittubaba · Sat Feb 26, 2022 9:03 pm

still waiting for container to be reintroduced :(

blurrybird · Sun Feb 27, 2022 5:14 am

RB5009 upgraded from 7.1.3 without issues. Rebooted again to upgrade firmware without issues.

Simple Queues with IPv6 are still broken.

Running this as my home router to see if anything explodes.

pe1chl · Sun Feb 27, 2022 11:56 am

Simple Queues with IPv6 are still broken.

I see no claim that this has been fixed... in general, one can say that when there is no mention in the changes, it is still broken.
(and it would only be worthwhile to report things that were fixed without mention in the changes)

loloski · Sun Feb 27, 2022 1:37 pm

@MT any estimation when Simple Queue + IPV6 will going to get fixed? our use case in production is simple enough no dynamic routing just plain NAT + PBR + Queue + IPV6 why is so hard for you guys to fix most of the IPV6 issue here?

In all fairness for most setup v7 is ok in our use case and we are ready to switch from v6 to v7, if only this main important function is working properly

loloski · Sun Feb 27, 2022 1:47 pm

by the way dot1x + EAP still broken in this release, if some people need this functionality stay away from v7.2rcx!!!

Grant · Sun Feb 27, 2022 10:00 pm

This version appears to fix the serious mipsbe 5ghz issues detailed here: viewtopic.php?t=182058

Why is there seemingly nothing in the changelog about this? It is like it was fixed silently. It was not working in 7.2rc3 and 7.1.3.

it's in the changelog :
*) queue - improved system stability when processing traffic;
*) queue - fixed traffic processing (introduced in v7.2rc2);

it works in 7.2rc3

mducharme · Mon Feb 28, 2022 1:01 am

*) queue - improved system stability when processing traffic;
*) queue - fixed traffic processing (introduced in v7.2rc2);

it works in 7.2rc3

What do queue fixes have to do with a 5ghz mipsbe wireless issue? And, no, I was running 7.2rc3 before this, so I can guarantee that these 5ghz mipsbe wireless issues were present in that version too.

benlg · Mon Feb 28, 2022 11:33 am

[admin@MikroTik] > /ip/firewall/service-port/disable dccp 
failure: module dccp is built-in and cannot be individually disabled
[admin@MikroTik] > /ip/firewall/service-port/disable sctp 
failure: module sctp is built-in and cannot be individually disabled
[admin@MikroTik] > /ip/firewall/service-port/disable udplite 
failure: module udplite is built-in and cannot be individually disabled

SUP-75572 created accordingly.

The kernel does not allow them to be turned off, according to MikroTik support.
Thank U !

Jotne · Mon Feb 28, 2022 12:54 pm

Both 7.2 rc3 and r4 does shows wrong in long term release
long term: 7.1
stable 7.1.3
testing 7.2 rc4
development: error: file not found.
Strange that 7.1.3 is stable and 7.1 is long term :)
.

long term.jpg

Znevna · Mon Feb 28, 2022 12:59 pm

What is wrong about that?

mducharme · Mon Feb 28, 2022 7:58 pm

Strange that 7.1.3 is stable and 7.1 is long term :)

7.1 isn't really long term. It is just there as a dummy placeholder until there is an actual long term v7.

Jotne · Mon Feb 28, 2022 8:21 pm

Then it should show up as testing:
development: error: file not found.
long term: error: file not found.

Now you are tricked to belive that 7.1 is a stable long term version. Yes I do now that it is not, but other may think so.

ivicask · Mon Feb 28, 2022 9:13 pm

I took the JUMP and hit the concrete on the bottom with my head!!

WTF Mikrotik!! Erase the routing tables (/routing/table), leaving me with setting about 50 different routing-marks all who are all over the place!!!!!

I started the recovery but ran out off breath doing them all and will think hard over it before trying to go from 7.1.1 to 7.2RC again. I went back to 7.1.1 and then restored the config and all worked again like a well oiled machine. oooooooooooooooooooooooof!

Is there not a better way change routing tables without let us running in to walls??

I have also lost all routing tables, i was upgrading from first V7 ever released thru all versions until this one and its first time it did something like that..
While it was easy fix by importing back from configuration export i hope it doesnt happen again Mikrotik
..

msatter · Mon Feb 28, 2022 9:34 pm

It is a easy fix but takes a lot of time to do. I rather wait till Mikrotik fix this bug and hope new are created doing so.

Mon Feb 28, 2022 9:37 pm

It is a easy fix but takes a lot of time to do. I rather wait till Mikrotik fix this bug and hope new are created doing so.

Wait a minute... you're hoping to see new bugs ?

Jotne · Mon Feb 28, 2022 9:46 pm

I took the JUMP and hit the concrete on the bottom with my head!!

WTF Mikrotik!! Erase the routing tables (/routing/table), leaving me with setting about 50 different routing-marks all who are all over the place!!!!!

I started the recovery but ran out off breath doing them all and will think hard over it before trying to go from 7.1.1 to 7.2RC again. I went back to 7.1.1 and then restored the config and all worked again like a well oiled machine. oooooooooooooooooooooooof!

Is there not a better way change routing tables without let us running in to walls??

If this was a production router in a company (with 50 routing-marks its not a home router), I would say that it 90% your fault.
1. Tesing a RC version in a production environment.
2. Not test on an equal router with same OS and Config as the production router.
3. With backup, you would only use some minute to downgrade to 7.1.1 and restore your backup. (what you did)
4. With 2500+ post you should know better.

In my 30+ year working with network and computing, I have seen many upgrade gone wrong.

pe1chl · Mon Feb 28, 2022 9:48 pm

3. With backup, you would only use some minute to downgrade to 7.1.1 and restore your backup.

Or better yet: PARTITION the router! Copy running version to 2nd partition, upgrade, when it is a disaster: make 2nd partition active, reboot, back in business.

Jotne · Mon Feb 28, 2022 9:51 pm

I guess that could not be done to all routers?

msatter · Tue Mar 01, 2022 12:24 am

It is a easy fix but takes a lot of time to do. I rather wait till Mikrotik fix this bug and hope new are created doing so.
Wait a minute... you're hoping to see new bugs ?

Makes it a difference then!? ;-)

msatter · Tue Mar 01, 2022 12:45 am

3. With backup, you would only use some minute to downgrade to 7.1.1 and restore your backup.
Or better yet: PARTITION the router! Copy running version to 2nd partition, upgrade, when it is a disaster: make 2nd partition active, reboot, back in business.

If the router goes up in smoke then I rather have backup and an export (off-site). If I can't get the same router again then I have still the export, to manually copy-and-paste.

@jotne why should I not have that many routing-marks in a home situation. Sorry, I anticipated something utterly stupid going wrong with this 'RC' as I wrote in the earlier posting in this tread...and it was.

I had my fare share of hairs turning white because of V7 so I was prepared to overcome any adverse and I could fallback petroleum lighting, and battery power if all went south after the update. ;-) It is time that Mikrotik is bringing out some kind of survival-kit special made for these kind of situations. Alone a Woobm won't cut it for non USB routers.

I expected it would go wrong, and it went wrong. It seems, that I have developed a special sense for this and that is why I am still on 7.1.1 and I will be patient as always and see if things happens in the lifespan I still got. No one knows their lifespan up front so it will be a surprise. ;-)

My other routers are still on 6.49.x and that is still sufficient for them and they run run and run on it.

pe1chl · Tue Mar 01, 2022 10:33 am

Or better yet: PARTITION the router! Copy running version to 2nd partition, upgrade, when it is a disaster: make 2nd partition active, reboot, back in business.
If the router goes up in smoke then I rather have backup and an export (off-site).

Of course you always make a backup, but for the depicted scenario of upgrading a router that is running in production to the next version of RouterOS, using partitioning is the best method.
In the past I encountered the situation where a remote router was upgraded and the new version made it crash. In case of partitioning it automatically switches the partitions and it came back in the old version running from the second partition.
No need to go there and do a netinstall or downgrade.

Jotne · Tue Mar 01, 2022 11:04 am

Most home ruter does only have 16MB, so to use multiple partition you need a larger router with at least 32MB
https://wiki.mikrotik.com/wiki/Manual:Partitions

pe1chl · Tue Mar 01, 2022 12:37 pm

Most home ruter does only have 16MB, so to use multiple partition you need a larger router with at least 32MB
https://wiki.mikrotik.com/wiki/Manual:Partitions

Yes you need some space. That page is incorrect saying "Partitioning is supported on MIPS, TILE and PowerPC RouterBOARD type devices.", I have a RB4011 as home router (ARM) and it works there. This device has 512MB of space (a bit of a useless in-between value, too much for a single or dual partition of RouterOS, not enough to do a lot with Docker containers later...).
I see that some of the newly announced devices again have 128MB of flash space. So it seems MikroTik has finally seen the light and provides more than 16MB.

eworm · Tue Mar 01, 2022 12:39 pm

Partitioning also works on ARM64, successfully tested with CCR2004-1G-12S+2XS.

raymondr15 · Wed Mar 02, 2022 1:41 pm

Routing filters seem to not be working in v7.2rc4.

pe1chl · Wed Mar 02, 2022 2:08 pm

Routing filters seem to not be working in v7.2rc4.

Here they work fine. Do you use the "Set" features? (now renamed to "List")
(Num Set, Community Set, etc)

memelchenkov · Wed Mar 02, 2022 2:08 pm

- Some problems with switching Wi-Fi networks (different SSIDs on the same router). Hardware (phone, notebook) reports "Network not found", but on the second try it connects OK. Not happened with 7.1.3.
+ Performance a lot better than before (CPU monitoring show normal load at 100 Mbps routing rather than almost full as was before).

Znevna · Fri Mar 04, 2022 4:55 pm

Can wireguard/peers current-endpoint and current-endpoint-port be added to winbox/webfig too?
Currently it is only visible with

/interface/wireguard/peers/print detail

Thank you!

Sat Mar 05, 2022 9:30 am

rtlx - As many as necessary.
obscurus, noyp - We will look into this.
Ullinator, eworm, blurrybird, loloski - It is fixed, but not in this release. Fix will be included in the next one.
pe1chl, msatter, CTassisF, osc86, IntLDaniel, ivicask - Very sorry for missing routing configuration after an upgrade. We are working on a fix for this.
CTassisF, hecatae, sirbryan, ssbaksa, loloski, memelchenkov- Please send supout file from this router, generated while in the problematic state, to support@mikrotik.com.
MikroTikTack - Thank you for report. We will fix this as soon as possible.
wojo - That is correct. We are working on a fix.
pe1chl, holvoetn - WinBox dependencies are made when it is absolutely necessary. We are not doing this without any reason. Please report problems with WinBox 3.35 to support@mikrotik.com so we can fix them. Without knowing them, we can not fix them.
elgrandiegote - To what changes are you referring to? If you refer to reboots, then they should be fixed in the next release.
buset1974, obscurus, Chupaka - We will look into this.
IntLDaniel - First of all, there is a download archive (https://mikrotik.com/download/archive). Also, you can take a download link from any version and simply edit the version number and platform in the URL.
own3r1138 - The problem with tunnel establishment after a reboot should be fixed. We will look into the problem with DDNS.
sinisa - Additional fixes will be included in the next release.
Znevna - Please provide supout file to support@mikrotik.com when MTU is set to 1480, instead of 1492.
osc86, pe1chl - If you notice such problems, then please report them to us through the official support channel - support@mikrotik.com. Provide examples so we can fix them.
mducharme - There are no direct fixes regarding such an issue. Maybe your problem was resolved by some unrelated fix, which in the end was to blame for the problems that you were experiencing.
realmark - On some very, very, very rare cases on bootup switch chip sometimes was not properly initialized. We fixed this problem.
manojlovicl - We are trying to reproduce this problem but at the moment no luck. Can you provide supout file from your server to support@mikrotik.com? Make sure that you generate file while duplicate sessions are present on the router.
gittubaba - You do not need to wait for long. Soon it is coming back.
raymondr15 - Please provide examples of rules that are not working properly to support@mikrotik.com.
Znevna - Will be added in the upcoming releases.

Everyone - there was no and is no a simple and perfect way how to transition from v6 to v7. We do consider this the least harmful way. We will slowly transit versions between channels until we reach a state when v7 has two reliable version trees (long-term and stable) and one for testing purposes (testing). It will take a while and many RC and beta versions are yet to come. Also, nobody is obligated to upgrade. If you are just fine with an older version, then you can simply wait for a while or try out upgrades on test setups - this is completely up to you.

wispmikrotik · Sat Mar 05, 2022 9:46 am

Thanks Mikrotik!

We are eagerly awaiting the next RC with the bug fixes.

pe1chl · Sat Mar 05, 2022 11:30 am

pe1chl, holvoetn - WinBox dependencies are made when it is absolutely necessary. We are not doing this without any reason. Please report problems with WinBox 3.35 to support@mikrotik.com so we can fix them. Without knowing them, we can not fix them.

Do you really need a mail to support, incurring extra work for you, to know about problems? Would it not be easier to read the comments on the release topic, as you clearly are doing for the v7 rc releases? Especially when there is a new problem introduced in a winbox release, and everyone is writing about it in the release topic, I would expect that to be looked at at high priority as it is still a fresh change and likely easier to fix.

osc86, pe1chl - If you notice such problems, then please report them to us through the official support channel - support@mikrotik.com. Provide examples so we can fix them.

It is difficult to know what you mean by "such problems" when only the username is quoted and the user posted several messages in the topic. I regularly send issues to the Jira system, I suppose that is equivalent to mailing them to support.
Maybe in this case you are referring to "problems with importing a /export file". I have posted several times here what is wrong with the import mechanism. I hope that once v7 is fixed to have feature completeness and bug counts equal to v6, someone at MikroTik can work on the whole mechanism of importing (both the /import command and the "run script after full reset" feature) which have serious issues that you should be well aware of. As it is now, it is *really painful* to transfer a config to another device or to rebuild a device after a netinstall (and not wanting to restore a backup).

About the whole "v7" thing...: well, you should be aware of the fact that some devices can only run v7. Also, v7 is presented prominently on the software download page as a stable release, which makes some people do the upgrade at a time they probably should not do that yet.
I surely understand that there is a lot of work to do, but I think many of us would prefer if all efforts are first concentrated on making v7 a worthy replacement of v6, where the same features work at the same quality level, and only then work is done on extending v7 with new features.
We are running a network operated by hobbyists and volunteers, which is heavily relying on BGP functionality, and I am holding my breath as more and more operators "discover" v7 and upgrade to it, causing frequent issues in the network. Sure it would have been better when we had a well functioning contact platform where I could send messages to all users requesting them not to upgrade, but we don't have that. So I am hoping that BGP will "soon" be again on par with v6 quality.

elgrandiegote · Sat Mar 05, 2022 5:09 pm

elgrandiegote - To what changes are you referring to? If you refer to reboots, then they should be fixed in the next release.

I am referring to the disconnections made by the server in udp mode, where the session ends at the request of the server and not reconnect.

buset1974 · Mon Mar 07, 2022 3:06 am

About the whole "v7" thing...: well, you should be aware of the fact that some devices can only run v7. Also, v7 is presented prominently on the software download page as a stable release, which makes some people do the upgrade at a time they probably should not do that yet.
I surely understand that there is a lot of work to do, but I think many of us would prefer if all efforts are first concentrated on making v7 a worthy replacement of v6, where the same features work at the same quality level, and only then work is done on extending v7 with new features.
We are running a network operated by hobbyists and volunteers, which is heavily relying on BGP functionality, and I am holding my breath as more and more operators "discover" v7 and upgrade to it, causing frequent issues in the network. Sure it would have been better when we had a well functioning contact platform where I could send messages to all users requesting them not to upgrade, but we don't have that. So I am hoping that BGP will "soon" be again on par with v6 quality.
Agree, v7 is not a beta anymore, it's a stable version, specially for their flagship product such as CCR, but there is a lot of homework must be fixed fast, specially for advance dynamic routing such as BGP.

WeWiNet · Mon Mar 07, 2022 10:15 am

Question on "kid-control" in 7.2r4! (Not sure I saw this in earlier R7 releases...)

Kid-control adds a very first forward rule into firewall in the forward chain, which jumps straight to the end of rules, to the individual kid-control device rules. They are the last ones in firewall.
But this jump rules seems to apply to ALL TRAFFIC! It is a generic rule and I could not find inside the rule any info why this would apply to the kid-control device only!
How does this rule know which device / interface to use and which not?

/ip firewall filter
add action=jump chain=forward comment="jump to kid-control rules" jump-target=kid-control

It seems the rules between the jump and the jump targets are still hit (counters increase), but I don't understand why?
I don't like in firewall things to happen which are not fully understood, especially as the jump target rules are last, there is no drop-all rule
anymore afterwards for forward traffic.

Bug or feature?

pe1chl · Mon Mar 07, 2022 10:38 am

You should understand that the name "jump" is inappropriate (when you have a programming background), it really should have been named "call".
I.e. it will execute the rules found in the chain kid-control, but when there is no rule that matches the traffic and has an action like "accept" or "drop", when the end of the rule set is reached it will "return" to the place where the "jump" was done and continue there.
So it is more like a subroutine call than a jump (goto).
Each "chain" in the firewall is separate, the firewall is called at the "forward" (and "input" and "output") chain but internally it can call other chains as subroutines.

Ullinator · Fri Mar 11, 2022 6:59 pm

The problem with the irregulary broken fiber connections with 10GB is still present in 7.2RC4.
I´ve updated yesterday all my MikroTik Devices from 6.48.6 over 6.49.4, 7.1.3 (via upgrade) to 7.2RC4. (RB5009, CRS326-24S+2Q+, CRS328-24P-4S+, RB4011, CRS32624G2S+, 5x CAP AC).
After the update the fiber connection between the CRS326-24S+2Q+ and the CRS328-24P-4S+ began to toggle. Every 5 min. the connection was broken. After deactivation of Graphing the disconnection happend ~ every 20-30 min.
This behaviour didn´t happen with ROS 6.48.6 or 6.49.4 and I only upgraded the ROS, nothing else.
Only the deactivation of "Auto Negotiation" and the fixing to 1GB stopped the diconnections to ~1x per day.
The cable between both devices is ~35m (2x)
The problem exists also with 7.0.5, the days where I´ve tried this ROS version I´ve also changed the cables without success. So the problem exists inside ROS 7.X
(https://help.mikrotik.com/servicedesk/s ... /SUP-71233)

ormandj · Sat Mar 12, 2022 1:47 am

The problem with the irregulary broken fiber connections with 10GB is still present in 7.2RC4.
I´ve updated yesterday all my MikroTik Devices from 6.48.6 over 6.49.4, 7.1.3 (via upgrade) to 7.2RC4. (RB5009, CRS326-24S+2Q+, CRS328-24P-4S+, RB4011, CRS32624G2S+, 5x CAP AC).
After the update the fiber connection between the CRS326-24S+2Q+ and the CRS328-24P-4S+ began to toggle. Every 5 min. the connection was broken. After deactivation of Graphing the disconnection happend ~ every 20-30 min.
This behaviour didn´t happen with ROS 6.48.6 or 6.49.4 and I only upgraded the ROS, nothing else.
Only the deactivation of "Auto Negotiation" and the fixing to 1GB stopped the diconnections to ~1x per day.
The cable between both devices is ~35m (2x)
The problem exists also with 7.0.5, the days where I´ve tried this ROS version I´ve also changed the cables without success. So the problem exists inside ROS 7.X
(https://help.mikrotik.com/servicedesk/s ... /SUP-71233)

You’re not the only one. Exact same issue here. My ticket is: SUP-68278 which was last updated by Mikrotik Dec. 23. I’ve posted in these threads about it before and been told to create a new support ticket… The same resolution (auto-negotiation off/1G fixed) “works” for me, but this is obviously not a fix.

xtrans · Sat Mar 12, 2022 2:34 am

Bridge port gone after reboot

leoservices · Sun Mar 13, 2022 4:16 am

Today I did some tests with L2TPv3 Ethernet: ROS 7.1.3 and ROS 7.2rc4
- After creating an L2TP Ethernet it is not possible to deactivate it, if you try to deactivate it, it activates itself immediately.
L2TPv3 worked for a while but then it fails to establish the tunnel again.

When capturing the packets with Wireshark I have the message Digerst ( Expert Info (Warning/checksum): Incorrect Digest

I was just studying about L2TPv3 on RouterOS

Router2
/interface l2tp-ether
add allow-fast-path=no circuit-id="" connect-to=2.2.2.1 cookie-length=0 digest-hash=md5 disabled=no l2tp-proto-version=l2tpv3-udp mac-address=\
FE:A8:86:3C:4E:99 mtu=1420 name=l2tp-ether1 use-ipsec=no use-l2-specific-sublayer=no

Router1
/interface l2tp-server server
set enabled=yes

Znevna · Mon Mar 14, 2022 1:41 pm

Znevna - Please provide supout file to support@mikrotik.com when MTU is set to 1480, instead of 1492.

I've reopened SUP-38224 since it was about the same thing and provided a supout, thank you.

riv · Mon Mar 14, 2022 3:50 pm

snmpwalk towards loopback (bridge) IP doesn’t work

But snmp towards the same loopback’s IPv6 address works just fine

benlg · Tue Mar 15, 2022 9:34 am

In 7.2rc1 :

*) ipsec - added hardware acceleration support for CCR2116;

@MikroTik support, could you then please add ipsec numbers to CCR2116 product page ?
https://mikrotik.com/product/ccr2116_12 ... estresults

Also note that there's no block diagram and no performance numbers at all for the CCR2216 :
https://mikrotik.com/product/ccr2216_1g ... ifications
Could you please add them ?

Many thanks !

Znevna · Tue Mar 15, 2022 10:07 am

Here's your MikroTik CCR2216-1G-12XS-2XQ Block Diagram, each line is 25Gbps.

MikroTik CCR2216-1G-12XS-2XQ.jpg

And performance numbers:

MikroTik CCR2216-1G-12XS-2XQ Performance Numbers.jpg

And L3HW capabilities:

MikroTik CCR2216-1G-12XS-2XQ L3HW.jpg

benlg · Tue Mar 15, 2022 10:23 am

Many thanks @Znevna for the CCR2216 details.
Would also be nice to have some numbers without l3hw, so that we would know what to expect from this device once hardware table is full (or if l3hw is intentionally disabled).
Same for CCR2116 of course.
@MikroTik support ? :-)

And for CCR2116 ipsec numbers, I think we'll need @MikroTik support, to have their test procedure applied, to get a proper comparison to other models.
Thank you again !

wispmikrotik · Wed Mar 16, 2022 11:40 am

@strods
Sat Mar 05, 2022 8:30 am

Do we have a date for the new rc with bug fixes, and possible feature additions?

Regards,

pe1chl · Wed Mar 16, 2022 12:00 pm

@wispmikrotik: there is no need to quote text to be able to reply in this forum, you can just use the Quick Reply field or the Post Reply button at the bottom of the list.

wispmikrotik · Wed Mar 16, 2022 12:43 pm

@pe1chl Do you like it better like this?

mafiosa · Wed Mar 16, 2022 1:28 pm

RB5009 crashed twice within 72 hours. Very tragic experience.

benlg · Wed Mar 16, 2022 8:13 pm

Strangely enough, the following command does not drop gre connections :

/ip firewall connection remove [find]

SUP-77175 created accordingly.

Jotne · Wed Mar 16, 2022 9:07 pm

It removes the GRE connection on 6.x and 7.1.3?

benlg · Wed Mar 16, 2022 9:43 pm

I tested 6.48.5, 7.1.1, 7.1.3, 7.2rc4, all have the issue.
Very old bug perhaps ?

Jotne · Wed Mar 16, 2022 10:42 pm

Or not an bug at all. It may be by design. You posted it in this thread, so it is to assume that this was related to 7.2rc4.
This may be posted to support@mikrotik.com as a future request or as a bug if it ever has worked.

buset1974 · Thu Mar 17, 2022 5:32 am

i'am waiting day by day for the next rc

Ullinator · Fri Mar 18, 2022 10:27 am

My CAPsMAN (RB4011iGS+5HacQ2HnD) crashes several times a day with 7.2RC4. (Log: "router was rebooted without proper shutdown")
The configuration is simple and fresh, nothing special.
This didn´t happen with ROS 6.4X.X.
Waiting also for a fixed new RC... :-/

(SUP-77336)

mkx · Fri Mar 18, 2022 10:51 am

If you can experiment: if you disable CAPsMAN on RB4011, do crashes cease to happen?

Fri Mar 18, 2022 10:55 am

If you can experiment: if you disable CAPsMAN on RB4011, do crashes cease to happen?

Adding:
Depending on how you arrived at this version 7.2rc4 (starting somewhere at ROS6 and then upgrade and upgrade and upgrade ...)
If previous suggestion still results in crashes, you can try to start with CLEAN DEFAULT config, restoring config manually line by line from previous export (you mention the config is pretty basic so should be done rather quickly).

Ullinator · Fri Mar 18, 2022 10:59 am

If you can experiment: if you disable CAPsMAN on RB4011, do crashes cease to happen?

It´s it main role (CAPsMAN). I would loose all my WLAN on my 5 CAP AC´s, so it´s not really a choice to do so.... :-(
I´ve tried 7.1.3 with clean config also, but it doesn´t work very well (WLAN Veeery sloooow and regulary discoonections of my WLAN dfevices)
After downgrade to 6.48.6 I also start from scratch and rebuild the config via Terminal....it worked fine with 6.48.6 :-/
Start to think about to go back to Long-Term....

Fri Mar 18, 2022 11:03 am

I´ve tried 7.1.3 with clean config also, but it doesn´t work very well (WLAN Veeery sloooow and regulary discoonections of my WLAN dfevices)

It seems there were some WLAN-related fixes with 7.2rc4 (but nothing was really mentioned in the change log, users just noticed ...)

jult · Fri Mar 18, 2022 3:37 pm

I´ve tried 7.1.3 with clean config also, but it doesn´t work very well (WLAN Veeery sloooow and regulary discoonections of my WLAN dfevices)
It seems there were some WLAN-related fixes with 7.2rc4 (but nothing was really mentioned in the change log, users just noticed ...)

I updated our Metal 52 because of what you mention here. Is it required to also upgrade Routerboard firmware, or will just the packages do, do you know?

mkx · Fri Mar 18, 2022 3:48 pm

Is it required to also upgrade Routerboard firmware, or will just the packages do

It's not required to upgrade routerboot, in theory when ROS boots routerboot doesn't matter any more. However, there were moments in history when older routerboot simply wasn't able to boot new ROS (or keep it running stably, such occasion was introduction of ROS v7, routerboot older than around 6.48 could not boot it). So generally it's advisable to upgrade routerboot with ROS ... unless routerboot upgrade actually breaks something (usually it doesn't but ocassionally it does).

Buckeye · Sun Mar 20, 2022 1:40 am

Is there any support for ZeroTier on Hex-S (mmips) in this v7.2rc4?

No

[demo@MikroTik] > /system routerboard print
       routerboard: yes
        board-name: hEX S
             model: RB760iGS
     serial-number: 
     firmware-type: mt7621L
  factory-firmware: 6.46.4
  current-firmware: 6.47.10
  upgrade-firmware: 7.2rc4
[demo@MikroTik] > [tab]
caps-man     interface  partitions  routing        user    password
certificate  ip         port        snmp           beep    ping    
console      ipv6       ppp         special-login  blink   quit    
disk         log        queue       system         export  redo    
file         mpls       radius      tool           import  undo    
[demo@MikroTik] >

loloski · Sun Mar 20, 2022 4:10 pm

nope, only arm32 and arm64 no plans for other architecture atm as per MT

Jotne · Sun Mar 20, 2022 4:37 pm

no plans for other architecture atm as per MT

I know its only arm yet. Can you post a link to where MT stats that there will be no ZeroTier for other platform?

felixka · Sun Mar 20, 2022 11:27 pm

I know its only arm yet. Can you post a link to where MT stats that there will be no ZeroTier for other platform?

viewtopic.php?t=178353#p890747

Sun Mar 20, 2022 11:31 pm

From what I understood it is a license issue. Too much to be paid when adding all other architectures.
Hopefully Normis can confirm.

Jotne · Mon Mar 21, 2022 8:04 am

viewtopic.php?t=178353#p890747

We only can do it for ARM systems, no plans for MIPS now.

That is not the same as that there will never be.

It may come in future.
We only can do it for ARM system (since we do not have time, or missing a component, or to little memory or...)

Buckeye · Mon Mar 21, 2022 9:14 am

Wouldn't you need to load a package before it would show the ZT directory? Are they working on a package to enable ZT on this version I guess was my question...

You are correct, I didn't have any extra packages loaded. But I don't think MikroTik currently has anything for non ARM processors.

However, the zerotier site has some MIPS64 support, for example https://docs.zerotier.com/devices/ubiquiti/ show the cavium based edgerouters, but not the MediaTek MT7621A based edgerouters like the ER-X. But someone supposedly had ZeroTier working on an ER-X, I don't know if they recompiled from source, and whether the latest version works.

Under OpenWRT they say you can no longer compile using uClibc++ without any explanation.
Note: Zerotier >1.1.14 cannot be compiled with uClibc++ anymore.

But I agree that having ZeroTier on the MMIPS hEX (RB750Gr3), hEX S (RB760iGS), RBMxx would be nice.

th0massin0 · Mon Mar 21, 2022 9:49 am

Is SSTP fixed in this release? In 7.1.3 is still broken (100% CPU usage without any reason); checked on CHR. Reported as SUP-67642.
To be honest, that's the main reason for not using CHR v7 in production environment.

Ullinator · Mon Mar 21, 2022 10:37 am

The problem with the irregulary broken fiber connections with 10GB is still present in 7.2RC4.
I´ve updated yesterday all my MikroTik Devices from 6.48.6 over 6.49.4, 7.1.3 (via upgrade) to 7.2RC4. (RB5009, CRS326-24S+2Q+, CRS328-24P-4S+, RB4011, CRS32624G2S+, 5x CAP AC).
After the update the fiber connection between the CRS326-24S+2Q+ and the CRS328-24P-4S+ began to toggle. Every 5 min. the connection was broken. After deactivation of Graphing the disconnection happend ~ every 20-30 min.
This behaviour didn´t happen with ROS 6.48.6 or 6.49.4 and I only upgraded the ROS, nothing else.
Only the deactivation of "Auto Negotiation" and the fixing to 1GB stopped the diconnections to ~1x per day.
The cable between both devices is ~35m (2x)
The problem exists also with 7.0.5, the days where I´ve tried this ROS version I´ve also changed the cables without success. So the problem exists inside ROS 7.X
(https://help.mikrotik.com/servicedesk/s ... /SUP-71233)

Something new on this topic.
First of all my fiber connections are bonded with LACP. Yesterday I´ve changed my settings within the Bonding set, specially the "Transmit Hash Policy" from "Layer 2" to "Layer 2 and 3" and the disconnections are gone (until now for more than 24h) and my latency in the LAN went dramatically down from >30ms to 1-2ms :-)
So something may have been changed with ROS7 and LACP, but I don´t know what has changed......

"To whom it may concern....." ;-)

jult · Tue Mar 22, 2022 10:58 am

I´ve changed my settings within the Bonding set, specially the "Transmit Hash Policy" from "Layer 2" to "Layer 2 and 3" and the disconnections are gone (until now for more than 24h) and my latency in the LAN went dramatically down from >30ms to 1-2ms :-)

Have you ever tried setting it to "layer 3 and 4" ? This is by far recommended over all others for LACP.

jult · Tue Mar 22, 2022 11:06 am

*) wifiwave2 - added "client-isolation" feature;

Is this feature available for all wireless interfaces? Or is wifiwave2 some special device?

Tue Mar 22, 2022 11:33 am

*) wifiwave2 - added "client-isolation" feature;
Is this feature available for all wireless interfaces? Or is wifiwave2 some special device?

See https://help.mikrotik.com/docs/display/ROS/WifiWave2

For now only:
hAP ac³ (non-LTE)*
Audience*
Audience LTE6 kit*
RB4011iGS+5HacQ2HnD**

Ullinator · Tue Mar 22, 2022 11:48 am

I´ve changed my settings within the Bonding set, specially the "Transmit Hash Policy" from "Layer 2" to "Layer 2 and 3" and the disconnections are gone (until now for more than 24h) and my latency in the LAN went dramatically down from >30ms to 1-2ms :-)
Have you ever tried setting it to "layer 3 and 4" ? This is by far recommended over all others for LACP.

Thanks for the tipp, I´ve implemented it right some minutes ago and will keep an eye on it ;-)

emils · Wed Mar 23, 2022 4:01 pm

New version v7.2rc5 has been released:

viewtopic.php?t=184351

Who is online