| Author |
 Topic  |
|
gpctexas
Junior Member
320 Posts |
 Posted - 07 February 2005 : 22:21:14
|
| Ah that's good. It is hard for me to debug and test things since my orig host I had flew the coop. I'm slowly trying to get my new web host setup similar to what I had lost on old host. Nice to see ya got it going.< |
ipgate 2.4.4 RC3
http://www.gpctexas.net/ipgate_v244.zip |
 |
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 09 April 2005 : 08:35:43
|
I have had a BUNCH of "good" members get banned with the auto cookie that are logging in using AOL.
I assume the precision on the auto ban cookie is set to three sets of ip numbers only? 123.345.789.xxx
This is s huge problem for us. Where, and is there a way to make the auto ban (even though it may not work as well) go to the Exact ip ony to set a cookie?
Help!  < |
|
|
|
gpctexas
Junior Member
320 Posts |
Posted - 09 April 2005 : 13:37:15
|
The cookie is based on the ban you setup, if you used 123.123 then it will catch everyone in 123.123, same with 123.123.123. You will need to add your range to the expire cookie option and ban by full ip or username for the bad user or change the cookie name in inc_ipgate.asp to get the others back in.
Which version are you using 2.3 or 2.4 I just put up 2.4 yesterday on snitzbitz< |
ipgate 2.4.4 RC3
http://www.gpctexas.net/ipgate_v244.zip |
|
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 10 April 2005 : 01:05:39
|
2.3
I'll get the 2.4
This problem was happening on the AUTO cookies. Three aol's had the first 3 sets the same and bammo.
I'll get 2.4 and look over the ip's that were banned earlier by another. Perhaps it caused a chain reaction?
Thanks for responding so quickly!
gmann< |
|
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 10 April 2005 : 01:07:38
|
PS: I expired all their cookies and all is ok now, but I have auto cookies off and I'd rather not!
thanks again< |
|
|
|
gpctexas
Junior Member
320 Posts |
Posted - 10 April 2005 : 02:05:50
|
If you used the range, then the autoban is working as intended. It prevents the same user from trying to re-reg or if they have more than one name it is intended to catch then. Like many things there are side effects. I may try and code the autoban to only detect full ip addresses or usernames, but it may take changing the way cookies are saved to make it work. Right now it detects banned and watched cookies.
Another work around is to set the good ip addresses to expire ban and leave the range. Expire ban is basically a bypass mechanisn too, but requires that user to remain logged in.< |
ipgate 2.4.4 RC3
http://www.gpctexas.net/ipgate_v244.zip |
|
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 10 April 2005 : 20:38:12
|
quote:
I may try and code the autoban to only detect full ip addresses or usernames, but it may take changing the way cookies are saved to make it work.
I think that was the problem, sorry to have to say.< |
|
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 10 April 2005 : 22:10:30
|
I'm not clear what all needs to be changed for ver 4...
Your readme seems to be about ver 3.
Could you elaborate?
(Sorry to be a pain)< |
|
|
|
gpctexas
Junior Member
320 Posts |
Posted - 10 April 2005 : 22:43:19
|
edit inc_ipgate.asp
there is a setting there to enable autoban.
copy admin_ipgate.asp and inc_ipgate.asp to forum. No db update needed, just a code change that uses different ip comparisons. Also only pulls records related to current user to compare to, should speed things up. 2.4 is still beta and only tested on test server and was released on servhackers site a week ago, nobody has mentioned any probs yet.< |
ipgate 2.4.4 RC3
http://www.gpctexas.net/ipgate_v244.zip |
|
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 11 April 2005 : 23:38:53
|
Great!
Thank you very much (again) < |
|
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 19 April 2005 : 07:51:16
|
FYI we added another name or two (Big hassles at our forum)  and
post.asp locked up (one of the ipban pages) with this error(Line 87 inc_ipgate.asp)
if dbrecordarr(3) < 0 or dbrecordarr(3) > 255 then
dbrecordarr(3) = 0
end if
Is the 255 some sort of max? Can I raise it and still be in good standing with the "force"?
Figured you'ld wanna know< |
|
|
|
gpctexas
Junior Member
320 Posts |
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 19 April 2005 : 08:45:55
|
I'l have to put the upgrade one back in and try to post to recreate.
I'll do that now and be back< |
|
|
|
golfmann
Junior Member
United States
450 Posts |
Posted - 19 April 2005 : 08:51:58
|
ok when we try and post (I'm sure because the IP Gate inc language is in post) we get this:
Microsoft VBScript runtime error '800a000d'
Type mismatch: 'dbrecordarr(...)'
/forum/inc_ipgate.asp, line 87
BTW it worked fine until the latest ipban was inserted yesterday...< |
|
|
|
HuwR
Forum Admin
United Kingdom
20584 Posts |
Posted - 19 April 2005 : 09:15:20
|
| If you are having problems with a particular MOD, pleas post in the mod implementation forums rather than here.< |
|
|
|
Topic |
|
IPGate 2.4.3 beta and 2.3
