Thanks! It's finally up and running. But, it's not quite smooth sailing yet:
1. DNS lookups fail completely. 204.127.198.4 is among a handful of external DNS servers I use, whether defined as dns_nameservers in squid.conf or picked by squid automatically from /etc/resolv.conf: 2009/05/20 21:44:49| comm_udp_sendto: FD 8, (family=2) 204.127.198.4:53: (22) Invalid argument 2009/05/20 21:44:49| idnsSendQuery: FD 8: sendto: (22) Invalid argument 2009/05/20 21:46:10| comm_set_tos: setsockopt(IP_TOS) on FD 7: (22) Invalid argument 2. Does that above have anything to do with the failure to apply this patch? patch -p0 < b9691.patch patching file src/dnsserver.cc Hunk #1 FAILED at 427. Hunk #2 FAILED at 436. 2 out of 2 hunks FAILED -- saving rejects to file src/dnsserver.cc.rej 3. I see the following in cache.log. I realize they're warnings, but is there any way to make squid "happy"? I thought the slash format is a CIDR mask. WARNING: Netmasks are deprecated. Please use CIDR masks instead. WARNING: IPv4 netmasks are particularly nasty when used to compare IPv6 to IPv4 ranges. squid.conf: acl sitelocalsrc src fec0::/48 acl linklocalsrc src fe80::/64 -------- Original-Nachricht -------- > Ah, possibly the init failure someone posted a fix for: > http://www.squid-cache.org/Versions/v3/HEAD/changesets/b9689.patch > > Amos > -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-aktionspreis/?ac=OM.AD.PD003K11308T4569a
