Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Djalel Chefrour <cdjalel@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Howo to get IP_NF_NAT_LOCAL behavior back after kernel 2.6.10 ?
Date: Wed, 27 Jul 2005 13:08:16 +0200	[thread overview]
Message-ID: <4a9dfdec0507270408427a9e20@mail.gmail.com> (raw)

Hi, 

I want to redirect local http traffic to a transparent squid porxy
running on the NAT box itself.

I've used :
# iptables -t nat -A OUTPUT -p tcp -m owner --uid-owner squid -j ACCEPT 
# iptables -t nat -A OUTPUT -p tcp --dport 80 -j REDIRECT --to-ports 3128 

But this works no more with kernel 2.6.11 & later.

# iptables -t nat -L -v 
gives this
---------------------------------------------------------------------------------------------------
Chain PREROUTING (policy ACCEPT 2281 packets, 906K bytes)
 pkts bytes target     prot opt in     out     source               destination 

Chain POSTROUTING (policy ACCEPT 97012 packets, 5712K bytes)
 pkts bytes target     prot opt in     out     source               destination 

Chain OUTPUT (policy ACCEPT 97005 packets, 5712K bytes)
 pkts bytes target     prot opt in     out     source               destination 
    0     0 ACCEPT     tcp  --  any    any     anywhere            
anywhere            OWNER UID match squid
    0     0 REDIRECT   tcp  --  any    any     anywhere            
anywhere            tcp dpt:http redir ports 3128

Chain loc_dnat (0 references)
 pkts bytes target     prot opt in     out     source               destination 

Chain wlan0_masq (0 references)
 pkts bytes target     prot opt in     out     source               destination 

---------------------------------------------------------------------------------------------------


TIA,
Djalel


             reply	other threads:[~2005-07-27 11:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 11:08 Djalel Chefrour [this message]
2005-07-29 11:26 ` Howo to get IP_NF_NAT_LOCAL behavior back after kernel 2.6.10 ? Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4a9dfdec0507270408427a9e20@mail.gmail.com \
    --to=cdjalel@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox