Community discussions

MikroTik App
 
oreggin
Member Candidate
Member Candidate
Posts: 205
Joined: Fri Oct 16, 2009 9:21 pm

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 12:21 pm

I always configure a channel list of 1-6-11 on 2 GHz (that is where my problem occurred).
I think ALL manufacturers, including MikroTik, should put that in their default configuration!
As it is now, the default "auto" will select any channel, it will find the nice quiet channel 3 or 8, and sit there interfering with all others.
Respectable WiFi manufacturers should not do that!
1-6-11 shouln't being default. WiFi channel regulatory is different in each country. It smells for me this info is coming from a cisco era. This 1-6-11 was good in late 1990's and early 2000's where we happily used 802.11b devices with 22MHz channel width using DSSS coding. Yes, in Japan they can use channel #14 for 4th channel.
As 802.11g had becomes more popular, then we had OFDM where you had 20MHz channel width and you can use four 20MHz channel (1-5-9-13) without interfering each other in the most country all over the world. Except in the USA and in a few country. If a microwave oven (operating around 2.45GHz) kills channel #9, you had further 3 channels.
https://en.wikipedia.org/wiki/List_of_WLAN_channels
 
MaxwellsEq
newbie
Posts: 33
Joined: Mon Apr 05, 2021 11:13 pm

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 12:40 pm

Successfully upgraded from 7.18.2 including hAPac2 (configured as cAP).
 
jhbarrantes
Frequent Visitor
Frequent Visitor
Posts: 56
Joined: Wed Aug 21, 2019 2:56 pm

Re: v7.19 [stable] is released!

Wed May 28, 2025 1:08 pm

Guys, "we" just discovered the universal package gate with one of the most embarrassing failure from MikroTik, certificate issues, undocumented traffic-processing and channel.reselect-time, tons of bugs to discover, the fact that WinBox 3 doesn't work with 7.21 that will be released at best by the end of the summer, is probably the lowest priority problem in this topic.

I'm interested in knowing how new features are working and how stable it is this version.
It seems to be implemented in new 7.20beta2 just published. It would be nice to see this feature on PPPoE client too.
 
User avatar
Ca6ko
Long time Member
Long time Member
Posts: 556
Joined: Wed May 04, 2022 10:59 pm
Location: Kharkiv, Ukraine

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 2:05 pm

you can use four 20MHz channel (1-5-9-13)
yes, but only if stanbart B support is disabled, i.e. G/H only N or AX only mode is selected. In AX devices from Mikrotik even for AX mode is still enabled support for mode B, the base transmission is on the standard B, so there is only the only option 1-6-11.
viewtopic.php?t=203221
 
User avatar
msilcher
just joined
Posts: 7
Joined: Mon Mar 09, 2009 9:39 pm
Location: Argentina

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 2:49 pm



Seeing a lot of retransmits that where not there before (v7.18 and prior). I'll test to cold boot when I have a moment but this started as soon as I updated to 7.19...
Is that on a client or on a server?
I have run an IPsec IKEv2 client for about 12 hours now without any interruption, and now I enabled "ipsec, !debug" logging (I presume you have that) and I see the "sending dpd packet" and correct processing, no retransmit seen yet.
Mikrotik is acting as a client in my case, server is a Cisco router. I did a cold boot and VPN is behaving normally now (fingers crossed!). This issue happend at least two times, upgrading from 7.18.1 to 7.19 and then from 7.19 to 7.19.1, it seems like the first boot after upgrade messes things up (??). I'll keep an eye on it.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 3:18 pm

1-6-11 shouln't being default. WiFi channel regulatory is different in each country. It smells for me this info is coming from a cisco era. This 1-6-11 was good in late 1990's and early 2000's where we happily used 802.11b devices with 22MHz channel width using DSSS coding. Yes, in Japan they can use channel #14 for 4th channel.
Maybe the default should be made country dependent, but for sure there should be a default channel list so it won't autoselect any 5MHz channel!
This has nothing to do with "cisco era", it has to to with sensible use of frequencies in the 2GHz band.
 
nmt1900
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Feb 01, 2017 12:36 am

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 4:39 pm

This is very easy to configure manually by adding appropriate entry into channel list like this
name="auto-24" frequency=2412,2437,2462 band=2ghz-ax width=20mhz
and then adding this entry into configuration template
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 5:08 pm

This is very easy to configure manually by adding appropriate entry into channel list like this
name="auto-24" frequency=2412,2437,2462 band=2ghz-ax width=20mhz
and then adding this entry into configuration template
Yes, very easy.
So it should be easy for MikroTik to put it in the default config!
So that people who do not know about such things will have it in their config as well.
 
nmt1900
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Feb 01, 2017 12:36 am

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 5:13 pm

Similar "universal default" for 5 GHz
name="auto-5" frequency=5180,5260,5500,5580 band=5ghz-ax width=20/40/80mhz
There are more channels but these others may be more region-dependent.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 5:18 pm

For 5 GHz the default should be to use only channels that are a multiple of 20 MHz. I always use manual channel assignment on 5 GHz so I am not aware how it works now.
Also, it would be nice when channel numbers could be used instead of frequencies (and converted on entry).
 
User avatar
sirbryan
Long time Member
Long time Member
Posts: 524
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 7:00 pm

24 hours of 7.19.1 on border/core routers and so far, so good. Enabling L3HW offload on the 5 2116's to see how that performs.
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1986
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 7:18 pm

..👍
 
telepro
Frequent Visitor
Frequent Visitor
Posts: 74
Joined: Sun Apr 03, 2011 7:50 pm

Re: v7.19.1 [stable] is released!

Wed May 28, 2025 11:24 pm

Issue found after upgrading to v7.19.1

Running the following command: /ip service set winbox address=1.2.3.4
fails with the following error: failure: this is configured elsewhere

I have tried the same command in different formats:
/ip service set winbox address=1.2.3.4
/ip service set winbox address=1.2.3.0/24
/ip service set winbox address="1.2.3.4"
/ip service set winbox address="1.2.3.0/24"

All of these fail with the same error.
ip_services_address.png
Adding the configuration manually using the GUI is successful.
Exporting the config after adding the configuration using the GUI shows a format that matches the first two of the above formats, but that same line cannot be fed back in as part of an RSC import.

NOTE: This issue did not show up when we upgraded from 7.16.1 -> 7.19.RC3, only when we moved from 7.19.RC3 -> 7.19.1
You do not have the required permissions to view the files attached to this post.
 
UpRunTech
Member Candidate
Member Candidate
Posts: 238
Joined: Fri Jul 27, 2012 12:11 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:35 am

1) Does a simple reboot change the behaviour (upgrade is also a reboot, maybe reboot made things different, not the upgrade)
One thing I have always wondered, does the firmware do critical register settings (like a BIOS does) that don't get set by ROS but can affect things like Wifi and other interfaces or system function or is it strictly for bootup and reset button related functions only?
 
nmt1900
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Feb 01, 2017 12:36 am

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:51 am

For 5 GHz the default should be to use only channels that are a multiple of 20 MHz. I always use manual channel assignment on 5 GHz so I am not aware how it works now.
Also, it would be nice when channel numbers could be used instead of frequencies (and converted on entry).
Exactly - but it seems that it somewhat works properly even "automatically" - if I set frequency to 5240 with 20/40/80 channels then system automatically sets channel to 5180/eeeC (and not 5240/Ceee) i.e. aligns it properly
Last edited by nmt1900 on Thu May 29, 2025 2:41 am, edited 1 time in total.
 
telepro
Frequent Visitor
Frequent Visitor
Posts: 74
Joined: Sun Apr 03, 2011 7:50 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 1:56 am

