v7.1.3 is released!

Announcements
1

RouterOS version 7.1.3 has been released “v7 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 7.1.3 (2022-Feb-11 21:20):

*) bridge - fixed PPPoE packet forwarding when using “use-ip-firewall-for-pppoe” setting;
*) bridge - fixed bridge filter and NAT rules on ARM64 and TILE devices;
*) bridge - fixed filter and NAT “set-priority” action;
*) conntrack - properly detect helper status;
*) crs3xx - fixed watchdog timer functionality;
*) ppp - improved stability when handling large amount of connections simultaneously;
*) sms - increased “at-chat” timeout when sending SMS;
*) switch - improved switch chip initialization process on bootup for CCR2004-16g-2s+ devices;
*) vxlan - allow unsetting “group” and “interface” properties;
*) vxlan - fixed running state after reboot when using “interface” and “group” settings;
*) wireless - correctly preserve WMM priority when receiving packets;
*) wireguard - fixed IPv6 traffic processing with multiple peers;

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.

2

Fix confirmed, my issue is gone :slight_smile:

3

So the issues with 3011 that was reported on the forum (bootloop etc) for 7.1.2 is that a confirmed issue that has been solved here? Looked to be more related to firmware then ROS.

4

This time my CCR1009-7G-1C-1S+ entered boot loop… :flushed_face::cry:
Have not seen this in a long time myself.

5

PPPoE MTU is still at 1480.

6

PPPoE Client?

7

Update on HEX S (MMIPS) from 7.1.2 to 7.1.3 without problems (ROS and RouterBoard-FW)

8

Update on 5009 from 7.1.1 to 7.1.3 without problems too

9

this simple routing rule still does not work:

 0   chain=cymru-in rule="if ( bgp-communities includes 65332:888 ) { accept } else { reject }"

all routes are rejected although they contain the right community:

 Fb   afi=ip4 contribution=filtered dst-address=23.151.160.0/24 routing-table=main gateway=1.2.3.4 immediate-gw=5.6.7.8%ether5_832 distance=20 scope=40 target-scope=30 
       belongs-to="BGP IP routes from 1.2.3.4" 
       bgp.peer-cache-id=*B000004 .as-path="65332" .communities=65332:888,no-export .atomic-aggregate=yes .origin=igp 
       debug.fwp-ptr=0x20302360

Mathieu

10

*) wireguard - fixed IPv6 traffic processing with multiple peers;

still only one peer can use ipv6, not fixed

11

Any chance to fix problem with disconnecting wireguard peer when endpoint is set by domain (not an IP)? Issue is described here:
http://forum.mikrotik.com/t/mikrotik-wireguard-peer-does-not-start-on-reboot/154038/34

12

This release does not break my hAP lite (SMIPS).

13

For me such rules do work OK. I would advise trying to put the community in a community list and then reference that in the rule.
The syntax for that is [[:name:]] (instead of 65332:888).
It fixed the problem for me when matching AS number.

14

I was going to wait, but I decided to try it. From 6.49.3 to 7.1.3 on RB750gr3, with netinstall. So far, so good, as far as I can tell. It’s using about 15MB more RAM than before. My setup is pretty vanilla, though I am using IPv6.

I do notice this new hardware offloading:

add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related hw-offload=yes

(log)
hardware offloading activated on bridge "bridge" ports: ether5,ether4,ether2,ether3

So that’s nice.

15

That hardware offloading is not new, unless you use a bridge with vlan filtering.
The log message refers to bridge offloading (i.e. usage of the switch chip).

16

I thought I read it was new for v7 (perhaps not v7.1.3 exactly), though I could be wrong. I know that “hw-offload=yes” wasn’t in the same configuration I had in v6.

17

Any progress on bgp and mpls?

18

Sure, but the message that it is activated is not related to that. It is related to bridge offloading and it was also there in v6.

19

Unfortunately, all of the SFP+ ports are still flapping in 7.1.x for me, even with 7.1.3, on a CRS328-24P-4S+. Forcing the interfaces to 1G fixes the problem, but then I lose 10G. It happens at regular 5 minute intervals, which is extremely suspicious.

Screen Shot 2022-02-21 at 12.39.22.png
There hasn’t been an update to SUP-68278 since December 23rd about this.

20

Yes