From: "Marius Mertens" <marius.mertens@gmx.de>
To: netfilter@lists.netfilter.org
Subject: Re: Packets that should have been DNATted appearing in INPUT table
Date: Tue, 11 Jan 2005 19:33:23 +0100 [thread overview]
Message-ID: <009601c4f80c$0cd15d40$4206a8c0@loki> (raw)
In-Reply-To: Pine.LNX.4.05.10501111313200.7610-100000@darkstar.sysinfo.com
On Tuesday, January 11, 2005 7:16 PM,
R. DuFresne wrote:
> [...]
> at various links and sec websites on the net. But,this can be
> confirmed with comparing these INPUT hits with his FORWARDED NAT hits
> in the logs, yes?
Great idea, but I think we can exclude malicious attempts: The source IPs of
the "critical packets" all (without exception) have far more packets that
were correctly forwarded (several 10 or 100) than dropped (just 1 or 2 in
the same time).
Thank you very much,
Marius
prev parent reply other threads:[~2005-01-11 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 18:00 Packets that should have been DNATted appearing in INPUT table Marius Mertens
2005-01-06 15:55 ` Jason Opperisano
2005-01-06 16:49 ` Marius Mertens
2005-01-07 20:08 ` Michael Gale
2005-01-08 0:43 ` Marius Mertens
2005-01-11 0:27 ` R. DuFresne
2005-01-11 15:03 ` Marius Mertens
2005-01-11 16:29 ` Jason Opperisano
2005-01-11 18:15 ` Marius Mertens
2005-01-11 18:16 ` R. DuFresne
2005-01-11 18:33 ` Marius Mertens [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='009601c4f80c$0cd15d40$4206a8c0@loki' \
--to=marius.mertens@gmx.de \
--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