Running the following command: /ip service set winbox address=1.2.3.4
fails with the following error: failure: this is configured elsewhere
Another note: Same error occurs when trying to set addresses parameter for other IP services. Our script sets address parameter for each of ssh, telnet and winbox, and all three routinely fail with the same error message shown above.
 
nmt1900
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Feb 01, 2017 12:36 am

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 2:43 am

Interesting - if I try to set 'address' parameter for a service from command line then it works without problems. I have not used or tested it with scripts.
 
theprism
newbie
Posts: 29
Joined: Sun Sep 16, 2012 4:11 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 6:07 am

This is very easy to configure manually by adding appropriate entry into channel list like this
name="auto-24" frequency=2412,2437,2462 band=2ghz-ax width=20mhz
and then adding this entry into configuration template
Using only 20MHz? Why not more?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7216
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 8:10 am

Running the following command: /ip service set winbox address=1.2.3.4
fails with the following error: failure: this is configured elsewhere
Another note: Same error occurs when trying to set addresses parameter for other IP services. Our script sets address parameter for each of ssh, telnet and winbox, and all three routinely fail with the same error message shown above.
Look at ip services output and you will understand why. Changing dynamic entries are not allowed.
 
oreggin
Member Candidate
Member Candidate
Posts: 205
Joined: Fri Oct 16, 2009 9:21 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 10:11 am

1-6-11 shouln't being default. WiFi channel regulatory is different in each country. It smells for me this info is coming from a cisco era. This 1-6-11 was good in late 1990's and early 2000's where we happily used 802.11b devices with 22MHz channel width using DSSS coding. Yes, in Japan they can use channel #14 for 4th channel.
Maybe the default should be made country dependent, but for sure there should be a default channel list so it won't autoselect any 5MHz channel!
This has nothing to do with "cisco era", it has to to with sensible use of frequencies in the 2GHz band.
I mentioned "cisco era" because I saw this behavior only in cisco APs. They have 2.4GHz channel list based on country and it is far from the regulatory domains. I don't saw this behavior on Aruba or Ruckus APs. Furthermore we have the most connectivity/compatibility problems with cisco APs. Simply a fact of experience. We operating ~100.000 APS over 5000 locations, cisco, Aruba, Ruckus in roughly equal proportions. We just started to testing MTik wifi, but it seems it is not production-ready yet however it is promising.
So however it seems good first, think twice. Unfortunately there are WLAN NIC vendors, whom doesn't respect standards and as soon as you starting to tuning, part of clients has getting problems. For example we have some site where clients won 100 laptops (cheap models I think) in a competition and none of the laptops can connect to the WPA-Enterprise SSID where I disable 802.11b rates and select preferred channel list 1-5-9-13. cisco is the most tunable WLC but it prints warning while you starting to tuning "some legacy client can't connect to this SSID". The fact is I didn't find a combination of setting where it doesn't print any kind of warnings :-)
In contrast, I didn't find such in-depth configuration options on Aruba Instant, it selects channels from 1 to 13 freely, and it just works.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 11:11 am



Another note: Same error occurs when trying to set addresses parameter for other IP services. Our script sets address parameter for each of ssh, telnet and winbox, and all three routinely fail with the same error message shown above.
Look at ip services output and you will understand why. Changing dynamic entries are not allowed.
Why winbox is dinamic entry?
Are static... or not?

What are dynamic are discover, dhcpclient and btest

@telepro
Update go wrong on same way, db config is locked from something, use netinstall, on my device work as expected...


EDIT: See next posts....

7.18.2 code

[admin@MikroTik] /ip/service> export 
# 2025-05-29 10:09:39 by RouterOS 7.18.2
# software id = 6A66-ZR6Z
#
# model = C52iG-5HaxD2HaxD
# serial number = ****
/ip service
set winbox address=192.168.88.0/24
[admin@MikroTik] /ip/service> /ip service
[admin@MikroTik] /ip/service> set winbox address=192.168.88.0/24
[admin@MikroTik] /ip/service>

7.19.1 code

[admin@MikroTik] /ip/service> export 
# 2025-05-29 10:12:17 by RouterOS 7.19.1
# software id = 6A66-ZR6Z
#
# model = C52iG-5HaxD2HaxD
# serial number = ****
/ip service
set winbox address=192.168.88.0/24
[admin@MikroTik] /ip/service> /ip service
[admin@MikroTik] /ip/service> set winbox address=192.168.88.0/24
[admin@MikroTik] /ip/service>
Last edited by rextended on Thu May 29, 2025 12:21 pm, edited 4 times in total.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7216
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 11:20 am

*) ip-service - show all TCP/UDP connections on the system;
*) ip-service - show all TCP/UDP ports on system, including ports in containers;
*) ip-service - show error message when service enable fails;
Like I said look at the output of the ip service.
 
oreggin
Member Candidate
Member Candidate
Posts: 205
Joined: Fri Oct 16, 2009 9:21 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 11:49 am

I think mrz mentioned this:
[admin@rtr2.076540] > /ip/service/print where name=winbox
Flags: D - DYNAMIC; c - CONNECTION
Columns: NAME, PORT, PROTO, VRF, MAX-SESSIONS, LOCAL, REMOTE
 #    NAME    PORT  PROTO  VRF   MAX-SESSIONS  LOCAL         REMOTE            
15    winbox  8291  tcp    main            20                                  
16 Dc winbox  8291  tcp                        192.168.1.72  192.168.1.64:45846
[admin@rtr2.076540] > 
There is one static and one dynamic entry if someone logged into the device with winbox. When you enter 'set winbox address=192.168.88.0/24', RouterOS try to apply it to the dynamic entry too where the error message comes from.
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 11:51 am

Ok, people need to adjust their scripts now. Instead of giving dynamic entries that are based on static entries a counter suffix/prefix, it is now not unique anymore to use the name like winbox anymore?
Last edited by infabo on Thu May 29, 2025 11:55 am, edited 1 time in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 11:55 am

1) Does a simple reboot change the behaviour (upgrade is also a reboot, maybe reboot made things different, not the upgrade)
One thing I have always wondered, does the firmware do critical register settings (like a BIOS does) that don't get set by ROS but can affect things like Wifi and other interfaces or system function or is it strictly for bootup and reset button related functions only?
The relevant point in that discussion is that a reboot of the router may affect the behavior of the client.
So it is not about reset button or reboot command or powercycle, it is simply about the WiFi interface going away for a while and coming back, and how the client reacts to that.
People complain about changes in WiFi after an upgrade, but the suggestion is to try a reboot without upgrade and see if the same change occurs, e.g. briefly or until the client is rebooted or re-connected.
 
nmt1900
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Feb 01, 2017 12:36 am

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 11:56 am

It looks like command is failing on services which have dynamic entries i.e. active session at the time of issuing the command.
If you issue this command on ssh service while there's no active ssh sessions, it will succeed. When ssh sessions are up it fails with the error message. Same applies to winbox respectively - and all other services which are configurable by static entries.

It looks like root of the problem might be in naming i.e. dynamic entries have same name as static ones.

If you define service by number (numbers="") instead of name command will succeed even with active sessions. Problem here is that number might change as dynamic entries appear. Therefore it is not clear if there's a way to make scripts work unless service naming will be changed.
Last edited by nmt1900 on Thu May 29, 2025 12:02 pm, edited 1 time in total.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 11:59 am

It looks like root of the problem might be in naming i.e. dynamic entries have same name as static ones.
Right, for do test I use MAC telnet, because changing address cut me out from winbox....


Ok, another problem added... The problem is RouterOS... two entry with same name, only the last count...
Must be that commands consider only the static one...

