Proxy ip to real ip conversion

This modification is no longer available or supported.

A simple modification I did for our forum that was originally based on the Proxy Detector Hack (v3.0). Obviously, like all proxy server detection hacks, this will only work if the proxy server passes the appropiate http variables.

This hack makes the forum always use the members real ip when a proxy is detected, meaning that all existing ip functions continue to work, basically ignoring the proxy server (other than recording it's presence).

i.e.

* The real ip/host is displayed in who's online

* The real and proxy server ip's are accesible for each post, the button is red for members using a proxy.

* The real ip is searchable in the admin/mod cp, not the proxy ip.

* The real ip is bannable by admins (no moving to another proxy to avoid a ban).

etc etc.

The installation should take about 10-15 mins (4 file edits, 2 phrase changes, 1 new template, 1 sql query, 1 new image).

[Paul M]

Originally Posted by xheliox

PS - the range is 172.16.0.0 through 172.31.255.255.. I'm a regex moron, how would I add that range?

preg_match("#^(10|172\.[16-31]|192\.168)\.#", $proxyip))

?

I'm not sure that would work - regex gives me headaches - I'll look into it for you.

[xheliox]

Originally Posted by Paul M

I'm not sure that would work - regex gives me headaches - I'll look into it for you.

Yeah, my way didn't work at all. It just broke the whole thing.

I appreciate it.

[Paul M]

Try this;

PHP Code:

if (preg_match("#^(10|172\.(1[6-9]|2[0-9]|3[0-1])|192\.168)\.#", $proxyip)) 


[xheliox]

That seems to work.. I'll keep an eye on it and let you know. Thanks again!

[David Bott]

I was just coming here to post about this same issue. I just had an issue with 127.0.0.1 and also some 10.X.X.X numbers. I do not think the above handles 127's. Somtimes hacks just work too good.

[Paul M]

Originally Posted by David Bott

Somtimes hacks just work too good.

No, they work as designed.

I have no reason to exclude those addresses, so my hack doesn't. If you don't want them then use the extra code posted above, you can add 127.x.x.x to it easily enough as well.

[David Bott]

Hi Paul...Thanks for the reply. I am sorry to say I am not advanced enough to understand how to add in the 127 range. Can you please be so kind to advise.

Thank you in advance. (Currently dealing with a problem user.)

[Paul M]

Originally Posted by David Bott

Hi Paul...Thanks for the reply. I am sorry to say I am not advanced enough to understand how to add in the 127 range. Can you please be so kind to advise.

Sure - I have updated the code in Post 98 for all the changes.

[David Bott]

Paul...Here is something for you to REALLY help in this case...

http://www.tcpipguide.com/free/t_IPR...ddresses-3.htm

It lists all the private IP's that could be used. (Not many)

Thank you for the updates!!!!

BTW...I am gussing that if the code finds any of these private IPs, it will just use the reported proxy IP like it did not find anything. (Thus we can choose to block the proxy if need be.)

BTW...Now running on TiVo Community (http://www.tivocommunity.com) and will be at AVS Forum after I convert that. (http://www.avsforum.com)

[Paul M]

Thanks - the only one really relevant in that list that was missing was the DHCP auto range of 169.254.x.x - I have added that.

BTW - you just reminded me to check my old Tivo userid out - I joined in 2002 !