Lower case the username in an authetnication packet, but leave it as is in an accounting packet?
Surely, you are using ACCOUNTING data to send PODs, not AUTHENTICATION data?
The company I work today have a control software that uses Accounting data to send the POD to mikrotik. They don't want to change the actual software to something that allow to drop user from Authentication data. Actually, yes, we have an "online customers" list in this software that gather information from ACK login at Radius on MK and register it, that I can drop anyone (Diconnect) without any issues at all. The problem is that we have about 4K customers using mixed case mode in their login forms (either Hotspot/PPPoE). The automatic proccess of blocking an access or releasing an access is not working properly. Well, almost now is only not working for PPP users, as I told before they are obligated to use UPPERCASE in hotspot page. But this doesn't occur in PPPoE.
At least you got my point, but why MK don't allow a function to drop a user, ignoring the way it was typed in "login" at PPP session but just comparing upper+lower case?
EDIT 1 = The accounting infos are located in an remote DB. The control software uses raddb + mysql to do the control, keeping users and passwords inside this DB.