A new bug in 3.22?!

InoX · March 22, 2009, 1:57pm

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

enk · March 22, 2009, 7:53pm

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

RK1 · March 23, 2009, 6:27am

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

InoX · March 23, 2009, 6:42am

it was working properly until 3.22

Kenneth · March 23, 2009, 7:28am

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

InoX · March 23, 2009, 10:15pm

I hope this will be fixed soon

skillful · March 23, 2009, 10:43pm

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.

InoX · March 24, 2009, 12:53am

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

taglio · March 28, 2009, 10:28pm

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:

uldis · March 29, 2009, 4:49pm

this will be fixed in v3.23

lucapilosu · April 7, 2009, 9:01am

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

normis · April 7, 2009, 9:07am

If will be released when all the fixes are done

moengoet · April 28, 2009, 3:55pm

3.23 did fix it…but it fix the problem by having a ‘blank’ field of TX

uldis · April 29, 2009, 8:48am

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.

boardman · May 13, 2009, 6:41pm

Or Nanostation

Regards

JB