From: prabha <prabha@multitech.co.in>
To: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: [Re: Logging packets with original address]
Date: Thu, 04 Mar 2004 12:05:55 +0530 [thread overview]
Message-ID: <4046CE4B.5D39CF03@multitech.co.in> (raw)
Hi
I can have the log in the PREROUTING chain. But, I have to log
ACCEPTed
and DROPped packets in the INPUT / FORWARD chains separately.
I use the options in the LOG target to tag the ACCEPTed and DROPped
packets.
So, I cannot have them logged in the PREROUTING chain, where we will not
know
whether the packet is going to be accepted or dropped.
I have to log the messages in the INPUT or FORWARD chains, but with
the
original addresses.
Regards
Prabha
From Antony@Soft-Solutions.co.uk Wed Mar 3 09:53:24 2004
>From: Antony@Soft-Solutions.co.uk (Antony Stone)
>Date: Wed, 3 Mar 2004 09:53:24 +0000
>Subject: Logging packets with original address
>In-Reply-To: <4045A0F1.F7366A69@multitech.co.in>
>References: <4045A0F1.F7366A69@multitech.co.in>
>Message-ID: <200403030953.24832.Antony@Soft-Solutions.co.uk>
>On Wednesday 03 March 2004 9:10 am, prabha wrote:
> Hi
> I want to log some packets in the INPUT and FORWARD chains, but
with
> the original address of the packets. (ie) with the destination address
> before any DNAT rule has been applied on the packet in the PREROUTING
>chain.
>You cannot do this because packets pass through the INPUT chain after
they
>pass through PREROUTING.
> When the packet comes to the INPUT / FORWARD chains, it will be
> after any DNAT has been applied.
>Correct.
> I do not want the NATted address to be present in the logs, but the
original
> address as the received interface saw it. Is this possible?
>Put the LOG rule in the PREROUTING chain.
>Regards,
>
>Antony.
reply other threads:[~2004-03-04 6:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4046CE4B.5D39CF03@multitech.co.in \
--to=prabha@multitech.co.in \
--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.