From: tengaman@wolke7.net
To: netfilter@vger.kernel.org
Subject: Re: NAT not for filtering - problem
Date: Wed, 18 Feb 2009 03:58:46 +0100 [thread overview]
Message-ID: <20090218025846.GA5948@localhost> (raw)
In-Reply-To: <20090217232744.GA5471@localhost>
My own pondering results in some new, hopefully clearer questions:
How does the REDIRECTed packages look like?
I mean REDIRECT can't simply change the IP-destination-field into
127.0.0.1, because the proxy wouldn't know where to relay it, would it?
Is it true that this REDIRECTed packages, whatever they look like
go through the filter-output chain before being delivered locally to the
daemon-process?
If there exists detailed documentation on this matters please give me a
hint.
regards
Sebastian R.
prev parent reply other threads:[~2009-02-18 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 15:28 NAT not for filtering - problem tengaman
2009-02-17 23:27 ` tengaman
2009-02-18 2:58 ` tengaman [this message]
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=20090218025846.GA5948@localhost \
--to=tengaman@wolke7.net \
--cc=netfilter@vger.kernel.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.