Advice on migration from Squid 2.2S5 to 2.3S2?
Steve Snyder
getting migration advice. Sorry if you've already read this]
I will soon be upgrading from Squid v2.2S5 to v2.3S2. So now I'm in
the proccess of planning what changes will need to be made to
accomodate the newer version.
This is on a RedHat box, with Linux kernel v2.2.14. I've got Squid
configured to act as a transparent proxy.
Below are my changes from the default Squid v2.2S5 configuration. I
understand that I will need to add the filesystem type to the "cache_dir"
parameter, but beyond that, what needs to be changed?
I've been reading of problems with v2.3S1's internal DNS resolution.
Should I disable internat resolution and stay with the use of
dns_children?
Any advice on v2.2S5-->v2.3Sx migrations issues and gotchas will be
appreciated. Thanks.
cache_mem 16 MB
cache_dir /var/spool/squid 256 2 254
cache_store_log none
dns_children 3
redirect_program /etc/squid/adzapper/squid_redirect
redirect_children 3
authenticate_children 3
quick_abort_pct 50
positive_dns_ttl 12 hours
acl all src 0.0.0.0/0.0.0.0
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl SSL_ports port 443 563
acl Safe_ports port 80 21 443 563 70 210 1025-65535
acl CONNECT method CONNECT
acl snydernet src 192.168.0.0/255.255.255.0
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow snydernet
http_access allow localhost
http_access deny all
icp_access allow snydernet
icp_access allow localhost
icp_access deny all
miss_access allow all
visible_hostname proxy.snydernet.lan
httpd_accel_host virtual
httpd_accel_port 80
httpd_accel_with_proxy on
httpd_accel_uses_host_header on
store_avg_object_size 8 KB
buffered_logs on
*** Steve Snyder ***
Henrik Nordstrom
> Which DNS do you use, internal or external?
I use 2.2.STABLE5+lots of patches, so that makes the external one
(internal isn't available in Squid-2.2).
> Do those "minor issues" also apply to v2.3STABLE2?
Most of the issues have patches on the squid-2.3 bugs page, and I guess
those patches are merged into 2.3.STABLE2 (haven't looked at that
release yet).
--
Henrik Nordstrom
Squid hacker
Steve Snyder
>Steve Snyder wrote:
>
>> This is on a RedHat box, with Linux kernel v2.2.14. I've got Squid
>> configured to act as a transparent proxy.
>> Below are my changes from the default Squid v2.2S5 configuration. I
>> understand that I will need to add the filesystem type to the "cache_dir"
>> parameter, but beyond that, what needs to be changed?
>
>I don't think much else needs to be changed from a configuration view,
>except that the dstdomain ACL has been cleaned up a lot and requires
>some rewriting of the name list (domains begins witha dot, hosts not).
>
>If you go for internal DNS then most directives related to DNS should
>also be removed.
>
>I am not sure what to recommend regarding the DNS at this time. The
>internal DNS implementation is still young and have some minor issues
>left to solve, but the external DNS implementation also has it's issues
>with queue lengths and so on (I have patches for the external DNS to
>make it acceptable, but it is not yet part of the standard
>distribution).
Which DNS do you use, internal or external?
Do those "minor issues" also apply to v2.3STABLE2?
Thanks.
*** Steve Snyder ***
Henrik Nordstrom
> This is on a RedHat box, with Linux kernel v2.2.14. I've got Squid
> configured to act as a transparent proxy.
> Below are my changes from the default Squid v2.2S5 configuration. I
> understand that I will need to add the filesystem type to the "cache_dir"
> parameter, but beyond that, what needs to be changed?
I don't think much else needs to be changed from a configuration view,
except that the dstdomain ACL has been cleaned up a lot and requires
some rewriting of the name list (domains begins witha dot, hosts not).
If you go for internal DNS then most directives related to DNS should
also be removed.
I am not sure what to recommend regarding the DNS at this time. The
internal DNS implementation is still young and have some minor issues
left to solve, but the external DNS implementation also has it's issues
with queue lengths and so on (I have patches for the external DNS to
make it acceptable, but it is not yet part of the standard
distribution).
--
Henrik Nordstrom
Squid hacker
http://squid.sourceforge.net/hno/squid/