This is a big problem, those who use branding scripts, flashfig, etc., have to modify them.

fix code

[admin@MikroTik] /ip/service> pri
Flags: D - DYNAMIC; X - DISABLED, I - INVALID; c - CONNECTION
Columns: NAME, PORT, PROTO, CERTIFICATE, VRF, MAX-SESSIONS, LOCAL, REMOTE
 #     NAME        PORT  PROTO  CERTIFICATE  VRF   MAX-SESSIONS  LOCAL          REMOTE             
 0     ftp           21  tcp                 main            20                                    
 1     ssh           22  tcp                 main            20                                    
 2     telnet        23  tcp                 main            20                                    
 3 D   dhcpclient    68  udp                                                                       
 4     www           80  tcp                 main            20                                    
 5  X  www-ssl      443  tcp    none         main            20                                    
 6 D   btest       2000  tcp                                                                       
 7 D   discover    5678  udp                                                                       
 8     winbox      8291  tcp                 main            20                                    
 9 D c winbox      8291  tcp                                     192.168.0.186  192.168.0.102:55073
10     api         8728  tcp                 main            20                                    
11     api-ssl     8729  tcp    none         main            20                                    
[admin@MikroTik] /ip/service> set winbox address=192.168.0.0/24
failure: this is configured elsewhere
[admin@MikroTik] /ip/service> set [find where name="winbox" and dynamic=no] address=192.168.0.0/24 
[admin@MikroTik] /ip/service> 
Last edited by rextended on Thu May 29, 2025 12:05 pm, edited 3 times in total.
 
nmt1900
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Feb 01, 2017 12:36 am

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:03 pm

It looks like we found a workaround for scripts...
Last edited by nmt1900 on Thu May 29, 2025 12:07 pm, edited 1 time in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:05 pm

The /ip services servicename set address= command likely should ignore all Dynamic entries automatically.
There is another bug (probably the new functionality just exposes a bug that was already there for a long time):
When you configure a BGP peer with BFD, every time the BFD detects that the link is down and then re-established, a new Dynamic /ip services entry is created with a local port incrementing from 49152 and remote port 3784 as expected.
So with a marginal link I now already have 975 dynamic route_BFD entries in addition to the 2 static ones.
Apparently BFD uses a dynamic local port instead of just using 3784 as both source and destination port, and also forgets to close the socket when the link has failed. How long until the system runs out of sockets?
Last edited by pe1chl on Thu May 29, 2025 12:07 pm, edited 2 times in total.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:06 pm

If you define service by number (numbers="") instead of name command
let's not start writing bull–t.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:08 pm

7.18.2 code

# software id = 6A66-ZR6Z
# serial number = ****
Last edited by BartoszP on 2025-05-29 10:52:34, edited 3 times in total. Reason: serial# obsfucation
Thanks.... but.... ;)
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:14 pm

I suggest: Put port status in separate tab instead of mixing togeter configuration and working status
 
nmt1900
Frequent Visitor
Frequent Visitor
Posts: 89
Joined: Wed Feb 01, 2017 12:36 am

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:25 pm

If you define service by number (numbers="") instead of name command
let's not start writing bull–t.
It just was a first way I tested. It is obvious that "find" gives a sure way to deal with the problem but "numbers" technically works to prove that workaround is possible.
snap 2025-05-29 at 12.22.34.png
You do not have the required permissions to view the files attached to this post.
Last edited by nmt1900 on Thu May 29, 2025 12:26 pm, edited 1 time in total.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 12:26 pm

It looks like we found a workaround for scripts...
We? :lol:

FIX code

/ip/service set [find name="winbox" !dynamic] address=192.168.0.0/24
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 1:48 pm

That would mean the /export should be like that as well! I think it is the wrong track.
Either the "session" entries should be in a different table, or they should have a different name than their "parent".
E.g. the service for winbox would be named "winbox" and a "dynamic" entry would be named "winbox-session".
 
User avatar
Archous
just joined
Posts: 15
Joined: Thu May 12, 2022 7:13 am
Location: USA
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 4:01 pm

FYI folks, there's a major problem in our eyes of this behavior:

*) dhcpv4/v6-client - fixed default route when DHCP client interface is in VRF;

What we are noticing is that the routing-table that the DHCP-learned default gateway is being installed to is not the same as the VRF the interface that the DHCP client is configured for. This is really bad default behavior. We expect that by default the routing-table the gateway is inserted to should be the same VRF the DHCP client interface belongs to. Otherwise we leak a default via DHCP into the "main" table and risk impacting network forwarding that is dependent on a default route.

This was observed happening on a CCR1036 on 7.19.1. Previous config for the DHCP client was:

/ip dhcp-client
add interface=Bridge-Management
 
lurker888
Member
Member
Posts: 427
Joined: Thu Mar 02, 2023 12:33 am

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 4:07 pm

*) dhcpv4/v6-client - fixed default route when DHCP client interface is in VRF;

What we are noticing is that the routing-table that the DHCP-learned default gateway is being installed to is not the same as the VRF the interface that the DHCP client is configured for. This is really bad default behavior. We expect that by default the routing-table the gateway is inserted to should be the same VRF the DHCP client interface belongs to. Otherwise we leak a default via DHCP into the "main" table and risk impacting network forwarding that is dependent on a default route.
Ensure that default-route-tables is set to "default" and not "main". You can see this with "print detail".
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 4:11 pm

Either the "session" entries should be in a different table, or they should have a different name than their "parent".
This. But Mikrotik sometimes choose the backwards incompatible way. Don't know why.
 
User avatar
Archous
just joined
Posts: 15
Joined: Thu May 12, 2022 7:13 am
Location: USA
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 4:18 pm

*) dhcpv4/v6-client - fixed default route when DHCP client interface is in VRF;

What we are noticing is that the routing-table that the DHCP-learned default gateway is being installed to is not the same as the VRF the interface that the DHCP client is configured for. This is really bad default behavior. We expect that by default the routing-table the gateway is inserted to should be the same VRF the DHCP client interface belongs to. Otherwise we leak a default via DHCP into the "main" table and risk impacting network forwarding that is dependent on a default route.
Ensure that default-route-tables is set to "default" and not "main". You can see this with "print detail".
We fixed this by setting it explicitly but our issue is why this isn’t just the default behavior? We should not be defaulting to putting VRF-learned DHCP gateways in to the main table. That’s very bad behavior.
 
lurker888
Member
Member
Posts: 427
Joined: Thu Mar 02, 2023 12:33 am

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 4:30 pm

We fixed this by setting it explicitly but our issue is why this isn’t just the default behavior? We should not be defaulting to putting VRF-learned DHCP gateways in to the main table. That’s very bad behavior.
Actually it is the default. Just touching it or adding it from Winbox or Webfig resets it to main. In fact it cannot actually be set to default from any of them.
 
toxmost
just joined
Posts: 3
Joined: Tue Jun 18, 2019 7:25 pm

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 9:51 pm

wAPG-5HaxD2HaxD after update to 7.19.1 from 7.19 LOST INTERFACE 5Ghz! Completely, hardware-wise, at the driver level!
log: DefConf gen: Unable to find wifi radio data!


who knows what to do with this???
 
User avatar
Archous
just joined
Posts: 15
Joined: Thu May 12, 2022 7:13 am
Location: USA
Contact:

Re: v7.19.1 [stable] is released!

Thu May 29, 2025 10:03 pm

We fixed this by setting it explicitly but our issue is why this isn’t just the default behavior? We should not be defaulting to putting VRF-learned DHCP gateways in to the main table. That’s very bad behavior.
Actually it is the default. Just touching it or adding it from Winbox or Webfig resets it to main. In fact it cannot actually be set to default from any of them.
The config on the box prior to upgrade to 7.19.1 was this:

