NET IPGATE v2

NET IPGATE v2.4.4 June 2007
by alex042@aol.com
modified by patrick@gpctexas.net

Version History:
-------------------------------------------------------------------------------------

0.5.0 BETA unsupported	08/27/02	Initial Release
0.5.1 BETA unsupported	08/27/02	Bug Fixes - main menu config, application variables
0.5.2 BETA unsupported	08/28/02	Bug Fixes - database setup
0.6.0 BETA unsupported	08/31/02	Added cookies, redirect option; Bug Fixes - logging
0.7.0 BETA unsupported	09/11/02	Added log expiration, enhanced ip capture, enhanced help, better Snitz integration; Bug Fixes - confirmation notices
0.7.1 BETA unsupported	09/19/02	Bug Fixes - set recordset closes, removed duplicate add
0.8.0 BETA unsupported	10/22/02	Added IP range ban & host ban, Added start/end dates, Added member logging & banning, Added cookie logging, Added basic admin ban prevention, Bug Fixes - removed record deletion asterick, removed include title, changed table theme tags, removed unused fields
0.8.5 BETA unsupported	05/03/03	gpctexas update: tried a different approach at range banning, fixed a few minor bugs in admin_ipgate.asp, changed sql some in inc_ipgate.asp. Added extra field to iplist table to support extra ranges. Cosmetic changes to admin_ipgate.asp
0.8.5 BETA unsupported		gpctexas update: removed <title>.....</title> tag from admin_ipgate.asp, page query's will be logged if the page requested has anything to the right of the ? in the address bar, otherwise the pagename will only appear.
0.8.7 BETA unsupported	05/21/03	Bug Fixes
v2.0.0 RC3 unsupported	8/09/03	gpctexas rewrite of inc_ipgate.asp ip subnet banning and logging. Used arrays for ip range checking for those who used the include in inc_header.asp, the include has been moved to the end of inc_header.asp to allow for admin logon in case of self ban. This move also allows for the use of the header and footer in the non redirect message to match your forum setup. admin_ipgate.asp logs will display a link to the page a user visited fixed a issue with modded forums when a query would exceed the maximum length for the page db field. A query will only get logged if the length of the page and query is less than 255 characters. If it is longer it will only log the page name. Fixed inc_ipgate.asp to only make 1 trip to the database instead of 2 trips. This should speed up the mod a little. It should be very hard for an administrator to now ban themselves, as long as you have moved your include file to the bottom of inc_header.asp as per upgrade instructions removed /forum/ from logs updated admin_ipgate to display Guest in the logs when no member id is present New Admin interface to improve ban setups. admin_ipgate.asp This page should simply the fields and the information that goes into them. added code to check for spaces before and after an ip addy. admin page will notify you if your ip address is included in a range ban admin page offers reverse ip address lookup Rewrite notes: username bans only require the username and an ipaddress of 0.0.0.0. When that user tries to log in, they will not have access to the forums. ip address bans only require an ipaddress and no username. iprange banning does not require an username but requires the 1st, 2nd, and/or 3rd octet of the ipaddress. entering 123.123. or 123.123.123. will ban any ipaddress that falls within that range. Note: the ip address range must end with a . Ip range, ip address, username banning/logging, lockdown, pagekeys have been tested and known to work. The default ban length is 30 days from adding a ban. the Special Access/pagekey feature will require a separate entry for each page you ban a user from viewing.. Cookies will now expire themselves are initial set based on the ending date. While that cookie is on their machine, their access attempts will get logged. New Admin page will update the mod version automatically if you resubmit the forum settings on the settings page. Future Plans: Have a ban record delete itself from the ban records when it is past its expiration date.
v2.0.0 Final	10/14/2003	Admin page tweaks and bug fixes
v2.1	10/26/2003	Optimized inc_ipgate.asp code added new functionality to the pagekeys option-You can now add multiple pages that you can deny access to. ip bans should work correctly whether or not the username has been banned first. Added 3 new message to show, which pertains to the users banned, blocked, or watched level. You should see a speed improvement in this release of the mod. Log view will only show the last 150 recent access to help with load times. The logs screen will get an overhaul in the next update.
2.2.7 Misc bug fixes
2.2.8 Misc Fixes		no db updates needed for patches if running 2.2.6-7
2.3.0 Misc fixes	9-2004	rescripted inc_ipgate.asp added new function, if the ipgate cookie is detected while a person is using an alternate name, the alternate name/ip is added to the ban table
2.3.1	March 2005	simplified ip checks, sped up the code. If a person's name or ip isn't in the db why make the script slow them down :)
2.4.3 beta 1 & 2	May 2005	New logs page, paginated :) Tweaks applied to the new logs page since first beta Speed improvements Minor tweaks to admin page off and on wrong bannings that appeared out of no where should no longer happen Misc improvements to the way the admin page handles css and standard forum code Misc tweaks to inc_ipgate.asp New admin status page ip address lookup from logs page Ipgate has always had 2 settings for logs, these have been combined and the unnecessary variable is no longer needed. Wording was changed on a few items in the admin page. planned for removal- ipgate lockdown planned for removal-old logs page(pending user approval) known probs: several gaps exist between several tables.
2.4.4 RC1	June 2007	dbs files fixed (I hope I got them all) logs have the ability to clean themselves after set amount of time (Yay!) various admin page tweaks Various CaSE SensItivE Fixes bug in inc_ipgate with cookies fixed Proxies Ugh-Shaggy may have fixed this one, his code is in use in inc_ipgate.asp Date issue using European date format fixed planned for removal- ipgate lockdown planned for removal-old logs page(pending user approval) known probs: several gaps exist between several tables.

