open proxy warning

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by dorris</i>
<br />noswal, are u using a proxy server, such as wingate for your connection?? certain proxy servers, wingate in particular, if not tightened enough, can become an open proxy server.
I have seen certain web sites pick me up as 168.x.x.x , I always thought it was due to the fact that I was NATing.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
Dorris, the 168. IP address is Sentech's transparent proxy (not his IP and so it's not due to him running an open proxy such as wingate on his system). The proxy is transparent (which means it effectively 'hijacks' your Web traffic and forces it to go through the proxy automatically always without you 'knowing') that's why websites pick you up as that even though you're not. It has nothing to do with your NATing. External sites, if you're NATing, would still pick you up as *your* real dynamically assigned IP address (i.e. ther 66. one) if it weren't for ST's transparent proxy .. I think you may be confusing the 168. (real IP address) with 192.168. private addresses often used behind a NAT system.
 
I just tested 168.210.90.180 from outside and inside.
It's not open. You can't connect to port 80 normally it just gives the follwoing error:

# telnet 168.210.90.180 80
Trying 168.210.90.180...
telnet: Unable to connect to remote host: No route to host

Which mean they're only allowing access to port 80 from a specified IP/IP Range.
I tried connecting to port 80 from my MW connection aswell...same error.


--
256k ... BAH..more like 25.6k
FSCK YOU Sentech!! [:(!]
 
Top
Sign up to the MyBroadband newsletter
X