/ip dhcp-client
add interface=Bridge-Management

As you can see above, there are no settings in the config changing the routing-table of the default-gateway. Since there are no extra parameters specified in the config, you would agree that with this config present in the system the behavior for the routing-table the default gateway is inserted to should be whatever MikroTik interprets as the “default” setting is, right?
 
sparkus
just joined
Posts: 8
Joined: Mon Sep 04, 2023 10:44 pm

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 7:04 am

wAPG-5HaxD2HaxD after update to 7.19.1 from 7.19 LOST INTERFACE 5Ghz! Completely, hardware-wise, at the driver level!
log: DefConf gen: Unable to find wifi radio data!


who knows what to do with this???
Have you already created a supout.rif file and sent it to support?
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 12:23 pm

I'm having issues with igmp-proxy since 7.19, had to revert back to 7.18.2.
Issue was that after a few minutes of tv the tv starts stuttering and about 30 seconds later the tv freezes.
Going back and forth to another channel temporarily worked but the issues than repeated itself.
Tried 7.19 and 7.19.1 but both have the issue.
After rollback to 7.18.2 the issues were gone.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 975
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 1:36 pm

CCR1009-7G-1C-1S+

I had to downgrade to RouterOS v 7.18.2 from 7.19.x

WHY: Because with 7.19 my CPU utilization when using Winbox4 or Winbox3 was consistently/persistently higher ...
under RouterOS v7.18.x my CPU utilization when using Winbox4 or Winbox 3 was barely noticeable

This is a dramatic turn of events from my perspective ...
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 13812
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 1:47 pm

I had to downgrade to RouterOS v 7.18.2 from 7.19.x
I certainly hope you did save supout.rif file while device was running 7.19.1 and you opened trouble ticket with MT support.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 975
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 2:02 pm

I certainly hope you did save supout.rif file while device was running 7.19.1 and you opened trouble ticket with MT support.
I did not open a ticket nor did I produce a supout.rif file ... But maybe I will do that this weekend when I go through the process again and if I can hide all my secrets ...
 
holvoetn
Forum Guru
Forum Guru
Posts: 7486
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 3:01 pm

As you should already know by now: supout is all-in.
You can not hide anything there.

Either you want issue to be investigated and then it is full disclosure or you do not want things to be investigated.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7216
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 3:57 pm

and if I can hide all my secrets ...
If by "secrets" you mean password or keys or other sensitive data, then those are not stored in supout file.
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 4:17 pm

It is documented here: https://help.mikrotik.com/docs/spaces/R ... Supout.rif
This file contains all your router's configuration, logs, and some other details that will help MikroTik Support to solve your issue. The file does not contain sensitive information or router passwords.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 5:37 pm

The scheduler, script and on-event script are present on supout?
If yes: Except what is stored inside script, ANY script, on any position.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 4963
Joined: Sun May 01, 2016 7:12 pm
Location: California
Contact:

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 6:01 pm

The scheduler, script and on-event script are present on supout?
If yes: Except what is stored inside script, ANY script, on any position.
Good point. FWIW, there is the "supout.rif Viewer" section on https://mikrotik.com/client/supout (under Account, after login in free account), which shows the contents of supout.rif that you upload. So any password/keys/"secrets" stored in variables/script are in the supout.rif since it has an "export" (which does not show RouterOS "sensitive" attributes, as noted....but export has no idea what's sensitive in scripts...)
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 6:38 pm

You can write sensitive information in comments as well.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 13147
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 7:35 pm

Another good point... ;)
 
strzinek
just joined
Posts: 13
Joined: Tue Oct 25, 2016 10:29 am

Re: v7.19.1 [stable] is released!

Fri May 30, 2025 11:13 pm

Hello, I'm having problems with chr v7.19.1 after upgrading from v7.18.1 under KVM on Fedora 42. The upgrade finishes successfully, but the VM does not boot and shuts down after the next reboot.
Screenshot From 2025-05-30 22-04-59.png
You do not have the required permissions to view the files attached to this post.
 
rajo
newbie
Posts: 45
Joined: Tue Aug 16, 2011 11:12 pm

Re: v7.19 [stable] is released!

Sat May 31, 2025 5:05 am

Resolved Wireguard issue. It was related to the /interface/wireguard/peers "responder" setting. It seems MT changed which side it needed to be applied to, as I had to swap it from the client peer definitions to the server peer definitions for the VPNs to work again.
Im having Wireguard issues as well but I havent needed to use the "Responder" settings on either side. This is in a S2S configuration where my home RB5009 is on 7.19.1 and work production CCR1009 is on v7.18.2

EDIT: Im getting the below log messages on both routers.
wireguard-DC-S2S: [DC-S2S] Handshake for peer did not complete after 20 attempts, giving up
EDIT2: Just reverted back to v7.18.2 on RB5009 and Wireguard S2S connectivity is restored.
Looks like I've found the culprit for your issue. I discovered it when I created a new Wireguard tunnel for a router and the client wasn't making any connection attempt.

