<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Controling interenet access with Squid proxy in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550073#M17741</link>
    <description>Depending on how complex your network is, you&lt;BR /&gt;could use something like the following:&lt;BR /&gt;&lt;BR /&gt;acl client src 192.168.2.0&lt;BR /&gt;acl domain dstdomain .ups.com&lt;BR /&gt;http_access allow client domain&lt;BR /&gt;http_access deny all&lt;BR /&gt;&lt;BR /&gt;If you are looking to implement this for more than 10 users, I would look into proxy_auth.. you can find all of the relevant informaton for proxy_auth here: &lt;A href="http://www.squid-cache.org/Doc/FAQ/FAQ-19.html#configuring-proxy-auth" target="_blank"&gt;http://www.squid-cache.org/Doc/FAQ/FAQ-19.html#configuring-proxy-auth&lt;/A&gt;</description>
    <pubDate>Mon, 23 May 2005 10:55:07 GMT</pubDate>
    <dc:creator>Ian Meyer_2</dc:creator>
    <dc:date>2005-05-23T10:55:07Z</dc:date>
    <item>
      <title>Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550069#M17737</link>
      <description>I would like to know if it is possible to control user access to internet with Squid proxy. I would like to be able to restrict some users to use just a few websites (like lookup for UPS or FedEx) and the rest should be unavailable for them.&lt;BR /&gt;Do I need to user RADIUS server for authentication, or Squid proxy can authenticate them?&lt;BR /&gt;&lt;BR /&gt;Miro&lt;BR /&gt;</description>
      <pubDate>Mon, 23 May 2005 09:44:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550069#M17737</guid>
      <dc:creator>mvr</dc:creator>
      <dc:date>2005-05-23T09:44:22Z</dc:date>
    </item>
    <item>
      <title>Re: Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550070#M17738</link>
      <description>You can control access through squid using ACL's in the squid.conf file.&lt;BR /&gt;&lt;BR /&gt;acl ups dstdomain &lt;A href="http://www.ups.com" target="_blank"&gt;www.ups.com&lt;/A&gt;&lt;BR /&gt;http_access deny all&lt;BR /&gt;http_access allow ups&lt;BR /&gt;&lt;BR /&gt;A good resource is the Squid faq located here: &lt;A href="http://www.squid-cache.org/Doc/FAQ/FAQ-10.html#ss10.1" target="_blank"&gt;http://www.squid-cache.org/Doc/FAQ/FAQ-10.html#ss10.1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;It explains ACL's and the different ways you can go about setting them up quite well.</description>
      <pubDate>Mon, 23 May 2005 10:21:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550070#M17738</guid>
      <dc:creator>Ian Meyer_2</dc:creator>
      <dc:date>2005-05-23T10:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550071#M17739</link>
      <description>&lt;BR /&gt;Thank you for information. This looks to me like it will deny access for EVERYBODY to anything except UPS. My next question would be if I could accomplish the same, but based on a single user or group.&lt;BR /&gt;&lt;BR /&gt;Miro&lt;BR /&gt;</description>
      <pubDate>Mon, 23 May 2005 10:31:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550071#M17739</guid>
      <dc:creator>mvr</dc:creator>
      <dc:date>2005-05-23T10:31:39Z</dc:date>
    </item>
    <item>
      <title>Re: Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550072#M17740</link>
      <description>Squid has a number of different authentication plugins (i'm sure there's a radius one around somewhere), and yes, you can tie the logged-in-user to given acl classes.&lt;BR /&gt;&lt;BR /&gt;The FAQ (url in the previous answer) has all the answers you are looking for.  Just read through it a bit more, and you'll answer your questions.</description>
      <pubDate>Mon, 23 May 2005 10:44:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550072#M17740</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2005-05-23T10:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550073#M17741</link>
      <description>Depending on how complex your network is, you&lt;BR /&gt;could use something like the following:&lt;BR /&gt;&lt;BR /&gt;acl client src 192.168.2.0&lt;BR /&gt;acl domain dstdomain .ups.com&lt;BR /&gt;http_access allow client domain&lt;BR /&gt;http_access deny all&lt;BR /&gt;&lt;BR /&gt;If you are looking to implement this for more than 10 users, I would look into proxy_auth.. you can find all of the relevant informaton for proxy_auth here: &lt;A href="http://www.squid-cache.org/Doc/FAQ/FAQ-19.html#configuring-proxy-auth" target="_blank"&gt;http://www.squid-cache.org/Doc/FAQ/FAQ-19.html#configuring-proxy-auth&lt;/A&gt;</description>
      <pubDate>Mon, 23 May 2005 10:55:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550073#M17741</guid>
      <dc:creator>Ian Meyer_2</dc:creator>
      <dc:date>2005-05-23T10:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550074#M17742</link>
      <description>I read the document that you sent me. A lot of great information. &lt;BR /&gt;I still don't understaned how can this be done if the Squid proxy is in DMZ, and computers are running in trusted zone.&lt;BR /&gt;&lt;BR /&gt;Miro</description>
      <pubDate>Mon, 23 May 2005 12:34:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550074#M17742</guid>
      <dc:creator>mvr</dc:creator>
      <dc:date>2005-05-23T12:34:54Z</dc:date>
    </item>
    <item>
      <title>Re: Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550075#M17743</link>
      <description>Not knowing your network topology, I can only add that Squid knows who is accessing it and what IP they are coming from as long as that IP address is not forwarded by a firewall or anything similar. So as long as Squid can see each machine's individual IP address you should be fine.. if not, that's a definite need for proxy_auth.&lt;BR /&gt;&lt;BR /&gt;Does that make any sense?</description>
      <pubDate>Mon, 23 May 2005 12:44:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550075#M17743</guid>
      <dc:creator>Ian Meyer_2</dc:creator>
      <dc:date>2005-05-23T12:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: Controling interenet access with Squid proxy</title>
      <link>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550076#M17744</link>
      <description>Given that you've got a trusted (which is probably being NAT'd out), and Squid in the DMZ (Huh? why? Put that inside too!), you'd probably have to go with some form of user authentication..&lt;BR /&gt;&lt;BR /&gt;Expanding on Ian's example..&lt;BR /&gt;&lt;BR /&gt;acl Courier_Users proxy_auth &lt;PERSON1&gt; &lt;PERSON2&gt; &lt;PERSON3&gt;&lt;BR /&gt;acl ALL proxy_auth REQUIRED&lt;BR /&gt;acl domain dstdomain .ups.com .fedex.com&lt;BR /&gt;http_access allow Courier_Users domain&lt;BR /&gt;http_access deny all Courier_Users&lt;BR /&gt;&lt;BR /&gt;(expanded from sections 10 and 19 of the FAQ)&lt;BR /&gt;&lt;BR /&gt;You'll need to set up an external Auth program (see the documentation on that), but this should restrict '&lt;PERSON1&gt;' etc. to only accessing those domains.&lt;BR /&gt;&lt;BR /&gt;If you aren't in a NAT'd environment, then you can tie it down to workstation, either by src, or by something else.&lt;/PERSON1&gt;&lt;/PERSON3&gt;&lt;/PERSON2&gt;&lt;/PERSON1&gt;</description>
      <pubDate>Mon, 23 May 2005 19:13:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/controling-interenet-access-with-squid-proxy/m-p/3550076#M17744</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2005-05-23T19:13:37Z</dc:date>
    </item>
  </channel>
</rss>

