<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Courier New, Courier, monospace">So I am new to squid
and trying to take over from what was already in place. <br>
Do you have an example of what it should look like or a best
practice guide to use.<br>
We can have up to 32 /24 blocks in our configurations.<br>
I want to try and make the systems as efficient as possible
knowing the large amount of IPs we are using.<br>
<br>
Thanks<br>
</font><br>
<div class="moz-cite-prefix">On 4/20/2020 15:16, Alex Rousskov
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f9a2f5f0-faba-dbdd-b91d-257751eed41a@measurement-factory.com">
<pre class="moz-quote-pre" wrap="">On 4/20/20 10:48 AM, James Adams wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">acl 1 myportname 1 src all
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I agree with Amos that you should consider automating these
configuration lines. Your access control and request routing
requirements are probably too special to warrant adding a new Squid feature.
While writing the config-generating script, please remove the "src all"
trailing garbage(?) from myportname ACL definitions. I would also
recommend avoiding using bare numbers as port and ACL _names_: It is
very confusing for many human readers, and might even cause parsing
failures in future Squid versions.
HTH,
Alex.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
James Adams
Sr. Systems Engineer
MOD Mission Critical</pre>
</body>
</html>