Turns out that (and this is probably a bug introduced in 7.19.x, if it's not intentional), you must now add the "persistent-keepalive" option to at least your client-side peer; otherwise, no connection attempt is made.

I'm going to go ahead an file a bug report, as this appears to be a regression from pre-7.19.x behavior and inclusion of the "persistent-keepalive" option is not being enforced as mandatory.
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 975
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v7.19.1 [stable] is released!

Sat May 31, 2025 12:30 pm

I did not open a ticket nor did I produce a supout.rif file ... But maybe I will do that this weekend when I go through the process again and if I can hide all my secrets ...
I reloaded 7.19.1 and this time the behaviour is back to what I expect ... back to normal --- so I can only surmise that something in previous upgrade did not load properly ...
 
mszru
Member Candidate
Member Candidate
Posts: 100
Joined: Wed Aug 10, 2016 10:42 am

Re: v7.19.1 [stable] is released!

Sat May 31, 2025 3:04 pm

Upgraded hAP ax^3 from 7.18.2 to 7.19.1.
All is well except for incoming L2TP/IPsec connections which all disconnect after 1-2 days of activity. Dynamic IPsec Peer and Identity "l2tp-in-server" also disappear. Re-enabling the L2TP server helps restore the connections. L2TP clients are running different versions of RoS: 6.49.10, 7.14.3, 7.15.1, 7.16.2. So the problem is clearly either with the ax3 config or the new RoS version.
 
merkkg
newbie
Posts: 33
Joined: Thu Jan 19, 2017 11:50 am

Re: v7.19.1 [stable] is released!

Sat May 31, 2025 3:16 pm

I did same thing, updated last night at 3am 12 * CCR2216 from 7.16.1 which I had a few issues with bgp and routes getting stuck. I have high hopes for this version.

I tested on LAB router first and seemed OK.
Been few days so far all working very well, happy with this version so far.

- Cpu looks good, I would say its improved as cpu usage on my side has dropped for one of the routers, others all same
- Ram is good.
- L3HW offloading seems good

Well done Mikrotik!!!
 
User avatar
sirbryan
Long time Member
Long time Member
Posts: 524
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:

Re: v7.19.1 [stable] is released!

Sun Jun 01, 2025 6:24 am

Been running 7.19.1 on five BGP routers for a few days now, and upgraded my CGNAT routers the other day. Played with a few routing filters, changed up some NAT rules, and had L3HW offload both on and off for at least 24 hours. So far so good.
 
User avatar
lemosh
just joined
Posts: 8
Joined: Tue Dec 09, 2014 8:23 am
Contact:

Re: v7.19.1 [stable] is released!

Mon Jun 02, 2025 11:42 pm

Still have this issue: viewtopic.php?t=168735
Any plans to fix it?
 
itimo01
Member
Member
Posts: 302
Joined: Thu Jun 29, 2023 2:55 am
Location: Germany
Contact:

Re: v7.19.1 [stable] is released!

Mon Jun 02, 2025 11:43 pm

Still have this issue: viewtopic.php?t=168735
Any plans to fix it?
Did you open a ticket?
 
faxxe
newbie
Posts: 40
Joined: Wed Dec 12, 2018 1:46 pm

Re: v7.19.1 [stable] is released!

Tue Jun 03, 2025 7:25 am

CCR1009-7G-1C-1S+

I had to downgrade to RouterOS v 7.18.2 from 7.19.x

WHY: Because with 7.19 my CPU utilization when using Winbox4 or Winbox3 was consistently/persistently higher ...
under RouterOS v7.18.x my CPU utilization when using Winbox4 or Winbox 3 was barely noticeable

This is a dramatic turn of events from my perspective ...
i cant confirm that on my CCR1009

-faxxe
You do not have the required permissions to view the files attached to this post.
 
User avatar
lemosh
just joined
Posts: 8
Joined: Tue Dec 09, 2014 8:23 am
Contact:

Re: v7.19.1 [stable] is released!

Tue Jun 03, 2025 8:09 am

Still have this issue: viewtopic.php?t=168735
Any plans to fix it?
Did you open a ticket?
No, I didn't. Please tell me how...
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Tue Jun 03, 2025 8:37 am

It is described over here: https://mikrotik.com/support
 
mike7
just joined
Posts: 15
Joined: Sun Oct 28, 2018 12:20 am

Re: v7.19.1 [stable] is released!

Tue Jun 03, 2025 10:04 am

I'm having issues with igmp-proxy since 7.19, had to revert back to 7.18.2.
Issue was that after a few minutes of tv the tv starts stuttering and about 30 seconds later the tv freezes.
Going back and forth to another channel temporarily worked but the issues than repeated itself.
Tried 7.19 and 7.19.1 but both have the issue.
After rollback to 7.18.2 the issues were gone.
Do you have hw offload enabled?
I've got several issues with igmp-proxy on RB5009, looks like it is regression in v7.19.x.
For workaround take a look viewtopic.php?t=182314#p906140.
 
xrlls
Member Candidate
Member Candidate
Posts: 112
Joined: Sun Jan 13, 2019 4:43 pm
Location: Copenhagen, DK

Re: v7.19.1 [stable] is released!

Tue Jun 03, 2025 5:01 pm

*) iot - improvement to LoRa stability and functionality;
I am seeing an issue on Knot LR8, where LORA is consequently disabled after reboot. This was observed on both 7.19 and 7.19.1.

Anyone else had problems with this?
 
bommi
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Fri Jan 24, 2014 9:13 am
Location: Germany
Contact:

Re: v7.19.1 [stable] is released!

Tue Jun 03, 2025 8:18 pm

Please backport this fix from 7.20 beta to 7.19:
*) bridge - disable/enable HW offload on bonding slave disable/enable (fixes potential MAC learning issue);
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v7.19.1 [stable] is released!

Wed Jun 04, 2025 10:37 am

I'm having issues with igmp-proxy since 7.19, had to revert back to 7.18.2.
Issue was that after a few minutes of tv the tv starts stuttering and about 30 seconds later the tv freezes.
Going back and forth to another channel temporarily worked but the issues than repeated itself.
Tried 7.19 and 7.19.1 but both have the issue.
After rollback to 7.18.2 the issues were gone.
Do you have hw offload enabled?
I've got several issues with igmp-proxy on RB5009, looks like it is regression in v7.19.x.
For workaround take a look viewtopic.php?t=182314#p906140.
I'll try that this weekend, i do have hardware offload enabled.
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Wed Jun 04, 2025 12:01 pm

Ok, people need to adjust their scripts now. Instead of giving dynamic entries that are based on static entries a counter suffix/prefix, it is now not unique anymore to use the name like winbox anymore?
It looks like someone has already encountered this issue: viewtopic.php?t=217197
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Wed Jun 04, 2025 3:47 pm

Anyone know what this (new?) menu does? I can't find it in wifi documentation.
/interface/wifi/radio/settings
There you can set 2 settings:
/interface/wifi/radio/settings/set external-antenna=<yes|no> wifi-band=<2.5GHz|5gHz>
 
User avatar
Paternot
Forum Guru
Forum Guru
Posts: 1110
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v7.19.1 [stable] is released!

Wed Jun 04, 2025 4:39 pm

RB5009 doesn't honor the option "set ethernet speed" for eth1 in RoS 7.19.1

I have a 2,5Gbps device connected on eth1 on an RB5009. For several reasons I need it to run at 1Gbps.
Up to 7.19 it was enough to just remove the 2,5Gbps from the auto negotiation options, and it would set at 1Gbps.
As of 7.19.1 it negotiates 2,5Gbps, no matter what I do. Even disabling auto negotiation, setting it at 1Gbps and power cycling the router. It still connects at 2,5Gbps.

Already opened a ticket with support. No answer yet, but it was just 2 hours ago.
 
User avatar
sirbryan
Long time Member
Long time Member
Posts: 524
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:

Re: v7.19.1 [stable] is released!

Thu Jun 05, 2025 4:17 pm

Reporting back:

9 days uptime with 7.19.1 on most of my 2116's in a 5-way full BGP mesh (three borders and two cores), plus nearly a week on the 2 CGNAT routers. None of the "route stuck" or other BGP issues that came with 7.16+ have appeared thus far. L3HW offload works as well.
 
User avatar
Paternot
Forum Guru
Forum Guru
Posts: 1110
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: v7.19.1 [stable] is released!

Thu Jun 05, 2025 7:19 pm

RB5009 doesn't honor the option "set ethernet speed" for eth1 in RoS 7.19.1

...

Already opened a ticket with support. No answer yet, but it was just 2 hours ago.
And... closed! (SUP-189978)

"...This is an automated message. Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out. To be sure this specific fix is included, read the changelog when the next version comes out. If your issue is not mentioned, it might mean it will be in the next release."

That was fast. Well done, Mikrotik. Well done indeed. :D
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v7.19.1 [stable] is released!

Fri Jun 06, 2025 12:17 pm


Do you have hw offload enabled?
I've got several issues with igmp-proxy on RB5009, looks like it is regression in v7.19.x.
For workaround take a look viewtopic.php?t=182314#p906140.
I'll try that this weekend, i do have hardware offload enabled.
It unfortunately did not help
 
zlook
just joined
Posts: 2
Joined: Mon Mar 04, 2024 4:55 pm

Re: v7.19.1 [stable] is released!

Fri Jun 06, 2025 12:52 pm

Upgraded hAP ax^3 from 7.18.2 to 7.19.1.
All is well except for incoming L2TP/IPsec connections which all disconnect after 1-2 days of activity. Dynamic IPsec Peer and Identity "l2tp-in-server" also disappear. Re-enabling the L2TP server helps restore the connections. L2TP clients are running different versions of RoS: 6.49.10, 7.14.3, 7.15.1, 7.16.2. So the problem is clearly either with the ax3 config or the new RoS version.
same issue. re-enabling helps me too but it is not a solution
 
mszru
Member Candidate
Member Candidate
Posts: 100
Joined: Wed Aug 10, 2016 10:42 am

Re: v7.19.1 [stable] is released!

Fri Jun 06, 2025 1:12 pm

