The issue seems to lie in the blocking of an IP range like 196.0.0.0 - 196.255.255.255. Somehow the code that breaks this apart is not catching the separation between the two IPs.
New update - there was an older mod version before and it seems that it kept both start and end address of a range in the same DB column. Inserting the correct values directly in the DB sorted it.
It seems that the mod has another problem, cause the interface does not allow a way to add the IP range as above (196.0.0.0-196.255.255.255).
ipgate ranges were changed after I started working on the mod.
In the 2 current version in my sig, ranges are actually entered as 123. 123.123. 123.123.123.
anything after the last . is detected as the range so in the case of the 123.123.123. 123.123.123.1 - 123.123.123.255 would be detected
I have been working on another way on handling the ranges which would simply ip detection on the mod end, but would also also someone to use a subnet calculator and have more control over ban ranges. Life and work needs to slow down so I can port it into the mod. The update would require considerable backend mod changes and admin changes.
Thanks for the info . I guess some of the issues with inc_ipgate.asp that have been reported may be due to range storage in a single DB column, of course, when the mod is upgraded from a previous version.
Topic Locked
Posted - 05 January 2008 : 11:17:46
. I guess some of the issues with inc_ipgate.asp that have been reported may be due to range storage in a single DB column, of course, when the mod is upgraded from a previous version.