I have a of RB433 box that have issue with client/wds associations from time to time. Client can see AP SSID, but it will not connect into it or clients still associated can not pass any traffic over that AP connection (even ARP table has correct MAC and IP bindings, but it will make no difference).
Only way to get it going again is to reboot that RB433.
No supout.rif can be made because that (Winbox?) functionality is broken - it just will sit there (usually with CPU load at 100%), but no file is being generated.
Sorry to inform you, but CHANGELOG of 5.0beta3 does not mention as addressing nor fixing those type of issues.
Still, I’ve pumped that device to 5.0beta3 and have yet to see that error again.
Yeah, I’ve upgraded to that as well and just waiting it to bomb out on me. Still my question about ROS CHANGELOG updates remain - why to have it if it does not list the issues addressed by given ROS release? Or is it “maybe we have fixed it” type of mentality what is in work here? In that case you are more likely just introduced a lot more bugs into the mix than randomly fixed one.
Just had that issue with 5.0beta4 as well.
This time I had the client stop pinging very soon after a system reboot and instead of rebooting again, I just disabled-enabled the radio and it came to life. I have supout.rif files if needed.
Second of my RB433AH with 5.0beta3 just had the same issue and IP traffic did resume just after disabling-enabling the wlan interface. I recall as trying the same “trick” with 5.0beta2 with no success. So, something has changed between these releases, but the end result is still the same. I have supout.rif files if needed.
. so you know what to do. But i suggest disable wireless and create supout.rif.