https://systems.nic.uoregon.edu/internal-wiki/index.php?action=history&feed=atom&title=Procedure%3ASetting_up_update_proxy 2026-08-19T11:26:12Z Revision history for this page on the wiki MediaWiki 1.39.12 https://systems.nic.uoregon.edu/internal-wiki/index.php?title=Procedure:Setting_up_update_proxy&diff=3024&oldid=prev 2020-02-04T02:09:07Z

<p>Created page with &quot;== Client setup == The client setup for use of a Squid proxy is remarkably simple. YUM and APT natively support use of it through a single modified configuration line. Curre...&quot;</p> <p><b>New page</b></p><div>== Client setup ==<br /> <br /> The client setup for use of a Squid proxy is remarkably simple. YUM and APT natively support use of it through a single modified configuration line.<br /> <br /> Current, Cerberus is configured to provide local proxying services to its 10.0.0.0/8 network and to 128.223.202.0/24 (i.e. the PRL).<br /> <br /> === Ubuntu 16 ===<br /> Add to /etc/apt/apt.conf.d/01-vendor-ubuntu (or presumably, whatever file here),<br /> <br /> Acquire::http::Proxy &quot;http://hostname:3128/&quot;;<br /> <br /> === CentOS/RedHat ===<br /> <br /> /etc/yum.conf:<br /> proxy=http://10.0.0.1:3128/<br /> <br /> <br /> == Server setup ==<br /> <br /> After installing SQUID 3 (yum install squid), /etc/squid/squid.conf see Cerberus<br /> <br /> Notable lines:<br /> <br /> refresh_pattern ^ftp: 1440 20% 10080<br /> refresh_pattern ^gopher: 1440 0% 1440<br /> refresh_pattern -i (/cgi-bin/|\?) 0 0% 0<br /> refresh_pattern (Release|Packages(.gz)*)$ 0 20% 2880<br /> refresh_pattern (Release|Packages(.bz2)*)$ 0 20% 2880<br /> refresh_pattern . 0 20% 4320<br /> refresh_all_ims on<br /> <br /> - Need to proxy both gz and bz2, different distros use different ones<br /> - make certain that Squid ACLs deny access to anything other than our network!</div>

Nic-systems