after the upgrade to 3.22...RB411 as AP with different clients like Edimax, Trendnet.

describe your problem in email for support, also attach supout.rif file.

What did you see in that field with an older version of routeros?
Could it be simply that the clients are reporting incorrect values?

it was working properly until 3.22

I've noticed the same thing on our 411 AP, all clients running MikroTik (133's & 411's).
Signal strengt we're flying from -50 to -1234556767.

I've downgraded fast as heck

I hope this will be fixed soon

I have noticed that this problem only occur when non Mikrotik or ROS systems connect to a to an AP running ROS 3.22.

You do see the problem when two systems running Mikrotik ROS connect.

I've seen on a mikrotik bridge for one second and then the signal is normal again, not only on non mikrotik.

I can confirm that this bug exist also with a AP mikrotik 3.22 [433AH] with a CM9-GP and a windows client connect to it:

this will be fixed in v3.23

Do you know when ROS 3.23 will be released?
Have you got any roadmap about that?
Thanks,
Luca

If will be released when all the fixes are done

3.23 did fix it...but it fix the problem by having a 'blank' field of TX

3.23 did fix it...but it fix the problem by having a 'blank' field of TX

It should be blank. It will only show the TX info if on the other end will be RouterOS, as the other end sends this info.

3.23 did fix it...but it fix the problem by having a 'blank' field of TX

It should be blank. It will only show the TX info if on the other end will be RouterOS, as the other end sends this info.

Or Nanostation


Regards

JB