Features:

-------------------------------------------------------------------------------------

IP Banning
- IP Banning On/Off
- Unlimited IP's
- Ban specific IP's, range of IP's or member
- Put a watch on specific IP's, range of IP's or member
- Allow special access to specific IP's, range of IP's, or member
- PageKey's blocks page access to a user/ip/range while banned, but allows general access to other pages not entered.
- Allows for temporary IP bans, watches, or access
- LOCKDOWN pages for website maintenance
- Sets & Checks for banned & watched IP cookies
- Allows for page redirects
- Admin ban prevention
- Automatic banning if a user changes name or ip address

IP Logging
- IP Logging On/Off
- Log All IP's w/ timestamp & member_id (if applicable) or logs only those in the IP database including those who may have changed IP's, but maintain cookies previously set
- Log expiration time frame allows easy log maintenance
- Easy IP adding through logs
- Paginated logs page
- Automatic log cleaning, for those who are forgetful :)

Contents :
--------------------------------------------------------------------------------------

readme.htm This file
admin_ipgate.asp New admin page
dbs_ipgate.asp Database Setup New Install (may be discarded after implementation)
dbs_ipgate_20ud.asp Database Update v0.8.7 to v2.4.3 (may be discarded after implementation)
dbs_ipgate_080ud.asp Database Update v0.7.1 to v2.4.3 (may be discarded after implementation)
dbs_ipgate_087ud.asp Database Update v0.8.0 to v2.4.3. (may be discarded after implementation)
inc_ipgate.asp Included page
ipgate_test.asp Test Page (used to test functionality. may be discarded.)
ipgate_banned.asp Customizable Include Page for Banned IPs
ipgate_lockdown.asp Customizable Include Page for Lockdowns
ipgate_noaccess.asp Customizable Include Page for Generic No Access
pop_ipgate_help.asp old help file Help File

Installation for Snitz 3.4:

--------------------------------------------------------------------------------------

New Install

Upgrades All Versions to current

How do I update the version information displayed in the admin_ipgate.asp page?

Click on the ipgate system settings link on the admin_ipgate.asp main page. You do not have to change the settings you have setup. Click submit and the new version information with be saved to the database. Then go to your forum admin page and click check installation. Your new version info will now be displayed for admin ipgate.

Implementation Ease: 2 (1 Easy - 10 Difficult)
MOD Dependencies: None

FOLLOW UPGRADE PROCEDURES IF YOU USED THE MOD BEFORE! AN IMPORTANT INC_IPGATE.ASP MOVED NEEDS TO BE PERFORMED!

New Install

After unzipping and saving the included files to your website:

Use MOD Setup dbs_ipgate.asp IPGate 2.4.3 Database Setup New Install on the forum admin page to setup the database.
Add the following to config.asp at the end of the DIM area :

Dim StrIPGateBan ,StrIPGateLck ,StrIPGateCok ,StrIPGateMet ,StrIPGateMsg ,StrIPGateLog ,StrIPGateExp, StrIPGateCss, strIPGateVer, StrIPGateLkMsg, strIPGateNoAcMsg, StrIPGateWarnMsg, strIPGateshowrecs, strIPGateAutoClean
Add the following to config.asp at the end of Application's