Upgraded hAP ax^3 from 7.18.2 to 7.19.1.
All is well except for incoming L2TP/IPsec connections which all disconnect after 1-2 days of activity. Dynamic IPsec Peer and Identity "l2tp-in-server" also disappear. Re-enabling the L2TP server helps restore the connections. L2TP clients are running different versions of RoS: 6.49.10, 7.14.3, 7.15.1, 7.16.2. So the problem is clearly either with the ax3 config or the new RoS version.
same issue. re-enabling helps me too but it is not a solution
I've created SUP-189868 for this issue 3 days ago and got no response yet...
 
S8T8
Member Candidate
Member Candidate
Posts: 147
Joined: Thu Sep 15, 2022 7:15 pm

Re: v7.19.1 [stable] is released!

Sat Jun 07, 2025 1:22 pm

Any info about new option traffic-processing?* Is working AX only?

*Other than TrevinLC1997 comment:
There is documentation about this on the old wireless interface. From what I read the data channel is basically just a tunnel that the cap will utilize when sending traffic to the CAPsMAN server. (Traffic is encapsulated in a special CAPsMAN header that can only be removed by a CAPsMAN router). Once data arrives it is then decapsulated and processed at the CAPsMAN router.
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Sat Jun 07, 2025 1:46 pm

There is a dedicated topic: viewtopic.php?t=217047
 
pfml
just joined
Posts: 3
Joined: Wed Mar 06, 2024 10:02 pm

Re: v7.19.1 [stable] is released!

Sun Jun 08, 2025 10:22 am

*) iot - improvement to LoRa stability and functionality;
I am seeing an issue on Knot LR8, where LORA is consequently disabled after reboot. This was observed on both 7.19 and 7.19.1.

Anyone else had problems with this?
Same issue here, LORA enabled for a few minutes after reboot, disabled after. No clue in log...
 
xt22
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Jul 14, 2015 1:16 pm

Re: v7.19.1 [stable] is released!

Sun Jun 08, 2025 7:27 pm

mustang1986 - I will try to not miss my point here... There are thousands and thousands of MikroTik routers. There are no such bugs that affect "everyone". Otherwise, we would be out of business. And clearly such thing as a memory leak simply by using WiFi would have been noticed, fixed, etc. So I strongly recommend in such case or any other case (not WiFi problems, but any major issue that does not allow for you to work properly) do not assume that it will somehow get fixed since it might be considered as "common issue". The right thing here - open a support ticket and let us get into it. Believe it or not, more often than not such "everything is broken and not working for anyone" are issues that affect like 3 people, and we really can not guess why, we can just dig and debug through your supout files. For example, maybe you have some random temperature sensor in your home which works badly and triggers such issue and that is it - we can not guess. And maybe there are several different issues causing similar problems. Any of them must be debugged individually and solved individually. There is no other way around it - forum will not re-write code. :)
this problem is known for at least 5 months.. I was one of the many that had the ticket opened (as you suggest here), since I have a few hundred cAPs and a many Chateaus and when the device is bricked, you can't do anything with it - edit, change, reset, reboot, nothing (at least the reboot may have been fixed in 7.19:
*) system - fixed "/system reboot" when the system disk is completely full;
Anyway - Mikrotik's response was like - go **** yourself, we don't care, we create crap, you bought crap, it is your problem and your config anyway, so what you bought six chateau 5Gs for $500 each, how dare you expect WPA3 in a $500 router in 2025 (huge sarcasm) - you wasted your $3000, throw it in thrash and buy our great AX devices..


For anyone dealing with this problem: if your device has been bricked and shows the no space message, you are s****** and have to netinstall or reset it - that means jump on a plane and fly to all of your router's locations (up to 7.18.2); you might be able to reboot the device in 7.19+, I haven't tried that.
Netinstall frees maximum free space, resetting a little less, but still sufficient (around 300-400 kB).
When the router is in a working state, downgrade to 7.16.2 (you need to download the qcom-ac 7.16.2 package too), it will have around 500kB of free space and work fine, although Mikrotik told you the problem is in your config. Don't upgrade.


viewtopic.php?p=1140301
 
xt22
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Jul 14, 2015 1:16 pm

Re: v7.19 [stable] is released!

Sun Jun 08, 2025 8:09 pm

Yeah but the wifi-qcom-ac driver is not "for hAP ac2". It just happens to have the right chip to work, but not enough storage.
Mikrotik says it is
Image

And this is not just about hAP ac2, Mikrotik will sell tou today Chateau 5G for $485 - then you go here https://help.mikrotik.com/docs/spaces/R ... 8/Wireless, where Mikrotik says Needed packages for WPA3 - routeros + wifi-qcom-ac. So you download it, wait for a few days and boom - device bricked. So you write to Mikrotik, and... oh, how dare you want WPA3 in a $500 router in 2025? Thrash it and buy our AX version.

Shame on Mikrotik for that, really
 
faux
just joined
Posts: 6
Joined: Tue Jul 28, 2020 12:55 pm

Re: v7.19 [stable] is released!

Mon Jun 09, 2025 11:02 am

Shame on Mikrotik for that, really

When did you buy those Chateau's? They're discontinued and shouldn't be available to purchase, newer Chateau versions have like 128mb. If you bought them recently I'd have a word with your partner cause they should have sent the updated version with bigger Flash.

Even the products with 16mb now come with 32mb at least, like we bought a CRS312 last year which says 16mb on the spec sheet but it came with 32mb.

At a minimum MikroTik should note in the docs that 16mb versions can't use the chunky wifi package, especially how it says 'all versions of D53G' which includes your particular 5G with 16mb
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19 [stable] is released!

Mon Jun 09, 2025 11:31 am

At a minimum MikroTik should note in the docs that 16mb versions can't use the chunky wifi package, especially how it says 'all versions of D53G' which includes your particular 5G with 16mb
Of course the wifi-qcom-ac package was especially released because the chunky wifi-qcom package (that also supports ax) was too big to fit on the 16MB flash models, and MikroTik believed they could pull this off.
In the beginning it worked, but of course the new releases of RouterOS v7.x become larger all the time and by now there is not enough space on 16MB models to use wifi-qcom-ac. That means it might as well be dropped now.
(or it has to be split in some more smaller packages that support only specific models)
 
xt22
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Jul 14, 2015 1:16 pm

Re: v7.19 [stable] is released!

Mon Jun 09, 2025 1:37 pm

When did you buy those Chateau's? They're discontinued and shouldn't be available to purchase, newer Chateau versions have like 128mb. If you bought them recently I'd have a word with your partner cause they should have sent the updated version with bigger Flash.

Even the products with 16mb now come with 32mb at least, like we bought a CRS312 last year which says 16mb on the spec sheet but it came with 32mb.

At a minimum MikroTik should note in the docs that 16mb versions can't use the chunky wifi package, especially how it says 'all versions of D53G' which includes your particular 5G with 16mb
this year, few months ago, the new upgraded 5G R16 version. Mikrotik is still offering it on their website https://mikrotik.com/product/chateau5gr16 or 2025 product catalog https://mt.lv/product_catalog

So I wasted like $3000 for six of these craps (I have two 5G AXes too, but their availability is pretty bad here). I didn't really care about the space, it never was a problem in Mikrotiks and I have hundreds of tiks from hAPs/cAPs to CCR1036s. So you look at the specs, then at their wireless page, saying you need to install the qcom-ac package for WPA3.. than won't be a problem, Mikrotik is long time respected wireless vendor, so it must work, we are not talking about some chinese junlink crap for $20... oh wait, all these chinese home craps support not only wpa3, but wifi 6 and even wifi7. You want a working WPA3 on a new $485 Mikrotik router in 2025? Sorry.. big disappointment
 
User avatar
loloski
Long time Member
Long time Member
Posts: 531
Joined: Mon Mar 15, 2021 9:10 pm
Location: Philippines
Contact:

Re: v7.19.1 [stable] is released!

Mon Jun 09, 2025 4:54 pm

@MT

Does BGP Signal VPLS with Route Reflector still in the pipeline or it won't fix on v7? thanks a ton
 
zlook
just joined
Posts: 2
Joined: Mon Mar 04, 2024 4:55 pm

Re: v7.19.1 [stable] is released!

Mon Jun 09, 2025 6:55 pm

I've created SUP-189868 for this issue 3 days ago and got no response yet...
i wonder if you have any ups on your ticket.
 
holvoetn
Forum Guru
Forum Guru
Posts: 7486
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.19.1 [stable] is released!

Mon Jun 09, 2025 7:03 pm

Guys, it has been a holiday weekend...
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 4963
Joined: Sun May 01, 2016 7:12 pm
Location: California
Contact:

Re: v7.19.1 [stable] is released!

Mon Jun 09, 2025 7:27 pm

Commands with sensitive fields are entirely remove from history. This has been annoying since there is no need for the entire command to be removed when it's only the sensitive attribute that should be removed (or shown as ="" like export) from history. I often "try" a command via CLI to cut-and-paste in a config file, or repeat a command with one/more changes in CLI. And it's not just /user that it happens with... as a lot of VPN config also has sensitive attributes, that cannot be repeated via UP arrow/etc.
 
mszru
Member Candidate
Member Candidate
Posts: 100
Joined: Wed Aug 10, 2016 10:42 am

Re: v7.19.1 [stable] is released!

Mon Jun 09, 2025 7:36 pm

I've created SUP-189868 for this issue 3 days ago and got no response yet...
i wonder if you have any ups on your ticket.
Yes, I was suggested to install the latest version of RouterOS and see whether that fixes the issue. I'll try to do that a bit later.
 
merkkg
newbie
Posts: 33
Joined: Thu Jan 19, 2017 11:50 am

Re: v7.19.1 [stable] is released!

Mon Jun 09, 2025 7:55 pm



i wonder if you have any ups on your ticket.
Yes, I was suggested to install the latest version of RouterOS and see whether that fixes the issue. I'll try to do that a bit later.
Its not very clever to recommend nightly build for people to test with... unless u post it with alot of disclaimers... and even then I wouldn't do it... the nightly build is 1000% ONLY FOR LAB and people who are experienced and willing to brick their devices. We finally have access to this please don't get it taken away....
 
oreggin
Member Candidate
Member Candidate
Posts: 205
Joined: Fri Oct 16, 2009 9:21 pm

Re: v7.19.1 [stable] is released!

Mon Jun 09, 2025 11:13 pm

Its not very clever to recommend nightly build for people to test with... unless u post it with alot of disclaimers... and even then I wouldn't do it... the nightly build is 1000% ONLY FOR LAB and people who are experienced and willing to brick their devices. We finally have access to this please don't get it taken away....
You are right, sometimes the nightly builds hide landmines. I tested few times suggested nightly builds and once my mipsbe devices softbricked, they can't boot into RouterOS, but fortunately I reinstalled them with netinstall, so be careful, and prepare yourself for the worst.
 
loxmaty
just joined
Posts: 10
Joined: Wed Mar 29, 2023 8:49 am

Re: v7.19.1 [stable] is released!

Tue Jun 10, 2025 9:42 am

With 7.19.1 , one or twice a day all conected L2TP clients (about 30) suddenly disapper !
No reconnection, I have manually to disable and re-enable L2TP server and clients immediately reconnect.
I have the same issue on hap AX3. I have 3 site to site tunnels with 3 other microtik devices, 2-3 time per day they disconnects and not reconnect until i re-enable L2TP server, or reboot router. I will Trying 7.20beta2 maybe it fix this issue.
 
zlook
just joined
Posts: 2
Joined: Mon Mar 04, 2024 4:55 pm

Re: v7.19.1 [stable] is released!

Tue Jun 10, 2025 11:27 am

I have the same issue on hap AX3. I have 3 site to site tunnels with 3 other microtik devices, 2-3 time per day they disconnects and not reconnect until i re-enable L2TP server, or reboot router. I will Trying 7.20beta2 maybe it fix this issue.
plz give some respond after your try
 
gotsprings
Forum Guru
Forum Guru
Posts: 2343
Joined: Mon May 14, 2012 9:30 pm

Re: v7.19.1 [stable] is released!

Tue Jun 10, 2025 11:42 pm

I have a CRS320-8P-8B-4S+ that is reporting all sort of problems with the new firmware.


2025-06-10 15:40:16 health,warning PSU1 removed from the slot
2025-06-10 15:40:16 health,warning PSU2 removed from the slot
2025-06-10 15:40:18 poe-out,info ether15 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether8 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether11 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether13 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether14 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether16-Scraper detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether7 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether3-Din_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether5-Pato_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether10 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether2-BAR_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether1-Office_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether12 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether6 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether4-PVT_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether9 detected poe-out status: wait_for_load
2025-06-10 15:40:23 poe-out,warning ether10 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether2-BAR_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether1-Office_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether12 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether6 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether4-PVT_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether9 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether15 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether8 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether7 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether11 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether16-Scraper detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether3-Din_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether14 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether13 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether5-Pato_AP detected poe-out status: controller_error
2025-06-10 15:40:26 health,info PSU1 returned to state OK
2025-06-10 15:40:26 health,info PSU2 returned to state OK
2025-06-10 15:40:26 poe-out,warning ether8 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether7 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether11 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether16-Scraper detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether3-Din_AP detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether14 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether13 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether5-Pato_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether10 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether2-BAR_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether1-Office_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether12 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether6 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether4-PVT_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether9 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether15 detected poe-out status: controller_init
2025-06-10 15:40:31 health,warning PSU1 removed from the slot
2025-06-10 15:40:31 health,warning PSU2 removed from the slot

NO ONE is touching the power supplies.

Can I downgrade once I get over 7.19? I am running 7.19.1.

I have another site that is 7.14.3 and is flawless.

EDIT: This maybe a hardware issue.

I was able to downgrade to the routerOS I have at another site. Problem persists.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 11:57 am

Well, these upgrades do flash the firmware of the internal PoE controllers (as indicated in the change notes) and downgrading RouterOS will not re-flash them to an older version... so problems like this cannot be fixed by downgrading.
You have to hope that a newer version will be released that again fixes the PoE firmware.
I have learned the hard way to never upgrade the production routers when the new version release notes contains "*) poe-out - upgraded firmware for 802.3at PSE controlled boards". I wait for others to report problems and/or until I find time to upgrade a test device that I can afford to lose.
 
User avatar
grusu
Member Candidate
Member Candidate
Posts: 168
Joined: Tue Aug 13, 2013 7:35 am
Location: Bucharest, Romania

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 12:21 pm

@gotsprings
Did you upgrade only RouterOS or also Routerboard (firmware)?
 
User avatar
infabo
Forum Guru
Forum Guru
Posts: 1746
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 1:26 pm

7.19.2 when? Too much teaser
 
gotsprings
Forum Guru
Forum Guru
Posts: 2343
Joined: Mon May 14, 2012 9:30 pm

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 2:30 pm

@gotsprings
Did you upgrade only RouterOS or also Routerboard (firmware)?
I upgraded from 7.16.2 to 7.19.1. RouterOS and Firmware.
Downgraded RouterOS to 7.14.3. Can't downgrade firmware below shipping firmware.
 
