Change History (8)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
It works fine on my end. Do you have a binary which includes anticascading? To which parameters do you refer? Please also note, that parameters are only saved if they are different from the default values (unless you specify httpsavefullcfg but that's not recommended).
comment:3 by , 13 years ago
comment:4 by , 13 years ago
There are some value restrictions. I will update the wiki with these restrictions.
comment:5 by , 13 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
parameters have their value restrictions and those count when you save. please stick to the wiki for the limits. if you want to discuss these values, please use forum!
comment:6 by , 13 years ago
Resolution: | worksforme |
---|---|
Severity: | high → medium |
Status: | closed → reopened |
Still doesn't work as expected, currently in #5775
value restrictions you mention about cannot be found completely in the wiki (does denysamples have any limit?)
comment:7 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
value restrictions you mention about cannot be found completely in the wiki (does denysamples have any limit?)
please use forum , for ask or correct any wiki problem or any incompatible webif with wiki.
tnx
comment:8 by , 13 years ago
"samples" means the amount of samples to take into account for anticascading calculations. It is limited to 10 because this memory is statically allocated with 10 elements. These samples are one by one checked for if the time exceeds the defined anticascading limit of the account. The result is an amount of exceeds between 0 and 10. Now, "denysamples" comes into play: If the amount of exceeds is higher or equal to "denysamples", the account is seen as exceeding its limit and thus blocked. "denysamples" always has to be one smaller than "samples" - I'm not sure if it couldn't be also equal to it but it is currently defined this way. The wiki is not completely correct but it is for sure no bug in OSCam itself.
Also note: If you set these values manually in your config file, the parameter restrictions are also applied when loading the config into OSCam.
Many Thank's for Developers!