v7.2rc6 and v7.2rc7 is released!

emils · Wed Mar 30, 2022 11:36 am

RouterOS version 7.2rc6 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.2rc7 (2022-Mar-30 15:21):

*) route - allow OSPF and RIP redistributed routes to be matched by routing filters;

What's new in 7.2rc6 (2022-Mar-30 10:56):

*) ccr2004 - improved PCI timeout handling on CCR2004-1G-2XS-PCIe;
*) dude - fixed The Dude compatibility with ARM64;
*) l2tp - improved service stability when disabling L2TP server with connected clients;
*) l3hw - fixed default route offloading for CRS305, CRS326-24G-2S+, CRS328, netPower, netFiber devices;
*) lte - enabled multi-APN and name re-use support for Chateau;
*) lte - improved stability when modem disappears during firmware upgrade;
*) ntp - improved source address usage for reply packets;
*) ospf - properly set VRF for gateway;
*) poe - fixed PoE driver loading on CRS354-48P-4S+2Q+;
*) route - allow OSPF and RIP redistributed routes to be matched by routing filters;
*) route - fixed "table" menu emptying after RouterOS upgrade;
*) switch - properly limit maximum number of switch rules to 256 on RB5009;
*) tr069-client - fixed RPC download of "3 Vendor Configuration File" with branding package;
*) x86 - fixed VLAN tagged packet transmit;

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.

zainarbani · Wed Mar 30, 2022 12:10 pm

nice!

th0massin0 · Wed Mar 30, 2022 12:18 pm

Could you please resolve SUP-67642? (SSTP is unusable in CHR)

pe1chl · Wed Mar 30, 2022 12:39 pm

nice!

It looks like a minor release with a couple of quick fixes. Still hoping for major work on e.g. BGP to be finished.

tpedko · Wed Mar 30, 2022 12:46 pm

When will container support be added?

fischerdouglas · Wed Mar 30, 2022 12:49 pm

I would say the lack of release notes being fteched via internal tool is a cosmetic bug, but surely some would pick up rocks and sticks to attack me...

Mikrotik_7.2rc6_ReleaseNotes_unupdated.jpg

pe1chl · Wed Mar 30, 2022 12:52 pm

I would say the lack of release notes being fteched via internal tool is a cosmetic bug, but surely some would pick up rocks and sticks to attack me...

This happens every time so shortly after the release announcement. It probably is some caching/synchronization issue. Wait some time and it will be correct.

huntermic · Wed Mar 30, 2022 1:22 pm

Please fix partitioning on RB5009, partitioning is very much wanted when testing rc's.

viewtopic.php?p=921392

psannz · Wed Mar 30, 2022 1:28 pm

When will container support be added?

I‘d guess we’ll see it again in 7.3

pe1chl · Wed Mar 30, 2022 1:28 pm

I agree partitioning is important when testing! Fortunately it works on my 4011 but I agree it should work on all devices with sufficient storage.
(I would even like to see it added to CHR)

Paternot · Wed Mar 30, 2022 2:04 pm

It looks like a minor release with a couple of quick fixes. Still hoping for major work on e.g. BGP to be finished.

Don't we all. But I like this "release early and release frequently" way: much better than a giant beta each two months. Let's hope they keep it this way from now on.

fragtion · Wed Mar 30, 2022 2:16 pm

Agreed. Regular small updates means the community can immediately start testing fixes and features on a more granular level meaning a more constant and organised/consistent flow of feedback to support team and opportunity to fix bugs before next incremental version update.

Really excited to see The Dude support fixed for ARM64. This means RB5009 users can use Dude in their network for the first time ever on this device. Good job Mikrotik!!

Jotne · Wed Mar 30, 2022 2:57 pm

Is RC the new Beta? I do not see that any beta has been posted for 7.2, but multiple RC. (6 so far)
7.1 was some inn between with 6 rc and 6 beta (Posted)

6.49 - 2 rc
6.48 - 1 rc
6.47 - 1 rc
6.46 - 1 rc
6.45 - 2 rc
6.44 - 1 rc

Znevna · Wed Mar 30, 2022 3:23 pm

