Re: rewriting source and destination of local packets

[Arnt Karlsen <arnt@c2i.net>]

On Thu, 24 Mar 2005 11:26:44 +0100, martin wrote in message 
<[🔎] 20050324102644.GA28364@piper.madduck.net>:

> also sprach Raúl Alexis Betancort Santana <rabs@dimension-virtual.com>
> [2005.03.24.0948 +0100]:
> > Are you trying to do transparent proxy on a router/gateway with
> > dynamic ip on the public interface?, it's also you client's ip
> > dynamic?
> 
> "local packets" means: packets generated on the machine running
> squid itself. no "clients" involved.
> 
> Maybe this is clear:
> 
>   (nat table)
>   -A OUTPUT -o world -p tcp --dport 80 -j redirect-local-squid
>   -A redirect-local-squid -m owner --gid-owner 13 -j ACCEPT
>   -A redirect-local-squid -p tcp -j REDIRECT --to-port 3128
> 
> This works. Problem is that the packets arriving at 3128 have the
> dynamic external IP as source, when they should have 127.0.0.1.
> 

..having re-read this thread all the way from your Message-ID:
<[🔎] 20050323100605.GA24210@cirrus.madduck.net>, I _lost_ you.

..is this some kinda paid "research" you're doing for Microsoft???

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.