gotsprings
Forum Guru
Forum Guru
Posts: 2343
Joined: Mon May 14, 2012 9:30 pm

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 3:26 pm

Well, these upgrades do flash the firmware of the internal PoE controllers (as indicated in the change notes) and downgrading RouterOS will not re-flash them to an older version... so problems like this cannot be fixed by downgrading.
You have to hope that a newer version will be released that again fixes the PoE firmware.
I have learned the hard way to never upgrade the production routers when the new version release notes contains "*) poe-out - upgraded firmware for 802.3at PSE controlled boards". I wait for others to report problems and/or until I find time to upgrade a test device that I can afford to lose.
The Beta shows an update for the POE board. Guess I have to try that. Hopefully it doesn't brick.
 
gotsprings
Forum Guru
Forum Guru
Posts: 2343
Joined: Mon May 14, 2012 9:30 pm

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 3:49 pm

Well that looks different...
 2025-06-11 12:29:36 dhcp,info dhcp-client on bridge got IP address 192.168.101.2
 2025-06-11 12:29:43 poe-out,info ether5-Pato_AP LLDP 12.9W request approved
 2025-06-11 12:29:43 poe-out,info ether1-Office_AP LLDP 22.9W request approved
 2025-06-11 12:29:46 poe-out,info ether2-BAR_AP LLDP 21.0W request approved
 2025-06-11 12:30:46 system,critical,info cloud change time Jun/11/2025 12:29:55 => Jun/11/2025 12:30:46
 2025-06-11 08:30:49 poe-out,info ether3-Din_AP LLDP 21.0W request approved
 2025-06-11 08:31:43 poe-out,info ether4-PVT_AP LLDP 12.9W request approved

 
pe1chl
Forum Guru
Forum Guru
Posts: 10669
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 4:27 pm

Ok you are lucky... last time this happened to me there was no beta that fixed it but fortunately I received an alpha version.
This PoE firmware seems to be hit-and-miss (and not well tested before release)...
Maybe there should be a config option to "not upgrade PoE firmware" so you can elect to keep it once it works for you...
 
User avatar
zBear
just joined
Posts: 24
Joined: Sat Mar 07, 2015 6:17 pm

Re: v7.19 [stable] is released!

Wed Jun 11, 2025 4:47 pm

you must now add the "persistent-keepalive" option to at least your client-side peer; otherwise, no connection attempt is made

can’t confirm, it might be client-specific
my android tablet connects to the 5009 without any keepalive data
 
gotsprings
Forum Guru
Forum Guru
Posts: 2343
Joined: Mon May 14, 2012 9:30 pm

Re: v7.19.1 [stable] is released!

Wed Jun 11, 2025 10:26 pm

pe1chl

If it weren't for bad luck... I would have none.
2025-06-11 14:45:28 poe-out,warning ether8 detected poe-out status: controller_error
 2025-06-11 14:45:28 poe-out,warning ether2-BAR_AP detected poe-out status: controller_error
 2025-06-11 14:45:28 poe-out,warning ether1-Office_AP detected poe-out status: controller_error
 2025-06-11 14:45:28 poe-out,warning ether12 detected poe-out status: controller_error
 2025-06-11 14:45:28 poe-out,warning ether16-Scraper detected poe-out status: controller_error
 2025-06-11 14:45:28 poe-out,warning ether15 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether10 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether9 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether4-PVT_AP detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether3-Din_AP detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether11 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether14 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether7 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether13 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether6 detected poe-out status: controller_error
 2025-06-11 14:45:29 poe-out,warning ether5-Pato_AP detected poe-out status: controller_error
 2025-06-11 14:45:29 interface,info ether16-Scraper link down
 2025-06-11 14:45:29 interface,info ether17-GuestNet link down
 2025-06-11 14:45:32 health,warning PSU1 removed from the slot
 2025-06-11 14:45:32 poe-out,warning ether4-PVT_AP detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether3-Din_AP detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether11 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether14 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether7 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether13 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether6 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether5-Pato_AP detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether8 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether2-BAR_AP detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether1-Office_AP detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether12 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether16-Scraper detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether15 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether10 detected poe-out status: controller_init
 2025-06-11 14:45:32 poe-out,warning ether9 detected poe-out status: controller_init
 2025-06-11 14:45:33 interface,info ether1-Office_AP link down
 2025-06-11 14:45:33 interface,info ether2-BAR_AP link down
 2025-06-11 14:45:33 interface,info ether3-Din_AP link down
 2025-06-11 14:45:33 interface,info ether4-PVT_AP link down
 2025-06-11 14:45:33 interface,info ether5-Pato_AP link down
 2025-06-11 14:45:37 poe-out,info ether10 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether9 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether4-PVT_AP detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether3-Din_AP detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether11 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether14 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether7 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether13 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether6 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether5-Pato_AP detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether8 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether2-BAR_AP detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether1-Office_AP detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether12 detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether16-Scraper detected poe-out status: wait_for_load
 2025-06-11 14:45:37 poe-out,info ether15 detected poe-out status: wait_for_load
 2025-06-11 14:45:39 poe-out,info ether1-Office_AP detected poe-out status: on
 2025-06-11 14:45:39 poe-out,info ether2-BAR_AP detected poe-out status: on
 2025-06-11 14:45:39 poe-out,info ether3-Din_AP detected poe-out status: on
 2025-06-11 14:45:40 poe-out,info ether4-PVT_AP detected poe-out status: on
 2025-06-11 14:45:41 poe-out,info ether5-Pato_AP detected poe-out status: on
 2025-06-11 14:45:42 poe-out,info ether16-Scraper detected poe-out status: on
 2025-06-11 14:45:42 health,info PSU1 returned to state OK
 2025-06-11 14:45:46 interface,info ether17-GuestNet link up (speed 1G, full duplex)
 2025-06-11 14:45:47 interface,info ether16-Scraper link up (speed 1G, full duplex)
 2025-06-11 14:45:51 interface,info ether2-BAR_AP link up (speed 1G, full duplex)
 2025-06-11 14:45:51 interface,info ether3-Din_AP link up (speed 1G, full duplex)
 
 
ToTheCLI
Frequent Visitor
Frequent Visitor
Posts: 98
Joined: Mon Jan 04, 2016 3:54 am

Re: v7.19.1 [stable] is released!

Thu Jun 12, 2025 12:14 am

Adlist on 7.19.1 RB5009 Not Blocking anything...
 
MichalPospichal
newbie
Posts: 44
Joined: Sun Feb 04, 2018 11:27 pm
Location: Czech Republic

Re: v7.19.1 [stable] is released!

Thu Jun 12, 2025 1:00 am

Adlist on 7.19.1 RB5009 Not Blocking anything...
Working just fine for me...
 
loxmaty
just joined
Posts: 10
Joined: Wed Mar 29, 2023 8:49 am

Re: v7.19.1 [stable] is released!

Thu Jun 12, 2025 11:06 am

I have the same issue on hap AX3. I have 3 site to site tunnels with 3 other microtik devices, 2-3 time per day they disconnects and not reconnect until i re-enable L2TP server, or reboot router. I will Trying 7.20beta2 maybe it fix this issue.
plz give some respond after your try
7.20beta2 not resolve the issue. Downgrade to 7.18.2 and all work fine.
 
zlook
just joined
Posts: 2
Joined: Mon Mar 04, 2024 4:55 pm

Re: v7.19.1 [stable] is released!

Thu Jun 12, 2025 3:09 pm

7.20beta2 not resolve the issue. Downgrade to 7.18.2 and all work fine.
oh... i hate to downgrade))) will wait for the fix couple days more)))