What is the problem that you are reporting with this specific 7.2rc6 and what does it have to do with 6.4x versions?

pe1chl · Wed Mar 30, 2022 4:27 pm

It looks like a minor release with a couple of quick fixes. Still hoping for major work on e.g. BGP to be finished.
Don't we all. But I like this "release early and release frequently" way: much better than a giant beta each two months. Let's hope they keep it this way from now on.

Of course I like it that fixes for problems that were blocking for some people are released in such an intermediate version. In fact I wish that v7 is made feature complete and reasonable stable ASAP so it can replace v6 in the field. This set of fixes at least concentrates on actual problems and not on new subsystems.
My only gripe is that BGP does not get enough love...

pietroscherer · Wed Mar 30, 2022 4:40 pm

Hello,

Any plans to add IPv6 support for l3hw?

Wed Mar 30, 2022 5:20 pm

Hello,

Any plans to add IPv6 support for l3hw?

IPv6 L3HW is currently in development. However, it is not going to be included in v7.2.

guipoletto · Wed Mar 30, 2022 5:39 pm

7.1.5 and 7.2rc1-6 cause 100% CPU usage and reboots by OOM on the HAP-Lite

mikegleasonjr · Wed Mar 30, 2022 5:51 pm

How come SUP-59224 has been closed while nothing as been done on that front?

Can we specify the direction of the Cake queue please so that we start testing and managing the bandwidth properly. I imagine we will find bugs so now should be the time to implement it no?

pe1chl · Wed Mar 30, 2022 6:16 pm

7.1.5 and 7.2rc1-6 cause 100% CPU usage and reboots by OOM on the HAP-Lite

On the HAP-Lite (and HAP-Mini) it is best to install the 6.47.9 long-term version and not upgrade any further. Later versions include "fragattack fixes" that kill the performance.

Jotne · Wed Mar 30, 2022 6:23 pm

What is the problem that you are reporting with this specific 7.2rc6 and what does it have to do with 6.4x versions?

It was just to show that in 7.x series MT has change from posting many beta version of the software to posting many RC version.

Wed Mar 30, 2022 7:11 pm

What is the problem that you are reporting with this specific 7.2rc6 and what does it have to do with 6.4x versions?
It was just to show that in 7.x series MT has change from posting many beta version of the software to posting many RC version.

Since we have switched the main focus to stability, it makes sense to publish more release candidates - until the latest candidate won't contain critical issues and becomes the actual stable release. Our version numbering system supports up to rc255 - so don't worry, we won't run out of numbers

Publishing betas at this point is not worth it. I doubt that the users will be happy for early access to some bug fixes that, in turn, may introduce even more bugs. We will return to publishing betas once we have new cool features for you to try.

ormandj · Wed Mar 30, 2022 7:46 pm

@raimondsp: Will this fix the port flapping issue (which appears on flash writes) on CRS328 series switches, mentioned in various reports/on these forums, such as mine: SUP-68278 ?

hecatae · Wed Mar 30, 2022 7:58 pm

Audience upgraded successfully.

Will look at chateau later.

hecatae · Wed Mar 30, 2022 7:59 pm

7.1.5 and 7.2rc1-6 cause 100% CPU usage and reboots by OOM on the HAP-Lite

In what configuration?
The default quickset of home ap is running fine for me.

mafiosa · Wed Mar 30, 2022 9:00 pm

Why am I getting this issue on RB5009?
WARNING!!! This router belongs to AS213326 - Kalpak Mukhopdhyay Network Lab. ...
mar/30/2022 10:18:22 system,info,critical cpu not running at default frequency
mar/30/2022 10:20:40 system,info,critical cpu not running at default frequency
mar/30/2022 10:20:40 system,info,critical Firmware upgraded successfully, please r
eboot for changes to take effect!
mar/30/2022 15:53:34 system,info,critical Firmware upgraded successfully, please r
eboot for changes to take effect!
mar/30/2022 15:55:08 system,critical,info ntp change time Mar/30/2022 15:53:53 =>
Mar/30/2022 15:55:08
mar/30/2022 10:26:28 system,info,critical cpu not running at default frequency
mar/30/2022 16:00:19 system,critical,info ntp change time Mar/30/2022 15:59:42 =>

