You're right, I also don't understand...
Actually, in 7.16.2 you can already do it... Just tried it...
After a 24h of testing on a CRS418-8P-8G-2S+5axQ2axQ-RM, I see great improovement on my wifi stability that a had with 7.23.x, will try to update my wAP AC APs that are manage by CAPMAN running wifi-qcom-ac.
Did you miss to add the wifi package ?
Hi,
no all is OK and up. I dont see any fault. Strange.
P.S.: This is from an hAP AX Lite
Mmmh. Wasn't there a change from 7.13 onwards where you needed a different WIFI Package depending on your Chipset.
And yup. There is an old "auto-before-reset.backup" file .
Does anybody know if the file can be removed without issues ?
Really?
Still no news on DOH connection multiplexing for http/2 upstream?
i had an issue with wireless CAPs after upgrading to 7.23.3 where Apple clients couldn't maintain a connection and i had to downgrade to 7.23.2. upgrading to 7.24 seems to have fixed this problem.
however, less good news: 7.24 has completely broken OSPF v3 on CRS312. after boot, CPU is pegged at 100%, no routes are added to the routing table, and "/routing/ospf export" returns "timeout".
downgrading to 7.23.2 fixed the problem.
OSPF neighbours are other MikroTik (7.23.3, 7.24) and BIRD 3.3.1.
Wireguard as reponder seems to be completely broken (after toggling peer off/on?). I have a setup that use one routerOs as reponder. another routerOs after NAT as initiater. the routerOs used as host do recieve the packet, but it never trying to auth the client or send anything back, and there is absolutely no wireguard debug entry generated (don't even have a entry that say failed auth or something)
After switch the wireguard host to lts(7.21.5), the same config works flawlessly
I can concur on this one. Moved my RB4011 and cAP AX and wAP AX to 7.24 and based on the logs I see less disconnects and roaming looks like it works very well as well.
I am not sure you should be running OSPF on a switch with a slow single core CPU...
how large do you think my OSPF network is? the 600MHz CPU in the CRS312 can handle it fine without breaking a sweat, as it did it in every previous RouterOS release. i'm not running a global ISP here.
Hello
Can confirm this!
After Disable ond Enable a Wireguard Responder - Peer, this Peer stops working.
Workaround is to Uncheck Responder and Check it agein!
Problem is general problem, also with no responder Peers.
After Reenable the Wirguard - Peer stops working.
It seems, the Peer somehow stays Disabled even if not shown as Disabled.
That depends...
If LSDB has more then 30-50 routes and it is noisy... Yep. I Agree! You shouldn't.
On a clean area?
Small number of devices and routes, no noisy flapping...
Nothing will do the job better then OSPF.
Some NOS use cgroups to protect computational resources to avoid Media Streaming tool consume resources that are important to CPU.
It does not matter whether peer is responder or not. Just changing the setting (and changing back) re-initializes the peer.
Fix is already in the nightly 7.25 build - so it will appear in later 7.24.x builds
