On Thu, Jan 03, 2002 at 01:18:56PM +0000, Ganesh Sittampalam wrote:
> > Having TCP/IP or not is probably not the problem. If W2K answers ARP > > requests on this interface you're still fscked. > > True. But I'd have thought disabling TCP/IP should disable ARP too. If the > interface was configured, it'd also have a different IP Some OSes (including linux by default, I think) answer ARP requests for local IP addresses even on interfaces that don't carry them. > I've come up with a possible theory for what could be happening, but my > knowledge of precisely how ethernet works is a bit thin. Is it usual for > ethernet cards to echo packets sent by the machine they are in back to > that same machine? No. In fact, it'd be a bug, although a normal stack should be able to deal with it. > If the answer is no, then it could be caused by the > VMWare "bridging" (I'll call it slaving from now on to avoid confusion). > Recall that the external ethernet interface on rocky is actually slaved to > sandy's external ethernet interface. Suppose the slaving decides which > frames to send to rocky by looking at the source MAC address; if it's the > MAC address of the slave device then it doesn't send them, and if it isn't > it does. I don't really see how this would work? Can you elaborate on this a bit? cheers, Lennert _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