Znevna · Wed Mar 30, 2022 9:01 pm

which one of all that is an issue?

mafiosa · Wed Mar 30, 2022 9:20 pm

which one of all that is an issue?

CPU not running at default frequency.

gittubaba · Wed Mar 30, 2022 9:40 pm

any news on container?

Znevna · Wed Mar 30, 2022 9:45 pm

@mafiosa set the cpu to run at the default frequency then.

Jotne · Wed Mar 30, 2022 9:55 pm

Do you run at not standard frequency for the CPU.
/system/routerboard/settings/print

huntermic · Wed Mar 30, 2022 10:52 pm

I agree partitioning is important when testing! Fortunately it works on my 4011 but I agree it should work on all devices with sufficient storage.
(I would even like to see it added to CHR)

Still they call it:”The ultimate heavy-duty home lab router”

But real ‘safe’ tinkering is not possible as there is no working support for partitioning. This makes me cry a little and not with laughter

deadkat · Wed Mar 30, 2022 11:25 pm

@gittubaba, @tpedko

we really need to stop pinging for containers on *release* threads. if it was released the note would be in OP. until then this is the last news we have: viewtopic.php?t=178342#p900434

the ETA/time line is "its done when its done." I don't want it any sooner! how often do we give MT staff endless grief over not testing things before release and now that a feature is taking longer we tell then they're not fast enough?!?!
until then you can run 7.1rc4 for containers and it should work just fine as long as your routing config isn't too exotic and does not contain BGP. the rest of that thread has some success stories using 7.1rc4 to host containers. I can provide NPKs if needed. I can provide contact info later to send files via telegram

the release thread is not the appropriate place to ask for/about new features. this is the place to talk about the new release and your experiences with it.

curtdept · Wed Mar 30, 2022 11:52 pm

Sierra Modems EM74XX are broken in this release, wont detect at all. Works in 7.1.5 and 7.2rc2

blackhandnz · Thu Mar 31, 2022 12:23 am

RB5009 some issues I picked up after upgrading from v7.2rc5 -> v7.2rc6 (happened on a few of our devices)
- info logging to memory topic disappeared after upgrade -> needed to recreate it
- DHCP Server static leases - some of them disappeared/didn't come across with the upgrade -> needed to recreate them

infabo · Thu Mar 31, 2022 12:50 am

Srsly??

buset1974 · Thu Mar 31, 2022 4:26 am

No BGP progress?? Please give more attention please?

rpingar · Thu Mar 31, 2022 7:09 am

on x86 seems issue with vrrp on vlan!!!!
vrrp slave interface sends arp about ha ip.on the network
#[SUP-78450] created with supout

RyperX · Thu Mar 31, 2022 8:42 am

RB5009 some issues I picked up after upgrading from v7.2rc5 -> v7.2rc6 (happened on a few of our devices)
- info logging to memory topic disappeared after upgrade -> needed to recreate it
- DHCP Server static leases - some of them disappeared/didn't come across with the upgrade -> needed to recreate them

Can confirm this 2 problems, but already with upgrade to 7.2.RC4
Also i have the question about the fixing of partitioning on the RB5009
Its sad because there is not a single ROS Version on the RB5009 that supports partitionjng

Thu Mar 31, 2022 9:10 am

How come SUP-59224 has been closed while nothing as been done on that front?

Can we specify the direction of the Cake queue please so that we start testing and managing the bandwidth properly. I imagine we will find bugs so now should be the time to implement it no?

"Done" is the status of support ticket, not the issue.

Thu Mar 31, 2022 10:07 am

RB5009 some issues I picked up after upgrading from v7.2rc5 -> v7.2rc6 (happened on a few of our devices)
- info logging to memory topic disappeared after upgrade -> needed to recreate it
- DHCP Server static leases - some of them disappeared/didn't come across with the upgrade -> needed to recreate them

Could you provide us with support output file after the incident?

