[General] FT Cache Compromised (Again)

Majed B. majedb at gmail.com
Thu Dec 4 11:10:34 +03 2008


The client that is using a proxy will go through port 3128 for
example, but I think the proxy itself will go through the web over
port 80 again, which is why it gets filtered.

My point was: since you have 2 machines, one local & one remote, just
configure the local proxy to route all traffic (route not cache and
forward requests) to the remote one. This way you're no longer going
through your ISP.

It's hooking the remote machine with the local through VPN, and the
remote box is the gateway to your proxy.

On Thu, Dec 4, 2008 at 10:59 AM, Bashar Al-Abdulhadi
<bashar at kuwaitnet.net> wrote:
> having local machine when accessing the internet via your ISP via port 80 it
> will be triggered by your ISP's caching system and wwill be filtered again,
> so no real use of it, thats why when you put a remote box to connect to it
> via non-default http port then that remote box goes to the internet
>
>
> for example from your local machine do wget www.skype.com it will show FT's
> blocked page it will be the same when squid/proxy access the internet from
> the machine
-- 
       Majed B.




More information about the General mailing list