From: Martijn Lievaart <m@rtij.nl>
To: "Krishnamoorthy (Siva) Sivakumar" <ksivakumar@packetmotion.com>
Cc: netfilter@lists.netfilter.org,
Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Subject: Re: Iptables rule on span traffic
Date: Mon, 23 Apr 2007 07:44:43 +0200 [thread overview]
Message-ID: <462C47CB.8030806@rtij.nl> (raw)
In-Reply-To: <E8AFFEFDBE97C94E9297963F0527A07B01DFB187@pmi00exf00.us.packetmotion.com>
Krishnamoorthy (Siva) Sivakumar wrote:
> You could try to turn on forwarding and block all traffic that makes it
> through the snort rules.
>
> HTH,
> M4
>
> [Siva:]
> Can you explain in more detail (sorry I am a novice)? How do you turn on forwarding? Does this require the iptables machine to be inline (in addition to a regular firewall/router that does the actual forwarding)?
>
>
http://www.google.nl/search?q=linux+forwarding :-)
HTH,
M4
next prev parent reply other threads:[~2007-04-23 5:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 19:13 Iptables rule on span traffic Krishnamoorthy (Siva) Sivakumar
2007-04-21 13:46 ` Oleg
2007-04-21 15:54 ` Jorge Davila
2007-04-21 16:23 ` Cedric Blancher
2007-04-21 19:44 ` Krishnamoorthy (Siva) Sivakumar
2007-04-21 21:20 ` Pascal Hambourg
2007-04-23 3:48 ` Krishnamoorthy (Siva) Sivakumar
2007-04-23 5:25 ` Martijn Lievaart
2007-04-23 5:41 ` Krishnamoorthy (Siva) Sivakumar
2007-04-23 5:44 ` Martijn Lievaart [this message]
2007-04-23 16:53 ` Krishnamoorthy (Siva) Sivakumar
[not found] ` <016c01c78593$061fc2e0$0302a8c0@southern>
[not found] ` <E8AFFEFDBE97C94E9297963F0527A07B01DFBA0D@pmi00exf00.us.packetmotion.com>
[not found] ` <007301c787a6$13fdceb0$6501a8c0@southern>
2007-04-26 2:21 ` Krishnamoorthy (Siva) Sivakumar
[not found] ` <be4ffce60704260256j5cd06e93o6aeb512cb5fd36a1@mail.gmail.com>
2007-04-26 16:15 ` Krishnamoorthy (Siva) Sivakumar
2007-04-21 19:33 ` Oleg
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=462C47CB.8030806@rtij.nl \
--to=m@rtij.nl \
--cc=ksivakumar@packetmotion.com \
--cc=netfilter@lists.netfilter.org \
--cc=pascal.mail@plouf.fr.eu.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.