emils · Thu Mar 31, 2022 10:15 am

What's new in 7.2rc7 (2022-Mar-30 15:21):

*) route - allow OSPF and RIP redistributed routes to be matched by routing filters;

Buckeye · Thu Mar 31, 2022 11:08 am

What's new in 7.2rc7 (2022-Mar-30 15:21):

*) route - allow OSPF and RIP redistributed routes to be matched by routing filters;

Is this a new record? two releases in under 5 hours?

I hope my RB760iGS has high endurance flash :-)

7.2rc7.png

Rox169 · Thu Mar 31, 2022 11:20 am

Hi,
I think we are close to stable release.

pe1chl · Thu Mar 31, 2022 11:20 am

Is this a new record? two releases in under 5 hours?

No, there have been fix releases quicker than that...

mrz · Thu Mar 31, 2022 11:47 am

It is hot fix for the previous fix

Ullinator · Thu Mar 31, 2022 11:54 am

Upgrade done on two CRS326-24G-2S+ done (ROS and FW) from 7.2RC5 to 7.2RC7, one of it lost the "bridge" after FW-upgrade and reboot.
Restore of the backup fixed it, but it was a little shocking moment as the PING didn´t came back.....

Jotne · Thu Mar 31, 2022 12:02 pm

No, there have been fix releases quicker than that...

From my long list of release, there has not been a faster public release (4:25) from 6.47 and up (including beta). Have not looked at releases before 6.47. But I may have missed some...

Jotne · Thu Mar 31, 2022 12:03 pm

but it was a little shocking moment as the PING didn´t came back.....

You should not be shocked, since this is just a test version and should not be used in production.

Ullinator · Thu Mar 31, 2022 2:16 pm

but it was a little shocking moment as the PING didn´t came back.....
You should not be shocked, since this is just a test version and should not be used in production.

Don´t worry, it was in a test environment and it was fixed within minutes. It was just to inform you and others (MT?) about a possible problem.

vittore · Thu Mar 31, 2022 2:56 pm

Will the hotspot feature work in ipv6?

Thanks in advance.
VZ

pe1chl · Thu Mar 31, 2022 4:19 pm

Don´t worry, it was in a test environment and it was fixed within minutes. It was just to inform you and others (MT?) about a possible problem.

It looks a bit like the "on reboot (or upgrade), part of the configuration is lost" issue of v7, for which we (outsiders) do not know if it is a generic v7 problem or if it affects just specific parts of the configuration.
I have seen it myself for "ipsec identities" (which was mentioned in rc5 to be fixed), "routing tables" (which was claimed to be fixed but I still saw parts of it), and I have seen others claim it for bridges (what you saw) and other config items.
It may be that when it is fixed in some version, you still encounter it on upgrade to that version because it was already lost in the version before that, before the reboot. Who knows.

Ullinator · Thu Mar 31, 2022 4:37 pm

Don´t worry, it was in a test environment and it was fixed within minutes. It was just to inform you and others (MT?) about a possible problem.
It looks a bit like the "on reboot (or upgrade), part of the configuration is lost" issue of v7, for which we (outsiders) do not know if it is a generic v7 problem or if it affects just specific parts of the configuration.
I have seen it myself for "ipsec identities" (which was mentioned in rc5 to be fixed), "routing tables" (which was claimed to be fixed but I still saw parts of it), and I have seen others claim it for bridges (what you saw) and other config items.
It may be that when it is fixed in some version, you still encounter it on upgrade to that version because it was already lost in the version before that, before the reboot. Who knows.

You´re right, I saw the same behavior in other releases as well (even pre ROS7). For me it looks like parts of the config are not written to flash, but still exist in RAM (running config), so they are visible during runtime.
After a reboot the non-permant config changes are lost. But "why" can only be answered by MT....

Thu Mar 31, 2022 4:51 pm

For completeness, already tried starting from clean configuration on such a device, configure it again and then reboot ?
To rule out there is no impact from prior undetected problems...
Which doesn't mean it doesn't need to be solved. Those devices have to be able to be upgraded on an existing config.

Ullinator · Thu Mar 31, 2022 5:04 pm

