v3.0 big BUG BUG BUG

RouterOS General
1

I found a big BUG in v 3 and in all RC, too.

The problem is forzing the client AP like ovislink 5450, 5460, 1120 and some WIFI PCI cards older than 1 year.
With newest are no problem!

If the signal is very strong stese client aps are runing good. If the signal is poor than the client Ap is froze and i must restart it. After that the client is runing no longer than 2 minutes and it frozes agan.

On 2.9.x there was no problem !


…sorry for my English :slight_smile:…

2

According to every other post you’ve made you have always had problems… makes me wonder about operator error.

3

Yes I have problems becouse I bought 18 RB600 and I changed my RB 532. There are a lot of costumers and I need to find a solve.

The firmware version on the Ovislink AP is V 3.2.1.3.8e

EDIT:

You can check this problef if you are very slowly disconecting the antena conector than the client ap goes down :frowning:
this problem is only on ROS v 3.x or RC

4

What exactly is freezing? Your non-MT clients or your MT AP?

5

Only my non -MT clients … like older ovislinks

6

test with Prism 2.5 is everything OK, no ovislink frozing :slight_smile: …


On RB600 I use R52 … it is the same

7

Maybe the problem is driver if it is changed in v3.

8

I have the same problem with AP RB333/RB133 + minipci atheros (senao NMP-8602 plus/ubiquiti xr2/compex WLM54AG 6A23) and clients WL-1302 chipset realtek 8181 ( http://www.ccandc.com.tw/product/11b-wl-1302.htm )
I need a solution urgent

9

I was having problems too. Started running my SR2’s at 23 dbm and decreased hardware retries to 7 and haven’t had any more problems.

10

well come on, if your client is freezing, then the problem is obviously in the client. one could easily turn this issue into a security risk and go crashing the client devices in the city.

11

What function is the HW retries? What is the best settings for R52 ?

12

I am sorry but the is no problem with client ! If clients are runing with no problem with diferent APs just the problem is with mikrotik V 3.x and RC

13

if you can cause a device to crash so easily, it’s a problem with the device obviously. anyone with this knowledge could build a wireless device that would destroy your network if it consists of these devices. this is a security risk and should be taken to the manufacturers support. we can’t debug why the device crashed because we haven’t made it.

14

I tryed to set the hardware retries to 7 and it is more more better ! But it nos no the same line in 2.9.x

15
  1. Same problem here, ovislink clients are frozing in all ROS 3,0. WHen using 2,9,50 i see no problem.
  2. Additionaly - on my X86 router when upgraded to ROS 3,0 my atheros clients - p2p got randomly freezed, after random time the client seems to be connected but is not receiving data. Enable/disable card to reconnect. Same with 2,9,xx client , also with 3,0 client. Repeating randomly from 2 to 12 hours.
    Downgrade back to 2,9,50 cleared the problem.
    Seems we have long way to get it work properly.

Jan

16

Try to change the output power to 13 dB … It is better

17

What kind of Atheros clients?

I am using a diverse mix of Tranzeo CPE-200 CPE-80 CPE-90 and CPQ’s in addition to Engenius CB3’s for client devices with no issues.

18

I change my RB532 for RB 333 and all my clients with realtek 8181 (Jath, micronet, edimax) ramdomsly crash and start to connect, disconnect, and i have the same problem with long links (30km) with realtek 8186, this only in v3 with v2.9.50 no problems, any solutions?

19

I dont think this is a solution - i rolled back to 2.9

20

hello everybody,

I have exactly the same problem (client connect disconnect every second) with RB333 with up-to-date firmware and ros 3.0rc14 or 3.0
I use client Linksys WRT54GL with DDwrtV23.sp2 for firmware.
I use WPA / TKIP mode for security and R52 wireless cards.
But with RB532, no problem with V2.9.3x–>v2.9.50 and same config for client (only migrate AP RB532 ->RB333 in our networks).

I need a solution !

Eric