And more importantly in this particular case RouterOS doesn't use systemd as far I can tell, but does use xz (where malware is actually distributed) for npk archives so maybe you should check if what you are using is affected version...Our SSH is not based on 3rd party implementation.
Strictly speaking the attack is against systemd which is dependent on liblzma, regular upstream openssh (unpatched for systemd notify functionality) is not affected...I'm guessing ROSSH it's based on Dropbear
Have you bothered to actually read the page from the link provided?What causes this message regarding a backup-routerboot upgrade? Screenshot from 2024-02-29 09-48-58.png
edit: Device is RB960PGS (hEX PoE) r2.
I presume wAP ac is an arm version not mipsbe...cAP XL ac and wAP ac upgraded (from 7.13.4) without problems (besides my RB4011).
Only had to suppress Wireguard logging.
Or one could go back to RouterOS v6 long-term, it is still supported and will be for some time as far as I can tell...Indeed, they are in denial. We can only hope that 7.12.1 will be labeled long-term and maintained with security fixes...
I presume this is incompatible with regular "wireless" package station-bridge and all APs not able to run wifiwave2 right?*) wifiwave2 - added station-bridge interface mode;
Maybe check if ip/dns has allow-remote-requests=yes...Yes, stays at 5-6% total CPU load with one core always at 100%.
If you have more than one IP addresses you can set the one that is used by default for this particular route...can you explain what is pref-src=0.0.0.0 what thats for?
Unless you read the posts above to find out where the dude package is and upgrade it you wont be able to run it...So, If we want to have the updated stable version, we can't run Dude.
Dude will work for 3 months and after will be dead for 3 months .
I wonder what for?Then probably will wait for 6.49.7 ...
And by all PPP you mean L2TP, SSTP, OVPN, PPTP, PPPoE or actually PPP that runs over serial connection?6.48.6 broke all PPP only for me? Сyclic PPP reconnections (client or server - it doesn't matter).
downgrade to 6.48.5 - fixed problem
Does not prevent users to connect and so far everything works well for us ...*) wireless - added option to disable PMKID for WPA2;
According to Qualcomm you need new chipsets for WPA3 so it seems that old gear wont be able to support it ...And what about working on WPA3?
Interesting ... What versions of WinBox/Windows are you using?Maybe on your routerboard. On rb922 (and others) don´t workIt surely works in winbox.
It wouldn't be Cloud Hosted Router than and Mikrotik already has "barenone" hardware that is running RouterOS ...Make CHR to run on barebone switches. http://www.edge-core.com/productsInfo.p ... 143&id=264
I'm creating VLAN20 on Bridge1 - there's still ok.
But when I add VLAN20 to Bridge2, RB is unavailable on these two ports.
Are you sure about that? mAP lite should have 64MB RAM and 16MB flash ... and no you cant use partitions ...Can I make partition(s) on my mAP Lite? It has only 32MB disk space.I really think Mikrotik should discuss using partitions in addition to backups.
Unfortunately Mikrotik is just ignoring this issue and sticks with 16 years old RSTP standard ...Would having MSTP option solve this issue?
What do you mean ...wireless snooper result don't indented in winbox 3.x
It is unusable on smaller screens ... You could use WebFig for now ...Could you please add a scroll bar to some windows?
You can start from here :Please specify what info would you like to get from LLDP?