[Top] [All Lists]


To: Andi Kleen <ak@xxxxxxx>
Subject: Re: IFF_PROMISC bug?
From: Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx>
Date: Wed, 13 Feb 2002 03:33:41 -0500
Cc: "David S. Miller" <davem@xxxxxxxxxx>, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, kuznet@xxxxxxxxxxxxx
Organization: MandrakeSoft
References: <3C6A0817.B50EFC74@xxxxxxxxxxxxxxxx> <20020212.223929.66060180.davem@xxxxxxxxxx> <3C6A0F32.DE282B67@xxxxxxxxxxxxxxxx> <20020212.234325.59465194.davem@xxxxxxxxxx> <3C6A1EF5.1BF97B99@xxxxxxxxxxxxxxxx> <20020213090932.A7398@xxxxxxxxxxxxx> <3C6A207F.3590B8ED@xxxxxxxxxxxxxxxx> <20020213092240.A10264@xxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
Andi Kleen wrote:
> Did you use the same tcpdump/libpcap in 2.2 and 2.4 ?


To separate out other bug reports and mentions,
here is my own test environment:

2.2.20 MDK kernel, or
  2.2.21-pre2 custom kernel, or
  2.4.18-preX MDK kernel, or
  2.4.18-preX custom kernel
net-tools 1.60
iproute2 2.2.4
libpcap 0.6.2
tcpdump 3.6.2
glibc 2.2.4 + bug fixes from 2.2.5 (MDK glibc)

So, same userland for 2.2 and 2.4.

When I boot into 2.2 MDK or custom kernel, SIOCGIFFLAGS indicates
IFF_PROMISC when tcpdump is running.
When I boot into 2.4 MDK or custom kernel, SIOCGIFFLAGS does not
indicate IFF_PROMISC under the same conditions.

Thems the facts, gentlemen :)

Jeff Garzik      | "I went through my candy like hot oatmeal
Building 1024    |  through an internally-buttered weasel."
MandrakeSoft     |             -

<Prev in Thread] Current Thread [Next in Thread>