netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: carlopmart <carlopmart@gmail.com>
To: netfilter@vger.kernel.org
Subject: A question about ebtables and virtual switching
Date: Thu, 12 May 2011 10:17:06 +0200	[thread overview]
Message-ID: <4DCB9782.6030605@gmail.com> (raw)

Hi all,

  I have installed a virtual machine with snort to sniff traffic on a 
dedicated virtual lan.

  But exists a problem: this snort vm only sees traffic destinated to 
its own MAC address and traffic with the multicast bit set in the 
destination address. This scenario is unusable for snot.

  I have found a partial soultion: set ageing to 0 in host's bridge but 
this produces another problem, all vms attached to this virtual switch 
sees all traffic, and that is not what I want.

  If I not wrong, ebtables is the solution to make snort work, but I 
didn't find any doc about how can I implement this solution.

  How can I configure ebtables rules to make a port mirroring in this 
virtual switch where snort needs to sniff??

  I am using KVM as virtualization platform.

  Thanks.
-- 
CL Martinez
carlopmart {at} gmail {d0t} com

                 reply	other threads:[~2011-05-12  8:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4DCB9782.6030605@gmail.com \
    --to=carlopmart@gmail.com \
    --cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).