Search squid archive

Re: transparent (intercepting?) without wccp, options?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "Amos" == Amos Jeffries <squid3@xxxxxxxxxxxxx> writes:

    > On 04.07.2012 15:54, Ezequiel Birman wrote:
    >>>>>>> "Eliezer" == Eliezer Croitoru <eliezer@xxxxxxxxxxxx> writes:
    >> 
    > <snip>

    >> http://wiki.squid-cache.org/ConfigExamples/Intercept/DebianWithRedirectorAndReporting
    >> >> > this is a good way to start but it wont be a transparent
    >> proxy but > a "nat" proxy but it can be good for your needs as
    >> anyway you have > nat in the RV042.
    >> 
    >> Are you sure? The only mention to nat in is in order to redirect
    >> port 80 to 3128 on squid box. This is the intro:
    >> ...

    > Yes. There are 4 protocol layers involved.  ebtables - rules stops
    > it being a bridge "transparent relay/proxy" and makes it routed
    > traffic.  iptables - rules use NAT (interception proxy) instead of
    > TPROXY (transparent proxy).  squid - config file uses
    > URL-rewriters to prevent Squid being a HTTP protocol "transparent
    > proxy" (HTTP definition of "transparent proxy" is the Squid
    > default behaviour).

    > There is a lot of people confused by the meaning of the word
    > "transparent". With good reason, it has been used out of context
    > so much.

Where should I start then? Could yo point me to some doc, tutorial or
config example to implement what Eliezer suggested? I mean beside the
books which I didn't buy yet.

Regards
  
-- 
Ezequiel Birman



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux