From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Re: LOG one particular IP traffic (Antony Stone)
Date: Thu, 8 Apr 2004 18:36:30 +0100 [thread overview]
Message-ID: <200404081836.30490.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <006a01c41d89$94419eb0$da0da8c0@pisic>
On Thursday 08 April 2004 5:50 pm, Danila Octavian wrote:
> I'm sorry for posting twice but i messed up my mail accounts... I was
> sending to the list from a non-member account... I fixed that ...
Okay :)
> but regarding my problem ... i don't know how am I supposed to log
> everything originating from 192.168.13.222 going to 0.0.0.0 except three
> destinations : - intip
> -extip
> -localnet
>
> can you give me an example line : iptables -A ... ?
iptables -A POSTROOUTING -t mangle -o eth0 -s 192.168.13.222
Yes, that's the entire rule - there is no -j TARGET at the end :)
How does this work?
1. It is in the POSTROUTING mangle table, therefore it's the very last bit of
netfilter before the packet hits the wire - this means you catch *all* the
packets (the filter and nat tables will miss some, for connection tracking
reasons).
2. It's looking at packets leaving eth0 (I'm assuming this is your external
interface - change as appropriate if not), so it's not going to see anything
addressed to your internal machines or the firewall itself.
3. It matches packets with a source address of the one machine you are
interested in, and.... well... simply counts them. There is no target at
the end of the rule, so nothing special happens to the packets (they're not
dropped, or accepted, or rejected, or natted, or mangled), however the
byte/packet counters for the rule will still tell you how many matched.
4. Every time you want to know how many packets & bytes have some from that
machine, do a "iptables -L -t mangle -nvx" and the first two columns tell you
what has matched the rule (this is probably your only rule in the mangle
table).
Hope that helps,
Antony.
--
"The joy of X!!?? I've always hated compiling graphical shite. You have a 10
line program, and it ends up depending on the entire known universe."
- Philip Hands
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-04-08 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 16:50 Re: LOG one particular IP traffic (Antony Stone) Danila Octavian
2004-04-08 17:36 ` Antony Stone [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=200404081836.30490.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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