From: nadim <nadim@khemir.net>
To: netfilter@lists.netfilter.org
Subject: Re: Primordial tool missing
Date: Fri, 13 Aug 2004 10:13:10 +0200 [thread overview]
Message-ID: <200408131013.10490.nadim@khemir.net> (raw)
In-Reply-To: <00bf01c480a4$31863f50$a900a8c0@cybergeneration.com>
Thanks for your answer (you too Jason) but I still think the tool _is_
primordial. Fideling with the rules and tailing the log is about as close a
"last resort" as can be. One might also want to try different setups of
rules, etc...
Now I have no ideas of how iptables works and I don't have time to dig into
all the details but if someone gives me a hand, I'll write a perl script.
Cheers, Nadim.
On Thursday 12 August 2004 21:40, Maxime Ducharme wrote:
> Hey Nadim
>
> I suggest that you use logging mechaninsm of iptables,
> put -j LOG lines in many tables, it will allow you to "see"
> the packets going trough tables and chains.
>
> By default packets are logged in /var/log/messages
>
> a good schema on how it works :
> http://iptables-tutorial.frozentux.net/iptables-tutorial.html#TRAVERSINGOFT
>ABLES
>
> a good example script of -j LOG :
> http://iptables-tutorial.frozentux.net/iptables-tutorial.html#INCLUDE.TESTT
>ABLES
>
> (option "--log-prefix" is important here to know where you are)
>
> I also suggest that you dont drop a packet before logging it,
> you may add a logging rule to every DROP or REJECT
> rules you may have in your configuration. It also helps
> to know where the packet have been dropped.
>
> Hope this helps
>
> Have a nice day
>
> Maxime Ducharme
> Programmeur / Spécialiste en sécurité réseau
>
> ----- Original Message -----
> From: "nadim" <nadim@khemir.net>
> To: <netfilter@lists.netfilter.org>
> Sent: Thursday, August 12, 2004 3:47 AM
> Subject: Primordial tool missing
>
> > Hi,
> >
> > For you gurus this might be superfluous but for the lambda user a tool
>
> which
>
> > given an input packet (xxx.xxx.xxx.xxx:tcp:25) and a set of rules, show
>
> how
>
> > the packet goes from one rule to the other and finally make it to it's
> > destination , gets tansformed or dropped.
> >
> > This would help enormously in understanding how this stuff works (no it's
>
> not
>
> > that obvious) and I also think it would be a great help when adding
> > rules.
> >
> > Does such a utility exist?
> >
> > Cheers, Nadim.
prev parent reply other threads:[~2004-08-13 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 7:47 Primordial tool missing nadim
2004-08-12 15:47 ` Jason
2004-08-12 19:40 ` Maxime Ducharme
2004-08-13 8:13 ` nadim [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=200408131013.10490.nadim@khemir.net \
--to=nadim@khemir.net \
--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