Robert Latest: > > What I can't figure out is how to separate the IP address spaces in > this PC itself. There are plenty of 192.168 addresses in use in our > intranet, and it is quite possible that addresses will be used both in > the Intranet and in the Modbus space.
That is a broken network design.
> Suppose the application wants to talk to the Modbus device
> 192.168.0.101 on eth1 (where the Modbus devices are connected). How
> can I prevent it from connecting to a host on the intranet that
> happens to have the same address?
You can't, except when using static host routes for each intranet host
you want to connect to.
> Actually, I know that the hosts that I need to connect to on the
> intranet do not have 192.168.... addresses. So I suppose I can set up
> the routing table using a network mask or something of the sort.
That's the way to go if you can find a netmask that fits your needs.
J.
--
It is not in my power to change anything.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>
signature.asc
Description: Digital signature