StrIPGateBan = Application(strCookieURL & "STRIPGATEBAN")
StrIPGateLck = Application(strCookieURL & "STRIPGATELCK")
StrIPGateCok = Application(strCookieURL & "STRIPGATECOK")
StrIPGateMet = Application(strCookieURL & "STRIPGATEMET")
StrIPGateMsg = Application(strCookieURL & "STRIPGATEMSG")
StrIPGateLog = Application(strCookieURL & "STRIPGATELOG")
StrIPGateExp = Application(strCookieURL & "STRIPGATEEXP")
StrIPGateCss = Application(strCookieURL & "STRIPGATECSS")
strIPGateVer = Application(strCookieURL & "STRIPGATEVER")
StrIPGateLkMsg = Application(strCookieURL & "STRIPGATELKMSG")
strIPGateNoAcMsg = Application(strCookieURL & "STRIPGATENOACMSG")
StrIPGateWarnMsg = Application(strCookieURL & "STRIPGATEWARNMSG")
strIPGateshowrecs = Application(strCookieURL & "STRIPGATESHOWRECS")
strIPGateAutoClean = Application(strCookieURL & "STRIPGATEAUTOCLEAN")
From the forum admin page, run Check installation to reinitialize application variables.
add to inc_header.asp,
insert:



to the very bottom of inc_header.asp right after the %>

should look like
%>
Add a link on your admin page to the admin file in this MOD:

" <LI><span class=""spnMessageText""><a href=""admin_ipgate.asp"">IPGate Configuration</a></span></LI>" & vbNewLine & _
Optionally, you may want to customize the redirect pages to match your site.
If you host multiple forums on the same domain then edit inc_ipgate.asp and locate

cookiename="IPGate" 'must change for each forum you host on the same domain!

and edit "IPGate" to a different name for each forum you use. copy inc_ipgate.asp to the forum folder that will use that cookiename.
If you want to auto ban potential ban evaders then edit inc_ipgate.asp and set autoban=1 else change to autoban=0
open ipgate config and set your options.

Upgrade

Use 0.8.7 update or locate your needed dbs file to update to v 2.4.3 update MOD Setup on the forum admin page to setup the database.
If you have a previous version installed and want to maintain the records, you can use the IPGate update dbs, otherwise, use the regular dbs file.
locate the following in config.asp at the end of the DIM area :

Dim StrIPGateBan ,StrIPGateLck ,StrIPGateCok ,StrIPGateMet ,StrIPGateMsg ,StrIPGateLog ,StrIPGateTyp ,StrIPGateExp

and change it to
Dim StrIPGateBan ,StrIPGateLck ,StrIPGateCok ,StrIPGateMet ,StrIPGateMsg ,StrIPGateLog ,StrIPGateExp, StrIPGateCss, strIPGateVer, StrIPGateLkMsg, strIPGateNoAcMsg, StrIPGateWarnMsg, strIPGateshowrecs, strIPGateAutoClean
locate the following in config.asp at the end of Application's

StrIPGateBan = Application(strCookieURL & "STRIPGATEBAN")
StrIPGateLck = Application(strCookieURL & "STRIPGATELCK")
StrIPGateCok = Application(strCookieURL & "STRIPGATECOK")
StrIPGateMet = Application(strCookieURL & "STRIPGATEMET")
StrIPGateMsg = Application(strCookieURL & "STRIPGATEMSG")
StrIPGateLog = Application(strCookieURL & "STRIPGATELOG")
StrIPGateExp = Application(strCookieURL & "STRIPGATEEXP")

and insert
StrIPGateCss = Application(strCookieURL & "STRIPGATECSS")
strIPGateVer = Application(strCookieURL & "STRIPGATEVER")
StrIPGateLkMsg = Application(strCookieURL & "STRIPGATELKMSG")
strIPGateNoAcMsg = Application(strCookieURL & "STRIPGATENOACMSG")
StrIPGateWarnMsg = Application(strCookieURL & "STRIPGATEWARNMSG")
strIPGateshowrecs = Application(strCookieURL & "STRIPGATESHOWRECS")
strIPGateAutoClean = Application(strCookieURL & "STRIPGATEAUTOCLEAN")

to the end.
From the forum admin page, run Check installation to reinitialize application variables.
copy the new files to your forum directory.
You may need to re-customize the redirect pages to match your site.
If you host multiple forums on the same domain then edit inc_ipgate.asp and locate

cookiename="IPGate" 'must change for each forum you host on the same domain!

and edit "IPGate" to a different name for each forum you use. copy inc_ipgate.asp to the forum folder that will use that cookiename.
If you want to autoban potential ban evaders then edit inc_ipgate.asp and set autoban=1 else change to autoban=0
Open ipgate config and set your options!