Cant set new quota based on IP range

[kiwiandy]

I have been setting bandwidth quotas based on IP addresses, and have succesfully set one range, and a number of discreet IP addresses, however when I try to add additional IP address ranges I get an error message " Duplicate Ip/Time Range-- only one quota per IP at any given time is allowed..." However I have not set any other quotas for these IP addresses...

I cant attach a screenshot error message board attachment quota has been reached... not my day today!!

[kiwiandy]

OK will post the image another way....

[Alexbrewer]

I don’t know if this is the same as your problem, but I saw something similar. I narrowed it down to the format of the range I was using.

Short answer is dont use spaces between the ip addresses. It will work with the first range, but you may get errors after the first. For example:

192.168.1.10-192.168.1.19

Don’t put spaces around the dash!!!!

Also, I found a trick to help me. I assign ranges to each of my kids. If you use ranges, you don’t know what range is for who in the quota page. I do each quota in two parts, with the first ip in the range separate, so the quota page shows the name of the device on the summary screen.

Hope this helps.

[kiwiandy]

Thanks Alex, will give ita try!

[d3fz]

I don’t know if this is the same as your problem, but I saw something similar. I narrowed it down to the format of the range I was using.

Short answer is dont use spaces between the ip addresses. It will work with the first range, but you may get errors after the first. For example:

192.168.1.10-192.168.1.19

Don’t put spaces around the dash!!!!

Mind elaborating a little further with this bug?

192.168.1.10-192.168.1.19 - Valid
192.168.1.10 -192.168.1.19 - Unvalid?

Thanks.

[Lantis]

Bug is a strong word lol.
String validation is an incredibly fragile thing. It is very hard to predict exactly what a user will enter.
The function is working as expected. It probably just needs to be better documented what the expected input is.

[d3fz]

Bug is a strong word lol.

You're right. I guess it's more to an "undesired system behavior due to unknowingly wrong input data format" than an actual bug . If it wiped all current quotas due to that little detail, then maybe yes, it's a bug.

String validation is an incredibly fragile thing. It is very hard to predict exactly what a user will enter.
The function is working as expected. It probably just needs to be better documented what the expected input is.

Agreed. Regex to the rescue maybe?

[Alexbrewer]

I don’t know if this is the same as your problem, but I saw something similar. I narrowed it down to the format of the range I was using.

Short answer is dont use spaces between the ip addresses. It will work with the first range, but you may get errors after the first. For example:

192.168.1.10-192.168.1.19

Don’t put spaces around the dash!!!!

Mind elaborating a little further with this bug?

192.168.1.10-192.168.1.19 - Valid
192.168.1.10 -192.168.1.19 - Unvalid?

Thanks.

That was my experience. You could have one of the ranges like this that has a space, but any range after that would give an error.


It may not be an actual bug, but it definitely wasn’t documented anywhere I could find. Maybe they could add a note to the config page where it gives the examples?

The general user of gargoyle probably doesn’t have access to the MAN pages anymore. Is that even a thing now?