[djf]

Hardware-wise, just one.

But the packet sniffing-routing software on the box I run the vmware stuff could be described as a software router.

Here’s the deal.

The software runs on Box A. Box A has an IP of 192.168.0.70
The virtual software runs also on box A and has an ip of 192.168.0.100

From a dos prompt on box A, I can ping 192.168.0.100
From the virtual machine on box A, I can do a ping 192.168.0.70

So Windows on box A can talk to the virtual machine and the wirtual machine can talk to windows.

But here I come on box B. Box B can ping 192.168.0.70 just fine

But I want box B to know that if he gets a request for 192.168.0.100, to send it to 192.168.0.70, and not just send it to the default gateway, the DSL router, which is 192.168.0.1

[unixfox]

But I want box B to know that if he gets a request for 192.168.0.100, to send it to 192.168.0.70, and not just send it to the default gateway, the DSL router, which is 192.168.0.1

I think you need to set the default gateway on 192.168.0.100 to 192.168.0.70. Then you would give 192.168.0.70 it's gateway to the router.

[Doohickey]

If you want to do that, you’ll need to either split 192.168.0.0/24 into two /28 subnets, or create another /24 for the machines you don’t want using the default gateway.

Sure, you could use the route command and make those routes persistent, but you’re going to hate life when you want to add hosts later on or if you need someone else to make sense of your home network.