For completeness, already tried starting from clean configuration on such a device, configure it again and then reboot ?
To rule out there is no impact from prior undetected problems...
Which doesn't mean it doesn't need to be solved. Those devices have to be able to be upgraded on an existing config.

I´ve tried in the last weeks several ROS versions (6.48.6, 6.49.5, 7.1.5, 7.2RC4 and 5) and every time I´ve reconfigured the devices from scratch with copy&paste the config via terminal
This time the config was made new in ROS7.2RC4 and updated over ROS7.2RC5 -> ROS7.2RC7.
My config is not very complicated, only 2 VLANS with one bridge and VLAN filtering enabled, IPv4 and IPv6, that´s all.
But from time to time I saw in different ROS versions most "bridge" losts after an upgrade / reboot.

pe1chl · Thu Mar 31, 2022 7:50 pm

For me it looks like parts of the config are not written to flash, but still exist in RAM (running config), so they are visible during runtime.
After a reboot the non-permant config changes are lost. But "why" can only be answered by MT....

Either that, or the config file on disk is something like a database with transactions, and they sometimes forget to COMMIT changes that are made.
Indeed, we cannot know why it happens, but apparently it is a difficult problem to solve as it has been there since early v7 releases and still isn't fixed.

Thu Mar 31, 2022 10:50 pm

Will the hotspot feature work in ipv6?

Thanks in advance.
VZ

Well, this post has nothing to do with the topic, but Hotspot is based on NAT and since RouterOS does not support NAT for IPv6, it is not possible at the moment.

Sob · Thu Mar 31, 2022 11:11 pm

@strods: Didn't your colleagues tell you? There's IPv6 NAT in RouterOS v7. :)

blackhandnz · Thu Mar 31, 2022 11:12 pm

RB5009 some issues I picked up after upgrading from v7.2rc5 -> v7.2rc6 (happened on a few of our devices)
- info logging to memory topic disappeared after upgrade -> needed to recreate it
- DHCP Server static leases - some of them disappeared/didn't come across with the upgrade -> needed to recreate them
Could you provide us with support output file after the incident?

Looks like issues are resolved, can't recreate it in v7.2rc7

Znevna · Thu Mar 31, 2022 11:15 pm

Will the hotspot feature work in ipv6?

Thanks in advance.
VZ
Well, this post has nothing to do with the topic, but Hotspot is based on NAT and since RouterOS does not support NAT for IPv6, it is not possible at the moment.

Um...
What's new in 7.1rc1 (2021-Aug-19 13:06):

!) added support for IPv6 NAT (CLI only);[...]

hecatae · Thu Mar 31, 2022 11:29 pm

Installed fine on an rb941.

Thu Mar 31, 2022 11:51 pm

This latest RC adds this bit of noise to the /export output:

/interface ovpn-server server
set auth=sha1,md5

I don't use OpenVPN and never have, so there are no old "echoes" of OpenVPN configuration for it to trigger off. Shouldn't /export suppress that?

brg3466 · Fri Apr 01, 2022 2:53 am

What's new in 7.2rc6 (2022-Mar-30 10:56):
*) lte - improved stability when modem disappears during firmware upgrade;

I tired with rc7, it doesn't solve the problem. My LtAP mini LTE US-Kit still cannot upgrade the modem firmware.
Once you hit the button to upgrade , the LTE interface stopped running.

[brg3466@LtAP] > /interface/lte/firmware-upgrade lte1 upgrade=yes
  status: checking

[brg3466@LtAP] >

mducharme · Fri Apr 01, 2022 7:44 am

I don't use OpenVPN and never have, so there are no old "echoes" of OpenVPN configuration for it to trigger off. Shouldn't /export suppress that?

When they make a change to a default setting in a new version, and you upgrade a device to that new version, the device retains the old default to avoid potentially causing issues. Therefore it begins to show that setting in the config export after upgrading to the version where the default setting has now changed from what it was before, since now it does not match the current default. That is probably what is happening here.

mkx · Fri Apr 01, 2022 8:35 am

