Ethernet Bridge development
 help / color / mirror / Atom feed
From: "The Q" <theq@rogers.com>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Sniffing a linux bridge vs sniffing enslaved interfaces
Date: Mon, 16 Feb 2015 16:35:58 -0500	[thread overview]
Message-ID: <02f601d04a30$8eb33820$ac19a860$@rogers.com> (raw)
In-Reply-To: 

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]

 

Hi all

 

Assume that you have a linux bridge with two interfaces eth0 and eth1
enslaved to this bridge

What is the difference between sniffing the bridge and sniffing its
interfaces?

 

tcpdump -i br0   vs tcpdump -i eth0

 

Thanks

MiniME


[-- Attachment #2: Type: text/html, Size: 2229 bytes --]

             reply	other threads:[~2015-02-16 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 21:35 The Q [this message]
2015-02-16 22:17 ` [Bridge] Sniffing a linux bridge vs sniffing enslaved interfaces Joel Wirāmu Pauling
2015-02-16 22:28   ` Stephen Hemminger
2015-02-16 22:39   ` Q

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='02f601d04a30$8eb33820$ac19a860$@rogers.com' \
    --to=theq@rogers.com \
    --cc=bridge@lists.linux-foundation.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