I've seen several VPN solutions implemented by companies that disable the connection to the local network when the company-VPN is started. An easy test to verify this : - ping your linux machine (192.168.1.3) : this should work (if the linux-firewall is not blocking this) - start company VPN - ping 192.168.1.3 again : If this doesn't work anymore, the VPN probably changed your routing table and disabled access to your own local network. If so : I'm afraid you will have to convince the company-guys ... Koen. -----"GJones" <jg.jones@xxxxxxxxxxx> wrote: ----- To: <squid-users@xxxxxxxxxxxxxxx> From: "GJones" <jg.jones@xxxxxxxxxxx> Date: 21/03/2006 22:44 Subject: Squid not routing when logged into VPN I have a very basic home network set up and I am trying to use Squid for my proxy. I realize it may be a little overkill, but........ I have squid running on a linux server (debian) and as long as I am not logged into my companies VPN, it works fine. The other PC's on my network are routed through the Proxy a well but are not used for VPN connections. But once I log into the VPN, all of my HTTP traffic is no longer routed through Squid, but onto my companies VPN network. (My client machines is a IBM notebook running XP) I have Internet Explorer set up to use the Proxy server. I use the linux servers IP address (192.168.1.3) and default port (3128). I realize this may not be a squid problem, but any help and/or pointers are appreciated. Grant
