From: Joe <joeja@mindspring.com>
To: netfilter@lists.netfilter.org
Subject: question on the nat table and iptables && REDIRECT
Date: Sun, 22 Sep 2002 22:38:55 -0700 [thread overview]
Message-ID: <3D8EA8EF.60909@mindspring.com> (raw)
Hello,
I am trying to get the redirect to work for use with squid. I know
that squid is working, but it seems that nothing from the local machine
is going through the nat PREROUTING table.
1) how do the tables interact with each other? i.e. if a rule in
the FILTER table is processed is that the end of it or does it make its
way through the NAT and MANGLE tables as well?
2) is there some reason that the POSTROUTING filter of the NAT
shows data going through it but the PREROUTING does not? How does the
PRE, POST and OUTPUT relate to each other? According to what I read the
packets should all go through the PRE, but this does not seem to be the
case.
output of iptables -L -v -t nat
#######################################
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 ACCEPT all -- ppp0 any anywhere
anywhere state RELATED,ESTABLISHED
1 48 ACCEPT all -- !ppp0 any anywhere
anywhere
0 0 LOG all -- any any anywhere
anywhere limit: avg 3/hour burst 5 LOG level warning prefix
`nat: PREROUTED -> unknown: '
Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
3 136 MASQUERADE all -- any ppp0 anywhere
anywhere
0 0 ACCEPT all -- any !ppp0 anywhere
anywhere
0 0 LOG all -- any any anywhere
anywhere limit: avg 3/hour burst 5 LOG level warning prefix
`nat: POSTROUTED unknown: '
Chain OUTPUT (policy ACCEPT 2 packets, 88 bytes)
#######################################
next reply other threads:[~2002-09-23 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 5:38 Joe [this message]
2002-09-23 15:17 ` question on the nat table and iptables && REDIRECT Antony Stone
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=3D8EA8EF.60909@mindspring.com \
--to=joeja@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.