I was using my 3.0 squid.conf, slightly tweaked to suit 3.1, when I encountered those three issues. I did later try the 3.1 default, again with slight tweaks, as seen below. The DNS lookup issue persisted with that route:
diff squid.conf.default squid.conf 2,3c2,3 < acl localhost src 127.0.0.1/32 < acl to_localhost dst 127.0.0.0/8 --- > acl localhost src 127.0.0.1/32 ::1 > acl to_localhost dst 127.0.0.0/8 ::1 22a23 > http_access allow localhost 25c26 < http_port 3128 --- > http_port 3129 27c28,31 < coredump_dir /usr/local/squid31/var/cache --- > coredump_dir /Applications/squid > cache_access_log /Applications/squid/logs/access.log > cache_log /Applications/squid/logs/cache.log > cache_store_log none 31a36 > debug_options ALL,1 0,5 78,9 In addition, I've also tried replacing the ISC BIND daemon listening on localhost:53 with the 6to4-tranlating totd, or have squid 3.1 cache-peering with Polipo, all to no avail. -------- Original-Nachricht -------- > Sorry I didn't get to this a few days ago. > > Are you using the default squid.conf that gets built with 3.1 or an > altered version? > Problem #3 will show up for some settings even though there is not yet > any other way to do them than netmasks. So it needs to be looked at but > in some cases can be ignored. > > Problem #1, I'm still thinking about. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE6 or 3.0.STABLE15 > Current Beta Squid 3.1.0.8 or 3.0.STABLE16-RC1 -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02
