On Thu, Jan 10, 2002 at 06:36:58PM +0000, Ganesh Sittampalam wrote: > > > 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? > > The slaving needs to present the illusion to the VM (rocky in this case) > of a real ethernet device. Therefore, it needs to send it everything on > the ethernet including frames originating with sandy, but not including > those originating with rocky. One way it might do this is to consider > every frame any device, internal (rocky/sandy) or external, sends. Then, > all it would do is to filter out any frame that has rocky's source MAC > address from those it sends to rocky, and similarly for sandy.
Ah, ok, that makes sense now. Well, I think the source to their linux kernel module is available, so you could check that out to see whether this is what they are actually doing. cheers, Lennert _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
