I have a theory that the cause is the modem I am using at location 1. I will
have this modem swapped out with a different one and test later this week.
Here's the image.
http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4664360/diagram.png
--
View this message in context:
Wanted to send an update---
So To rule out CentOs and the Squid install I have grabbed the VMware image
of the known good (location 2) centos/squid, copied it over to location 1,
changed the ip, validated iptables and tested. Same results.
So we can safely assume that its not centos or the
Further research:
There's a utility called http-ping.exe that pings http for a response. This
shows a timeout from location 2 to location 1 calling google.com through the
proxy. Vice versa, no timeout.
*From Location 1 -- 2*
Hi Thank you for the reply. Your right I did fail to mention. Yes squid
proxy works locally on the same local subnet just fine. The issue is only
from location 2 to Location 1 traversing through the IPSEC Tunnel.
--
View this message in context:
Hi All-
So I have a need to direct all web traffic through an IPSEC Tunnel to a
Squid Proxy server on the other end of the tunnel.
Sounds complicated but the concept is really easy however I am having
issues.
So let me gather as much info as I can:
*Location 1 Subnet:* 192.168.1.0/24
I noticed this could be complicated to the readers so I have drew up a Visio
Diagram to illustrate the flow so my question and issue is better
represented.
http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4664322/proxyissue.png
--
View this message in context:
