DRIVE

PS - on my server, even if it (my ip) is the only IP in whitelist it doesnt match it and blocks me. Even if I put two or three others or a couple dozen in there, it still does not match my IP. It only matches it when it does not exist in whitelist, and whitelist has enough of a listing that it does a partial match. Tested it backwards and forward. If I cut out several hundred of the preloaded whitelist IP's, it does not match it whether I put it in there or not.

PHP on that server is: 5.2.17 (Old Stable, not supported by PHP but still very common) http://php.net/downloads.php

So again:

My IP in Whitelist: blocked
My IP not in Whitelist: matches
My IP in in whitelist but white list reduced in size: blocked'

*ya, I made doubly sure that I was whacking it out of the blocked list when I tested

IP trap is matching my IP from the white list. I assume the white list that comes with IPT is loaded with many of the common bot/spider IP's since many use a lot of them (like google).

	$ipw = file ('../banned/Whitelist.txt');
  	$ip = $_SERVER["REMOTE_ADDR"]."\n";
	foreach( $ipw as $whiteip )

$ipw is a multi-line file. The way you structured "foreach" in secret.php wont do any accurate matching on my servers version of PHP. It is just reading it as a huge blob and saying that my ip is on the whitelist when it is not.

Works great for the IP_Trapped.txt though! I think the white/secret will have to be structured similarly to the iptrapped one but actually you need to get away from the \n deal and slurp the file in and do a foreach line or something.... eventually the file will be so large that it will bomb just because the function is a bit weak. At best it is doing a partial match... dont have much more time to trouble shoot it but partial matching will end up blocking a $#!+ load of wanted users