Laurent Deniel wrote:
>
> Which operating system ?
Linux.
I noticed the problem with 2.2.11; and I now have it with 2.2.12. Also
happens with the other computer running 2.2.11 or a stock redhat 2.2.5; it has
a
dmesg gives me
eth0: Promiscuous mode enabled.
device eth0 left promiscuous mode
AND I have the same problem with tcpdump ...
I recompiled a kernel with firewalling explicitly disabled in case that was
the problem. I'm not 100% sure it's not ipchains, but I don't recall enabling
any chains (and don't know why that would block promiscuous anyway).
Is it possible that the ethernet hub managing my segment is somehow blocking
the packets since it (could be) a star topology? On the other hand, I don't
think so because I rebooted the 2nd machine to win32 and used an network
associates lan monitor; I couldn't figure out how to examine individual
packets, but it looked like it was seeing the traffic from the first computer
off to the internet ...
I'm about out of ideas, and I would really like to get this sniffer sniffing.
Thanks
>
>
> On some OS, you have to enable the promiscuous mode of the interface to
> be able to see packets that are not destined to (or originated from) the
> machine that do the packet filtering. On Tru64 for instance, this is
> achieve with the pfconfig <dev> +c +p command (see README.tru64).
>
> Laurent.
>
> --
> Laurent DENIEL | E-mail: deniel@xxxxxxxxxxx
> Paris, FRANCE | laurent.deniel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> | WWW : http://www.worldnet.fr/~deniel
> All above opinions are personal, unless stated otherwise.
