All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jorge Davila <davila@nicaraguaopensource.com>
To: "Krishnamoorthy (Siva) Sivakumar" <ksivakumar@packetmotion.com>,
	netfilter@lists.netfilter.org
Subject: Re: Iptables rule on span traffic
Date: Sat, 21 Apr 2007 09:54:32 -0600	[thread overview]
Message-ID: <web-69340783@bk1.webmaillogin.com> (raw)
In-Reply-To: <E8AFFEFDBE97C94E9297963F0527A07B01DFAED8@pmi00exf00.us.packetmotion.com>

What are your iptables rules?

On Fri, 20 Apr 2007 12:13:30 -0700
  "Krishnamoorthy (Siva) Sivakumar" <ksivakumar@packetmotion.com> wrote:
> Hi
> 
> I am new to this forum and my knowledge about iptables is fairly limited. 
>I did search but couldn't find an answer to my question; if this has been 
>addressed elsewhere, please point me to the source. 
> 
> Anyway, here is my situation. 
> I have fwsnort generate iptables rule (based on snort IDS rules) which are 
>running on a machine with two interfaces. One of the interfaces (eth1)  is 
>connected to a SPAN port that mirrors traffic on part of our network, this 
>interface is in promiscuous mode. The other interface (eth0) is a regular 
>addressable interface. For some reason, the iptables rules seem to have no 
>effect on traffic seen by the SPAN port. It seems to work fine on traffic 
>seen on eth0. I have tried using the -i option to specify the interface but 
>that doesn't seem to help. I am trying simple rules like "look for string 
>'ssh' and LOG traffic as well as reject with tcp reset" to troubleshoot.  
> 
> Anyone have any idea what I need to do to have iptables rule to act on 
>SPAN traffic. Tcpdump on eth1 does show traffic that the loaded iptables 
>rules should catch. Am I missing something in the way I have set things up?
> 
> Thanks,
> Siva
> 
> 

Jorge Isaac Davila Lopez
Nicaragua Open Source
davila@nicaraguaopensource.com


  parent reply	other threads:[~2007-04-21 15:54 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 [this message]
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
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=web-69340783@bk1.webmaillogin.com \
    --to=davila@nicaraguaopensource.com \
    --cc=ksivakumar@packetmotion.com \
    --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.