v7.10, 7.10.1 and more [stable] are released!

can you read? read above in this topic…

Works fine here!

I got problems with DACs (Direct Attach cables) since the update.
They don’t work anymore, both with auto-negociation and manual transfer rate setting.
One is Ipolex and other is HiFiber. Both don’t work anymore. Very annoying …

can confirm above is fixed. if you still have issues do these steps:

remove private (on RouterOS) and public (on the remote host) keys;
downgrade RouterOS to version 7.8;
Export RouterOS SSH keys;
import new private key in RouterOS, the public key in the remote host;
check if ssh-exec to the remote host works;
upgrade RouterOS to version 7.10 and check if ssh-exec to the remote host works.

Upgraded all my devices from ROS6. My first time with ROS7. For now all is working flawlessly.

LtAP, PowerBox Pro, BaseBox 2 and BaseBox 5.

Regards.

I’m using a CCR-2004-16G-2S+ and a wAP AC (RBwAPG-5HacD2HnD).

I upgraded the CCR-2004-16G-2S+ to 7.10. I tried upgrading the wAP AC through CAPsMAN and noticed the Upgrade button is not working. I click Upgrade and nothing happens.I waited about 10 minutes. It usually confirms if I want to upgrade, then the wAP comes back up in 30s or so. I tried Winbox and the web interface.

EDIT: I think I’m blocking the wAP’s access to WAN. I uploaded RouterOS 7.10 to the CCR-2004 and now the upgrade button works.

Sir, there is a funcionality for this already.

Thank you for the new features, I can confirm that prefix count seems to work fine, but what does “bgp - show address family in advertisements” mean?

/routing/bgp/advertisements/print is still empty, all session have “.keep-sent-attributes=yes”

[admin@CCR1] > /routing/bgp/advertisements/print detail

[admin@CCR1] > /routing/bgp/advertisements/print count-only
0

In docs it says: “Features not yet supported […] enabling BFD for ip route gateways”

Is that a forever thing, or “coming soon”?

Yes, this has been an issue for me on CCR2004-16G-2S+ since a few releases ago (I think it started with 7.8). Luckily that device has a backup GbE into the network. But for a few releases the DAC has not been working for me anymore. I see RX traffic on it but nothing on the TX side.

we got issues with RR, is not exchanging the routes on the main table between iBGP

Ovpn client log show more info.
I have similar ovpn setup and I am back to 7.9.2 working fine again.

IPsec not working after update. Freezes on first packet phase1 and can not auth on Strongswan server.
I spent an hour trying to find the cause and couldn’t. I had to go back to the previous ROS.
The same config on 7.9.2 is working.

thanks, updated my small zoo:

  • RB4011 (SFP+: MT S+AO)
  • hex Gr2 (Switch mode)
  • CRS309 (SFP+: DACs from Aristo, Cisco, MT S+AO, fs.com 80m 10G-T)
  • CRS326-24G-2S (SFP+: DACs from Aristo), running wifi capsman
  • LHGG
  • wAP-ac 2ndGen (CAP)
  • 2x hap-ac^3 (WW2 APs) no ww2-capsman, container (Adguard-home)
  • CHR

…VLANs, Wireguard, SFP+ Modules all good.
Container on hap-ac^3 needed re-install to start properly.

That is a very general statement you are stating. There are plenty of reports but not all can be attributed to ROS, many can be misconfiguration. When you say fix will come at 7.11, it is understood that some particular fix will come at 7.11.
In the change log of 7.10 there are some wifi wave2 fixes like

*) wifiwave2 - fixed key handshake timeout with re-associating clients;

and many others

Since this Update my OpenVPN Windows Clients are unable to connect. Mikrotik to Mikrotik with OpenVPN is working. Anyone else see this Problem?

please check SUP-119380
RouterOS 7.10 dns dynamic-servers random lost on all type device, RB5009/RB4011/RB450Gx4/CHR
Downgrading to version 7.9.2 everything is fine, but when upgrading to 7.10, random loss occurs.
1.jpg
2.jpg
this link
http://forum.mikrotik.com/t/7-10-stable-dns-crash/167135/1
maybe the same issue

My OpenVPN Server stopped working after this update!
I get this error on client side:

"Client exception in transport_recv: process_server_push_error: Problem accepting server-pushed peer-id: parse/range issue"

After downgrading to 7.9 the problem solved!

Same problem here…

I don’t use MikroTik OVPN but when I read the above error message I would guess maybe the peer-id used by MikroTik is the “/system identity” that you have set, and you may be able to solve that issue by using a more plain identity than you have now? (try only letters and numbers, for example).