Sniffing a linux bridge vs sniffing enslaved interfaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: <bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Sniffing a linux bridge vs sniffing enslaved interfaces
From: "The Q" <theq@xxxxxxxxxx>
Date: Mon, 16 Feb 2015 16:35:58 -0500
Delivered-to: bridge@xxxxxxxxxxxxxxxxxxxxxxxx
In-reply-to:
References:
Thread-index: AdBKL54LMpn5vmyPSM+aiKbHjCC5RAAAOWRg

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

Follow-Ups:
- Re: Sniffing a linux bridge vs sniffing enslaved interfaces
  - From: Joel Wirāmu Pauling

Prev by Date: Re: [PATCH] bridge: make it possible for packets to traverse the bridge withour hitting netfilter
Next by Date: Re: Sniffing a linux bridge vs sniffing enslaved interfaces
Previous by thread: [PATCH] bridge: netfilter: Move sysctl-specific error code inside #ifdef
Next by thread: Re: Sniffing a linux bridge vs sniffing enslaved interfaces
Index(es):
- Date
- Thread

[Index of Archives] [Netdev] [AoE Tools] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba] [Video 4 Linux]

Powered by Linux