I am using an SR71-A on RB433AH and having a strange problem.

If I look at the wireless registration, it shows that the clients 'last activity' time is 1000's of seconds ago. These clients are not actually registered anymore and new clients can't register until I reboot the unit.

I had this problem a couple times on RouterOS version 4.10 but not too frequently. When I upgraded the devices to 5.0rc7, it started happening all the time.

Anyone else using this hardware? I suspect it is a problem with the SR71-A's compatibility with RouterOS.

Are you running in 802.11 mode, Nstreme or NV2?

I have ran into this bug while running 4.16 with the Nstreme package in 802.11. Clients show registered in the registration table but won't pass any traffic, disable and re-enable the AP interface brings them back for a random amount of time. As far as I know there is no fix for it at this time other than going back to 4.16 with the normal wireless package. MT knows about the problem and is hopefully working on it.

I am using an SR71-A on RB433AH and having a strange problem.

If I look at the wireless registration, it shows that the clients 'last activity' time is 1000's of seconds ago. These clients are not actually registered anymore and new clients can't register until I reboot the unit.

I had this problem a couple times on RouterOS version 4.10 but not too frequently. When I upgraded the devices to 5.0rc7, it started happening all the time.

Anyone else using this hardware? I suspect it is a problem with the SR71-A's compatibility with RouterOS.

I am using 'unspecified' as the Wireless Protocol (2ghz, g only as band). No Nstreme.

Now I just had the same problem with an SR2 card on 5.0RC7

maybe you can downgrade to RouterOS v4.16 and compare the behavior between regular wireless package and wireless-nv2 package. If it is only happening with wireless-nv2 package, then please contact to support@mikrotik.com and also if you could give us remote access for debugging that also would be great.

BTW, how often does this problem happens - what is the fastest way to reproduce it?

I am a little reluctant to try it again since this is a production network. The weird thing is I have other access points with the same config that don't have the problem nearly as often as the others. I believe it has something to do with the amount of interference as this is a very high noise environment.

I have not been using NV2 though (at least not on purpose). This is a hotspot network (clients are various, not mikrotik). The wireless protocol I had was 'unspecified'. Do non-mikrotik clients work with NV2?

Thanks,
Philip

I am a little reluctant to try it again since this is a production network. The weird thing is I have other access points with the same config that don't have the problem nearly as often as the others. I believe it has something to do with the amount of interference as this is a very high noise environment.

I have not been using NV2 though (at least not on purpose). This is a hotspot network (clients are various, not mikrotik). The wireless protocol I had was 'unspecified'. Do non-mikrotik clients work with NV2?

Thanks,
Philip

From my experience when you set it to non specified runs in whatever mode you were running before the upgrade. So if you were running 802.11 that is what it is going to run. Again the NV2 wireless package flat won't work in 2.4Ghz 802.11 mode from what I have seen. I have tested it across at least 5 AP/Sectors from lightly loaded to moderate and every single one of them locked up at some point in time. Unless you are running straight NV2 the new wireless package doesn't work.

There may be some out there who are using it successfully but I haven't been able to get it to work.

Also no non mikrotik clients won't run with NV2. I would recommend rolling back to 4.16 with the standard wireless package.

OK, much appreciated Chadd. I am rolling my APs back!