I don't use OpenVPN and never have, so there are no old "echoes" of OpenVPN configuration for it to trigger off. Shouldn't /export suppress that?
When they make a change to a default setting in a new version, and you upgrade a device to that new version, the device retains the old default to avoid potentially causing issues. Therefore it begins to show that setting in the config export after upgrading to the version where the default setting has now changed from what it was before, since now it does not match the current default. That is probably what is happening here.

Very probably indeed. I've never used OVPN either. A 6.49.3 device shows auth property set to "sha1,md5" while 7.2rc5 (netinstalled with that version) has it set to "sha1,md5,sha256,sha512".

cheeze · Fri Apr 01, 2022 8:46 am

IPv6 L3HW is currently in development. However, it is not going to be included in v7.2.

Hello good sir. Is it at all possible we can get more information on L3HW development plans?

I see IPv4 is working, and IPv6 is planned in the future to work. Will MPLS also be part of this as well?

Fri Apr 01, 2022 8:58 am

When they make a change to a default setting in a new version...

Very probably indeed. I've never used OVPN either. A 6.49.3 device shows auth property set to "sha1,md5" while 7.2rc5 (netinstalled with that version) has it set to "sha1,md5,sha256,sha512".

Confirmed with a fresh 7.2rc7 CHR, then by setting my real routers to the same auth settings, whereupon the /export noise goes away. Nice diagnosis, you two!

eworm · Fri Apr 01, 2022 9:07 am

Speaking about unwanted configuration in export... A lot of my systems have a default bgp template in configuration.
Is there any way to set parameters to make it disappear? I have not been successful to date.

Fri Apr 01, 2022 9:14 am

Speaking about unwanted configuration in export... A lot of my systems have a default bgp template in configuration.
Is there any way to set parameters to make it disappear? I have not been successful to date.

I just went into WinBox and deleted it. Same with the default OSPF config I wasn't using. Thus why I didn't bother reporting it. :)

eworm · Fri Apr 01, 2022 9:19 am

Ah, indeed... I removed the unwanted OSPF configuration as well... Pretty sure it was not possible with the GBP template back then.
Succeeded now, issue solved. 😜 Thanks a lot!

Fri Apr 01, 2022 10:00 am

This latest RC adds this bit of noise to the /export output:
Code: Select all
/interface ovpn-server server
set auth=sha1,md5
I don't use OpenVPN and never have, so there are no old "echoes" of OpenVPN configuration for it to trigger off. Shouldn't /export suppress that?

Export shows the difference between built-in configuration and your configuration. Since built-in configuration now has aextra auth algorithms, then export shows that you use only these two. If you would reset your configuration now, then you would have four auth algorithms set on your server.

osc86 · Fri Apr 01, 2022 12:32 pm

One of my hap ac2 is rebooting every 3h42m since I upgraded to 7.2rc7. It didn't do that with 7.1.5.
I already checked, it's not because of low memory. I'll write to support.

2022-04-01 11_22_36-172.16.50.91 Logs _ LibreNMS - Brave.png

infabo · Fri Apr 01, 2022 3:16 pm

Export shows the difference between built-in configuration and your configuration. Since built-in configuration now has aextra auth algorithms, then export shows that you use only these two. If you would reset your configuration now, then you would have four auth algorithms set on your server.

@strods

7.1.5 includes this change:

*) lte - made "no" the default value for "use-network-apn" parameter;

I still use `use-network-apn=yes`. But export does not show anything related to `interface/lte/apn`. But from your statement, it should at least show something like `interface lte apn [ find default=yes ] use-network-apn=yes`. But it is not there.

So either buggy or wrong theory.

Fri Apr 01, 2022 3:25 pm

So either buggy or wrong theory.

Confirmed, it's missing from export.

/interface lte apn
set [ find default=yes ] apn=free default-route-distance=5 ip-type=ipv4 name=FRFree
[xyz@MTSXTLte] /interface/lte/apn>

.

2022-04-01_14-23-03.jpg

rextended · Fri Apr 01, 2022 3:29 pm

Try if the setting is exported correctly with one of these commands:

/interface lte apn export show-sensitive

