User Manager upload limit from client not working

[ridgerunner]

To anyone who may have seen this before.

I have User manager setup authenticating succesfully from and AP. I can disable/enable the client and all works fine. But, when I set the rate-limit in User Manager for a client it seems that the download to the client follows the rate I set it to but upload from the client does not get set, it is still unlimited. Any one lse ever see this issue?

Other than this everything seems to work perfect.

Derek
Ridge Runner

[jordantrx]

Is your CPE or client unit a mikrotik device? They all say that the Client Tx limit will not work unless you use mikrotik CPE units. However some say some CPE’s will work fine with it..



What im reallllllly curious about is DOES THE User-manager BURST WORK! I do not know as of yet and it is really eating me… I dont see how considering you have to reset the connection to the Tx/rx limits to take place… How will it allow burts without diabled/enable the connection to set the rates… Im not sure. -Jordan

[SweetSunday]

Hey Krige.

Great scripting - just what I need.

But can’t get it to work.

Running RouterOS v3.0rc6 + Usermanager.

Located the following errors in your Wiki scripts, but don’t have Wiki access to note them there:

Billing Script: line under 'uncapped services should read

:if ([$poolname] = “usagebased”) do={ :set usagecharge ((($gigstotal/100) * 7) + 7) }

UsageWarning Script: correct line=

:set percentage (($megstotal * 100) / $cap)

Note also that a space preceding the # in any script is noted by the parser as an error which stops painting at that point. So if you cut and paste these scripts you may need to delete any spaces inserted by the process.

HOWEVER in the MonthEnd script the parser won’t accept the script after the line:

:global found

and it paints the ‘found’ in a darker green. Commenting out this line clears the rest of the script, but of course the global value is required and the whole exercise is dependent on it.

I can’t find any reason for this or way around it.

Any ideas?

[SweetSunday]

@SweetSunday

HOWEVER in the MonthEnd script the parser won’t accept the script after the line:

:global found

and it paints the ‘found’ in a darker green. Commenting out this line clears the rest of the script, but of course the global value is required and the whole exercise is dependent on it.

I can’t find any reason for this or way around it.

Any ideas?

OK. It seems that the reason is ‘globals’ have to begin lists of variables - move the “:global found” line to the beginning of the script and it’s fine.

[jordantrx]

@SweetSunday

@SweetSunday

HOWEVER in the MonthEnd script the parser won’t accept the script after the line:

:global found

and it paints the ‘found’ in a darker green. Commenting out this line clears the rest of the script, but of course the global value is required and the whole exercise is dependent on it.

I can’t find any reason for this or way around it.

Any ideas?

OK. It seems that the reason is ‘globals’ have to begin lists of variables - move the “:global found” line to the beginning of the script and it’s fine.

Im not krige but i talk to krige. And i use his script and help others install it. I know the script now from head to toe now.. Thanks to krige helping me out with it and teaching me scripting i figured how it works. Its like its own language you just have to learn how to speak it


However havent talked to him in a bit been busy. Have to get on and see what he is up to…


Let me know if you have any issues with the script maybe i can help .


Hey Ridgerunner, Have you solved your problem? Be nice to know how it works. and if your bursts work. Good day-Jordan