Re: [Win4Lin-users] Win4Lin 3.0 Limitations

[Michael L Torrie]

On Tue, 29 May 2001, David Peet wrote:

> Someone else asked about support for non-IP networks --
> The VNET code routes packets from the real ethernet to the VNET
> based on looking at the packet.  So it needs to understand the
> protocol to know how to route it.  Currently this router code only
> knows about IP (plus a bit of DHCP awareness).

Couldn't win4lin just put the ethernet adapter in promiscuous mode (like
vmware does) and pass all ethernet traffic through to the VNET interface,
regardless of protocol or routing information?  This seems like the best
way to go.

cheers,
Michael


_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users