Expired internal RADIUS pool guest accounts not purging automatically?

[VeniVidiVidic]

Something has being bugging me for a while. We have hit the issue where on a RFS4000 we have hit the 500 user limit on the internal RADIUS database. IO've cleared expired accounts down and all works again. However I found it strange I couldn't find an option to automatically delete expired accounts.

Upon reading the How To guide for Captive portals I find multiple references to an automatic purge:

When a guest / visitor account is created on the system it will be mapped to a user pool and group so that the user can be authenticated using the integrated RADIUS server. The accounts will be automatically purged 24 hours upon expiration.

Upon expiration the guest / visitor user accounts are automatically purged from the system

This is clearly not the case on 5.3.1.0-009R as expired accounts remain until being manually deleted. I don't know yet but wonder if the same will happen on clustered RFS7000's running 5.2.13.0-015R?

Thanks

[noobie]

Hi there,

Seriously? 5.3.1 and comparing it to 5.2.13 when 5.4.4 is out?

I am really sorry, but I just cant understand why people are staying on old firmwares even if they face some issues. The update process is so easy in 5.x, when you have multiple partitions/RFDM upgrades via WAN links..

Accounts are being automatically purged on the latest firmware. Look at the date when this guide you are reading has been written, its from December 2012 (i.e. ~ 5.4.1 release).

btw, release notes (the ones you are getting with the download link) contain a lot of info regarding recent bug fixes for each release, so its worth to have a look at them.

[VeniVidiVidic]

Well the guide is called WiNG 5.x How To Guide with no reference to what versions it is applicable to so you would assume all 5.x - a fair assumption surely!

As for the release notes I've read them all for higher versions than 5.3 and none seem to mention fixes at all just new features so not sure how I'm meant to track things like you say?

Also the deployment is very high profile and of reasonable scale (Up to 2000 AP's eventually, ~500 so far) robust change control as it's now partially live (1 WLAN is) mean I'm not going to upgrade firmware without absolutely confirmed reasons.

Thanks

[mwted]

To your point about the release notes, one thing I observed about the WiNG5 firmwares is that the release notes on the support site don't show bug fixes but if you actually download the firmware and read the release notes in that zip file they do shed some light on bug fixes.  I can say from experience the 5.4.x series is far more stable then the 5.3.x and before although I do sympathize on trying to push new firmwares across larger enterprises without reasonable cause.