ifconfig alias route

[motoslide]

A Client has a SCO 5.0.7 system with a primary IP of 192.168.0.240, and an alias of 192.168.2.240. They have remote offices and are in the process of changing network carriers.
The SCO system is in Office-A. It's primary subnet is 192.168.0.XXX
Office-B has a subnet of 192.168.1.XXX
Office-C has a subnet of 192.168.3.XXX
The "old" circuit between Office-A and Office-C used the 192.168.2.XXX subnet in Office-A.

This is ugly, but basically working except for some devices in Office-C. Specifically, a couple of HP LJ's with JetDirects. When I send a print job, I see this connection:

# netstat -an|grep 9100
tcp        0      0  192.168.0.240.1080     192.168.3.200.9100     SYN_SENT

This is the route table:
# netstat -rn
Routing tables
Destination      Gateway            Flags    Refs      Use  Interface
default          192.168.0.1        UGS         3        3  net0
127.0.0.1        127.0.0.1          UH          3      307  lo0
192.168          192.168.0.240      UC          1        0  net0
192.168.0.240    127.0.0.1          UGHS        4       29  lo0
192.168.2        192.168.2.240      UC          1        0  net0
192.168.2.240    127.0.0.1          UGHS        0        0  lo0
192.168.3        192.168.2.1        UGS         0       22  net0
192.168.3.200    192.168.2.1        UGHS        1        4  net0
224              192.168.0.240      UCS         0        0  net0

The entry starting with 192.168.3.200 is just an attempt to create a 1-to-1 route to that specific printer.

As you can see, the HPNP process is trying to hit Office-C on the primary subnet instead of the alias.

Any ideas out there?

 

[PHV]

What is the Gateway value in the 192.168.3.200 JetDirect TCP/IP config ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[motoslide]

It has a valid gateway of 192.168.3.1. PC's on that subnet are able to establish telnet connections to the UNIX box (on it's alias of 192.168.2.240). This appears to be a problem with the SCO system not knowing how to look a the route table to establish outbound connections. As the netstat -an results show, the connection endpoint is on the 192.168.0.240 IP, which has no physical route to the 192.168.3.xxx network.

We just flipped the Primary/Alias IP's on the SCO box to resolve a problem in Office-B. I'm hoping to find a solution which will allow the "alias" to function as if it were truly a second NIC. Adding an additional NIC would probably solve the issue, but the machine is not local to me.

 

[PHV]

Can't 192.168.0.1 and 192.168.2.1 use RIP ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[motoslide]

I'm not familiar with the configuration/management of RIP. Is there a sample gated.conf somewhere?

This particular SCO system only needs to communicate with local devices and those two remote offices. It has no need for general Internet access for Mail, Web, FTP, etc.

Thanks much for the help. This one's a time-sensitive issue.