Quoting Ian C. Sison ([EMAIL PROTECTED]): > Really? I don't get that behaviour on my box... Maybe some sort of > setting on the emulated ethernet?
Searching Google finds pages like this, that may cast some light on the matter: http://www.komacke.com/archive/rl2-library/2000-07/0026.html "Perhaps this has to do with the fact that VMware kicks the card into promiscuous mode, as you mentioned...." http://www.securiteam.com/tools/5UP0E206VC.html "Q: My adapter is in promiscuous mode but there is no sniffer in my computer. What is wrong? A: For example, VMWare puts your adapter in promiscuous mode even if you are not running a sniffer." http://online.securityfocus.com/archive/101/212127/2001-08-29/2001-09-04/0 "BUT as far as I know, vmware does not support bridging on wireless interfaces. Bridging on the wireless interface means putting it into promiscuous mode or "monitor" mode...." https://listman.redhat.com/pipermail/enigma-list/2001-November/002784.html "Another culprit, quite often is VMWare. It prefers PROMISC depending on how you set it up." So, it seems a fair bet that, as the last snippet suggests, it depends on VMware's configuration. I haven't run the thing for a couple of years, and so am not in a position to experiment and find out. _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
