Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How can I make my users browsers use my cache without configuring the browsers for proxying?

0
Posted

How can I make my users browsers use my cache without configuring the browsers for proxying?

0

Getting transparent caching to work requires three distinct steps: • Getting the packets to your cache machine. If your proxy machine is already in the path of the packets (i.e. it is routing between your dialup users and the Internet) then you don’t have to worry about this step. If the cache is not in the natural path, then you have to divert the packets from the normal path to your cache host. You might be able to do this with a Cisco router, depending on your IOS version. You might also use a so-called layer-4 switch. • You have to configure your cache host to accept the redirected packets and deliver them to your cache application. This is typically done with IP filtering/forwarding features built into the kernel. On linux they call this ipfwadm. On FreeBSD and other systems they call it ip filter or ipnat. • Finally, you have to configure Squid to recognize the hijacked connections and discern the destination addresses. For linux this seems to work automatically. For FreeBSD you

0

Yes and no. The simple answer is no, you need the filter to be running on a seperate server. If you have squid/squidGuard running on a seperate server, you can redirect out-bound web traffic from the terminal server to the proxy/filter server.

0

First, it is critical to read the full comments in the squid.conf file! That is the only authoritative source for configuration information. However, the following instructions are correct as of this writing (July 1999.) Getting interception caching to work requires four distinct steps: • Compile and run a version of Squid which accepts connections for other addresses. For some operating systems, you need to have configured and built a version of Squid which can recognize the hijacked connections and discern the destination addresses. For Linux this seems to work automatically. For *BSD-based systems, you probably have to configure squid with the –enable-ipf-transparent option. (Do a make clean if you previously configured without that option, or the correct settings may not be present.) • Configure Squid to accept and process the connections. You have to change the Squid configuration settings to recognize the hijacked connections and discern the destination addresses. Here are the i

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.