These are used as client antennas. CPU goes to 100% for a long time when pppoe is enabled. But the weird thing, is that some boeards work great. If everyone was slow, i would accept that it’s old slow boards, but with the same config, same packages, same ROS they work different.
If we take a slow board, and use it as a bridge, it works fine..
Is there anyting i can check on the slow board to make it work better?
Some of the boards is “online” (pppoe connected) but ping is not responding. If i’m able to MAC telnet into the RB, it shows the IP adress on pppoe-out but cant ping. (no route to host) after restart they can be “fine”
When the boards are like that MAC ping from AP is very unstable 170ms to 800ms with many timeout
Will it help if I took a supout from an unstable board and sent you?
This exact same problem of 100% CPU with RB133 using PPPoE Client over wireless is evident in every single known version of MT since v3.0 and upwards. EXCEPT v3.19 is fine so this is the version we have had to standardise on.
New boards we use are RB411 and they are fine. But the problem is the 100’s of RB133’s we already have deployed so we cannot upgrade!
PLEASE, mikrotik can you fix this. It is very easy to replicate. Just enable PPPoE client in any wireless RB133 running version higher than 3.0 (but not 3.19) and it hangs with 100% CPU.
We just tested and version 4.16 is still the same too. So you should simply test with this current version and you will be able to replicate.
We have tried and tried and tried to get a supout.rif for MT support but with 100% CPU it’s impossible!
Without PPPoE Client enabled the RB133 works just fine. It’s ONLY the PPPoE client that causes 100% CPU and always hangs.