Vnet works by providing a "virtual ethernet device", i.e. a "NIC".
It has a "normal" Windows ethernet driver, and the normal WIndows
TCP/IP stack is used. So a program that inserts stuff
into the stack should work.
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).
So only IP based networking is currently supported.
Supporting other network protocols will need protocol specific router
code in VNET.
E.g. for IPX, the router code in VNET would have to have to recognize
and parse IPX packets to know if the package is intended for the VNET
or for LINUX. So, IPX is not currently supported.
-David
Dan Swartzendruber wrote:
>
> At 02:46 PM 5/29/2001 -0400, Amanda Owens wrote:
> >Actually, VNET in Win4Lin 3.0 only supports Windows TCP/IP. It has no
> >capabilities to do NetBEUI or IPX/SPX networking.
>
> How does VNET work? Is it a real NIC (virtually speaking)? I ask this
> because I am forced to
> use a telecommuting package (secureremot) which shims itself between
> windows TCP/IP and
> the ethernet driver. If VNET will do this, I'm golden (and I can ditch
> vmware).
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
