I've got one network card in a box with a primary address W.X.Y.Z/24 and an alias that 
connects
to all of the natted machines of 192.168.A.B/24. While this is not ideal, the DSL 
modem will not
route 192.168 addresses and my switches will not send packets to it from the 192.168 
machines,
at least I think they won't, as they are supposed to recognize MAC addresses and only 
send stuff
where it needs to go. Anyway, I tried stopping the VNET server, removing the alias 
eth0:0 , restarting
the VNET server, then putting it back. The VNET IP is in the 192.168 network. It does 
not work.
Windows under W4L cannot even ping the gateway, either the W.X.Y.Z ip, or the 
192.168.A.B ip.
After considering this, I think that it cannot work, as VNET can only talk to the main 
IP, which
will not talk to a 192.168 network. Is this correct? Any way to set up routing for 
this to work as
a special case? Otherwise, I have to wait for either the problem to be fixed, or 
install another
ethernet card, which I currently don't have a slot for. Any suggestions?



Mark Goldberg
[EMAIL PROTECTED]
(finger [EMAIL PROTECTED] for PGP public key)


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

Reply via email to