Re: bond or bridge sniffing

From: Omer Faruk Sen
Date: Tue Dec 02 2008 - 16:23:35 EST


My problem is that I tcpreplay traffic at eth1 but I cant see or sniff
it on bond0 (composed of eth1,2,3) but if I do the reverse (replay
traffic at bond0 and sniff at eth1) it works without a problem. My
kernel is 2.6.18-8.el5 (the one that comes with rhel5)

On Tue, Dec 2, 2008 at 8:51 PM, bsilva <bsilva@xxxxxxxxx> wrote:
> What kernel are you using?
>
> I routinely sniff a bond interface using: "tcpdump -i bond0" and it seems
> to behave as expected.
>
> Regards,
> Brad
>
> On Tue, 2 Dec 2008, Omer Faruk Sen wrote:
>
>> Hi,
>>
>> I have a question about linux kernel. I want to have a setup. This
>> setup will have 3 interfaces (eth1,eth2,eth3) i will send traffic to
>> these individual interfaces but I want to see it on just one interface
>> (traffic aggregation) . I have used bond0 and br0 but when I send
>> traffic to eth2 I can't see it on br0 or bond0. How can I achieve this
>> on linux kernel? I can do that on FreeBSD but I must do that on Linux
>>
>> Test setup:
>>
>> br0 -----> eth1,eth2,eth3 or
>>
>> bond0 ----> eth1,eth2,eth3 (used mode 0 and mode 3)
>>
>> If I send traffic on eth2 I CANT sniff it on br0 or bond0 but If I
>> sent traffic (via tcpreplay) to bond0/br0 I can sniff it on ethX.. Is
>> there a facility to achieve that on Linux? I can sniff interfaces
>> individually but this case is not ok for me..
>>
>> Regards.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-net" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html