7.23.2 [stable] is released!

[pe1chl]

There also is another issue that has been introduced in 7.22 and I believe is related to the disabling of EEE (energy efficient ethernet), but I am not sure.

We have a location where a Draytek router is connected to an ethernet port of an RB5009 and it fails to work correctly after some time. The Draytek router (which is operating as a downstream router for a tenant) obtains a lease, but the systems behind it have no traffic. Downgrade to 7.21.5 fixes it. SUP-219648.

[agilis1]

Using 7.21.5, I actually enabled IPv6 so that I am compliant without actively using it. Meaning, I accept the IPv6 address from my ISP, Xfinity, and stumbled through this guide here: https://tangentsoft.com/mikrotik/wiki?name=IPv6%20with%20Xfinity

I now support and distribute IPv6 addresses on my flat home network with maintaining my local DNS server which is a pi-hole. I think it’s called SLAAC.

I’m going to stay on 7.21.5 until someone from Mikrotik guarantees the next long-term release addressed the issue you raised awareness of.

Thank you for your contributions

[smn]

I had the same issue when 7.23 was released and have stayed on 7.22.1 since.

As for the interface=all, I am using ipv6 on my home network. Should I use interface=bridge instead?

[CGGXANNX]

Yes, if you don't have dynamic interfaces (for example SSTP or PPPoE clients using your router as server) then you can disable the * entry with the all interface, and make a copy of it for each of your LAN interfaces, in this case your bridge interface. If you also use VLAN interfaces then add more copies for those too.

[smn]

I set in my 7.22.1 configuration the IPv6 nd to advertise dna on bridge only, then upgraded to 7.23.2 and everything came back to life just fine. DHCP client got my cable modem's IP address without any issue.

[livione]

Please advice if it's safe to upgrade to 7.23.2 or better upgrade to 7.21.5 long-term?

My device (normal home use connecting to ISP via PPPOE + CONTAINERS and IPv4/IPv6):
router] > /system/routerboard/print
routerboard: yes
model: RB5009UG+S+
serial-number: HJY0****
firmware-type: 70x0
factory-firmware: 7.18.2
current-firmware: 7.19.6
upgrade-firmware: 7.19.6

Thanks

[infabo]

I can't garuantee that it's safe, but I would upgrade to latest longterm first.

[jbl42]

For production, we use long-term, unless we require a specific feature or fix only available in stable.
At home, I prefer stable what allows me to play with new features. And with 2 teenagers in the house, the network performance monitoring is tight, good for testing

[agilis1]

You should read my post about what the latest stable release did and how much grief it caused me. For me, long term only from now on.

7.23.2 [stable] is released!

Edit: Issue resolved by downgrading to v7.21.5 Following RouterOS firmware update to v7.23.1, I am experiencing severe interface instability and total internet connection drops on ether1 connected to my cable modem (NETGEAR CM3000). Initial Issue (2.5G Mode): With auto-negotiation advertising 2.5G (2500M full) on ether1, the physical link continuously drops, flappings, or fails to pass WAN traffic cleanly. Flow control toggling does not resolve the behavior. Fallback Testing (1G Mode): E…

7.23.2 [stable] is released!

Thank you so very much!! I had this exact issue. I spent several hours with Gemini, Xfinity, NETGEAR, even bought a replacement NETGEAR CM3000 trying to troubleshoot this issue. I believed that my ISP was to blame and it just happened to occur during the reboot of the router. Silly I know but I never had any issues with the RB5009 and upgrading the RouterOS since its initial set up. I’m very relieved I found your post. I appreciate you taking the time to actually post the issue and the steps …

[agilis1]

@CGGXANNX

This was Mikrotik’s Support suggestion on the issue I was dealing with. Mind you, I emailed them on July 22nd so I can no longer attempt this since I am on 7.21.5.

I don’t think Mikrotik is aware of the issue, these forums, or they don’t care

[CGGXANNX]

MikroTik is aware, this is strods' answer above in this thread:

7.23.2 [stable] is released!

Okay, thank you for all the information now. I am pretty sure the issue would be already resolved through support channel, but anyway - the problem is clear now. We will try to figure out if we can somehow differentiate "old config where option advertisement was not expected without additional configuration" from "new configuration where options must be advertised even without prefix configuration" and advertise options only if that is manually forced by "prefix" (including "none") configuration…

[agilis1]

Thank you.

Strod seems annoyed that the issue was being discussed in the forums and not the proper support channel BUT at the top of the announcement when you vote, it says to post (to the thread) about the device, configuration, and unexpected symptoms.

[bratislav]

What is safe anyways? You cannot rely solely on a router to make your network safe, if you open access and use low quality passwords nothing will keep you safe...
In this particular case RouterOS versions have been specifically released to address a known vulnerability that can compromise routers that use PPP so you should upgrade to make your network a bit safer, and your safest bet is to go for a long-term version 7.21.5 since there is usually the least chance of something else being broken...

And strictly speaking what you are showing is routerboard firmware version (or BIOS in PC terms), RouterOS version can be shown with:

system/package/print where name=routeros
Columns: NAME, VERSION, BUILD-TIME, SIZE
# NAME VERSION BUILD-TIME SIZE
0 routeros 7.21.5 2026-07-03 10:23:40 11.7MiB

although these have been synchronised for some time now...

[BartoszP]

@bratislav

What a famous scene recalled in the gif. Bravo.

[EdPa]

Version 7.23.3 has been released:

7.23.3 [stable] is released!

Before an upgrade: Remember to make backup/export files before an upgrade and save them on another storage device; Make sure the device will not lose power during upgrade process; Device has enough free storage space for all RouterOS packages to be downloaded. What's new in 7.23.3 (2026-Jul-30 14:17): certificate - added "ISRG Root X2", "Root YE" and "Root YR" to SMIPS built-in root certificate authorities store; certificate - added "Root YE" and "Root YR" to built-in root certificate autho…

[pe1chl]

@pe1chl

There also is another issue that has been introduced in 7.22 and I believe is related to the disabling of EEE (energy efficient ethernet), but I am not sure.

I now believe it has nothing to do with EEE but it is related to "ip firewall mangle route route-dst=xx.xx.xx.xx".

This seems to fail under more recent versions, either immediately or after some uptime.

I have replaced it with a "mark routing" and a second routing table with only a default route, and it looks like that works fine.

[fischerdouglas]

@pe1chl

I now believe it has nothing to do with EEE but it is related to "ip firewall mangle route route-dst=xx.xx.xx.xx".

This seems to fail under more recent versions, either immediately or after some uptime.

I have replaced it with a "mark routing" and a second routing table with only a default route, and it looks like that works fine.

Mangle is câncer!
It depends on Connection Tracking Table to work.
How do you do what you use to do with mangle, if ConnTrack is disabled?

[pe1chl]

Route marking does not depend on connection tracking. Each packet (in the pre-routing chain) is independently inspected.