/interface lte apn export verbose

/interface lte apn export terse

Also specify what platform.

Some platform, for error or not, have different defaults...

Fri Apr 01, 2022 3:40 pm

OK, this is strange ...

export show-sensitive: no difference
export verbose: it DOES show but wait ...
export terse: it does not show

And now the catch:
I got 2 APN definitions on that device.
Regular export shows that part for one but not the other.

[xyz@MTSXTLte] /interface/lte/apn> export
# apr/01/2022 14:36:56 by RouterOS 7.2rc7
# software id = WZHT-RPE1
#
# model = RBSXTR
# serial number = <something>
/interface lte apn
set [ find default=yes ] apn=free default-route-distance=5 ip-type=ipv4 name=FRFree
add apn=mworld.be default-route-distance=5 ip-type=ipv4 name=BEOrange use-network-apn=yes
[xyz@MTSXTLte] /interface/lte/apn>

rextended · Fri Apr 01, 2022 3:53 pm

On just resetted to defaults mipsbe:

export code

[admin@RouterOS] /interface/lte> export verbose
# jan/02/1970 00:10:05 by RouterOS 7.2rc7
# software id = S8SE-P15J
#
# model = RB911G-5HPacD
# serial number = 95F00D84B093
/interface lte apn
set [ find default=yes ] add-default-route=yes apn=internet authentication=none \
    default-route-distance=2 ip-type=auto name=default use-network-apn=yes \
    use-peer-dns=yes
/interface lte settings
set firmware-path=firmware mode=auto
[admin@RouterOS] /interface/lte>

>>> use-network-apn=yes <<<

mada3k · Fri Apr 01, 2022 9:04 pm

Is anyone really using RIP anymore?

rextended · Fri Apr 01, 2022 9:10 pm

RIP... Is R.I.P. ...

Fri Apr 01, 2022 10:05 pm

I've just discovered that this release COMPLETELY FAILS in compatibility tests with RFC 1149. Time to sell all my MikroTik gear and go buy Uni-TP stuff instead.

Chaosphere64 · Fri Apr 01, 2022 10:15 pm

I've just discovered that this release COMPLETELY FAILS in compatibility tests with RFC 1149. Time to sell all my MikroTik gear and go buy Uni-TP stuff instead.

... and don't get me started on RFC 2549 compatibility. ;-)

gabacho4 · Fri Apr 01, 2022 10:47 pm

I've just discovered that this release COMPLETELY FAILS in compatibility tests with RFC 1149. Time to sell all my MikroTik gear and go buy Uni-TP stuff instead.
... and don't get me started on RFC 2549 compatibility. ;-)

What, no RFC 6217 either?!

wojo · Sat Apr 02, 2022 12:13 am

Upgrade done on two CRS326-24G-2S+ done (ROS and FW) from 7.2RC5 to 7.2RC7, one of it lost the "bridge" after FW-upgrade and reboot.
Restore of the backup fixed it, but it was a little shocking moment as the PING didn´t came back.....

Lost bridge on one of my CRS328s as well. Very odd.

Paternot · Sat Apr 02, 2022 4:49 am

Guys, be serious. No one cares about RFC 1149, 2549 or 6217. The REAL problem is RFC 7168: this is the one we should worry about!

Sat Apr 02, 2022 4:57 am

The REAL problem is RFC 7168: this is the one we should worry about!

I tested it here and it conforms to the protocol perfectly. It just returns a 418 is all.

Paternot · Sat Apr 02, 2022 1:35 pm

The REAL problem is RFC 7168: this is the one we should worry about!

I tested it here and it conforms to the protocol perfectly. It just returns a 418 is all.

Good to know.

StubArea51 · Sun Apr 03, 2022 3:58 pm

Ran into an issue with MPLS/LDP when using IPv4 and IPv6 together

In 7.2rc7, LDP for the IPv4 afi works by itself and the ipv6 afi does too. But if you use the IPv4 and IPv6 afi together, LDP becomes non-functional and targeted LDP for VPLS stops forking for IPv4 and IPv6.

Submitted this as a bug to MikroTik (SUP-78710)

