A question for the vmware gurus out there

[Roger Oberholtzer]

I am not sure how best to explain this, so I will just jump in:

I have a Linux box with an Ethernet interface that has various aliases:

3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:a0:00:00:19:4a brd ff:ff:ff:ff:ff:ff
    inet 10.2.10.41/28 brd 10.2.10.47 scope global eth1
    inet 192.168.0.41/24 brd 192.168.0.255 scope global eth1:ranger
    inet 10.1.5.41/24 brd 10.1.5.255 scope global eth1:ANTS
    inet 10.1.6.41/24 brd 10.1.6.255 scope global eth1:vlan
    inet6 fe80::2a0:ff:fe00:194a/64 scope link
       valid_lft forever preferred_lft forever

This is a 'catch all' network for attaching various network-based
measurement transducers, like lasers, accelerometers or 3D cameras.
Often the addresses of these devices are difficult to change. Using an
alias lets me access it without having to reconfigure the device. At
least this is the case from our Linux applications. No problems.

I have some software (came with a device) that I need to run on Windows.
I have installed this in vmware/WindowsXP. The problem is that it (the
app or vmware) does not seem to see the things on this network.
Specifically, I am trying to access this alias on that network:

inet 192.168.0.41/24 brd 192.168.0.255 scope global eth1:ranger

I do not think vmware has set up any logic to ship things for
192.169.0.255 on eth1. I have the default vmware setup, which is:

4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
    inet 172.16.94.1/24 brd 172.16.94.255 scope global vmnet1
    inet6 fe80::250:56ff:fec0:1/64 scope link
       valid_lft forever preferred_lft forever
5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
    inet 192.168.220.1/24 brd 192.168.220.255 scope global vmnet8
    inet6 fe80::250:56ff:fec0:8/64 scope link
       valid_lft forever preferred_lft forever

Generally, the network in vmware/Windows is working. I can ping things
on 10.2.10.x on eth1 from linux or vmware/windows. I can ping things on
192.168.0.x from Linux, but not from vmware. And that is my problem.

I am not even sure where to start with vmware to get packets for
190.168.0.x to go to eth1. Anyone have any ideas? 


-- 
Roger Oberholtzer

OPQ Systems / Ramböll RST

Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden

Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696