P.S. /system hardware set multi-cpu=no seems to have stabilised it for now. 1 core is enough for now I think. Until a more stable version is released at least. What did this setting do, remind me, it switches the kernel binary?
P.S.2 I have not written to support about this. I have more important activities at hand.
Is this v5 RC1 stable enough to start trying it on real live routed (no WDS) wirless network with relative simple configs and all rb boards and radio’s?
I am very tempted to start using the new wireless features on my network because I still have the issue of very heavy congested airspectrum with many hidden nodes. Also some of my backhauls could use some boost.
But after some earlier disasters and reading the many bugs around (on more advanced funcions though) I am a bit reluctant to start uploading RC1 to my devices.
Anybody already having experiances with 5RC1 in an all MT (radio’s included) environment?
I still can’t authenticate clients via RADIUS w/ NV2… have to use local ACL.
I have deployed on two production AP’s but they are very small only 3 clients on them.. NV2 seems to be working well, but it’s only the 6hr mark. I had problems with all clients disassociating with the AP at random times and not reassociating. Regular NSTREME works fine.
I have it on about 10 routers. Memory leak on my RB1000 still seems to be there. Booted to ~460mb free ram with 127 SSTP connections, after 6 hours, its down to 440mb. I turned on an idle timeout to try and accelerate the effect.
Model RB750G
3 L2TP client without encryption.
3 openvpn client aes128 encryption.
Version 4.11 works perfectly, load average around 40 percent.
After updating to 5rc1, mikrotik even tunnels can not lift, loading 100 percent and constantly breaks the connection winbox. In the logs at the same time throws out the old and unsolved problem - you can not use the new address, as it already exists. That is, it turns out that when picked up the new tunnel, mikrotik no time to remove the old ip address.
Please, do not make such imprecise posts anymore, i got my coffee cold while jumping to check all the routers. So far all my connection marks for routing marks and packet marks are working fine, i will keep looking, but, looks to me ether it is configuration error, or specific complex situation is necessary to repeat the problem.
5.0rc1 in normal Wlan 802.11n Link with MPLS/VPLS Backbone without Firewall, QoS or so works very good. Same with two R52 on RB/600 in 2km Link. Stabil Link with low Latence by >20Mbit traffic.
mangle and queue works fine on x86, no more problem with queue tree, found some bug with RPS - recomended to disable RPS in this version. Supout send to support.
And RC1 still has bug with torch on intel ethernet.
