Re: connect: no route to host...

This sounds like you are behind a firewall (or forgot to add a default
route in your hosts routing table).

If you are inside a firewall, then use inside_firewall in squid.conf, to
force requests to go by a parent.

If you are not inside a firewall, then make sure that your routing table
is correct (check with netstat -rn).

The "No route to host" errors is your host (Linux Squid server) telling
Squid that it can't reach the destination. You can verify this by doing
a "telnet 204.162.96.10 80" from your Squid server.

---
Henrik Nordstr�m
Sparetime Squid Hacker
Daniel Suen wrote:
> not work. Whenever it tries to direct connect to a URL that contains ? or
> cgi, or *.exe stuff, it returns "no route to host". I have turned on the
> debugging level to 9, and I saw,
> 
> connect: 204.162.96.10:80: (113) No route to host.
...
> Our configuration is as an ICP client of two parent cache hosts, and
> nothing about "cgi" or "?" in the configuration file had been changed.
> Does anyone know what the problem is?