Details in this thread: viewtopic.php?p=923526#p923526

CTassisF · Sun Apr 03, 2022 6:26 pm

There seems to be a memory leak somewhere in v7.2rc7:

weekly.gif

monthly.gif

hecatae · Sun Apr 03, 2022 8:45 pm

Chateau 5G upgraded, suggests that I'm only connecting to LTE, but still getting 5G NSA speeds.

Mon Apr 04, 2022 9:35 am

So either buggy or wrong theory.
Confirmed, it's missing from export.
Code: Select all
/interface lte apn
set [ find default=yes ] apn=free default-route-distance=5 ip-type=ipv4 name=FRFree
[xyz@MTSXTLte] /interface/lte/apn> 
.
2022-04-01_14-23-03.jpg

*) lte - made "no" the default value for "use-network-apn" parameter;

The default value for the "default" apn profile is "use-network-apn=yes", this remains the same, so that is why you don't see it in the export if it is set to "yes". But for any new APN profiles the default value is "use-network-apn=no", so if you change it to "use-network-apn=yes" it will be shown in the export. I hope this clears it up.

infabo · Mon Apr 04, 2022 10:46 am

Thanks for the explanation. This makes sense now.

osc86 · Mon Apr 04, 2022 1:11 pm

@CTassisF I have the same problem on a hap ac2. The device has not a lot of memory, so it reboots every 3h42m.
I wanted to check the memory usage on a CCR2004-16G-2S+ running rc7, but the Memory Graph isn't even showing up under Tools / Graphing / Resource Graphs...

pe1chl · Mon Apr 04, 2022 1:56 pm

You need to enable the graphing first on the 3rd tab

osc86 · Mon Apr 04, 2022 2:11 pm

I know, it is enabled, I have the cpu and hdd graphs but the memory graph isn't there.

/tool graphing
set page-refresh=300 store-every=5min
/tool graphing resource
add allow-address=0.0.0.0/0 disabled=no store-on-disk=yes

2022-04-04 at 13.15.08.png

Mon Apr 04, 2022 4:17 pm

Sierra Modems EM74XX are broken in this release, wont detect at all. Works in 7.1.5 and 7.2rc2

Please create a support ticket and send us the supout file from your device.

This article explains how to make a supout.rif file:
https://help.mikrotik.com/docs/display/ROS/Supout.rif

Support portal:
https://help.mikrotik.com/servicedesk/servicedesk

rpingar · Mon Apr 04, 2022 5:00 pm

tested on x86 intel NIC E810-C dual 100gbps.
MT reports all the Interface Running also when no thing is connected.

regards

lamaral · Mon Apr 04, 2022 8:09 pm

Is anybody using IPv6 with Wireguard and VRFs successfully?

I have my Wireguard interface slaved to a VRF. IPv4 traffic works just fine, but IPv6 doesn't work at all.
When I try to ping the other side of the WG tunnel from the Mikrotik router, I get a no route to host.
I have tried configuring a /124 as well as a /64 to no avail.

That was happening already on 7.2rc5 and is still happening on 7.2rc7.

Amm0 · Mon Apr 04, 2022 8:40 pm

The REAL problem is RFC 7168: this is the one we should worry about!

I tested it here and it conforms to the protocol perfectly. It just returns a 418 is all.

Well Mikrotik does seem to have RFC 9225, "Software Defects Considered Harmful", well covered in V7.

nithinkumar2000 · Mon Apr 04, 2022 8:47 pm

Please Add IPv6 Delegation Accounitng in PPP Radius Accounting Packet Itself Just Like Cisco and other Routers....

We are unable to Implement IPv6 because of Complaint issues... Please consider Mikrotik Team

huntermic · Mon Apr 04, 2022 9:50 pm

There seems to be a memory leak somewhere in v7.2rc7:

weekly.gif

monthly.gif

I’m also seeing a memory leak.
Fortunately it isn’t a big issue with 1GB ram.

emils · Tue Apr 05, 2022 9:44 am

RouterOS v7.2 has been released

viewtopic.php?t=184778

export code

Who is online