My question was answered on a different forum, so I would like to make the solution available here in case anyone else has a similar setup.
Code:
/---*queue-master*
| exporting /export/home directories
| dhcp/NAT server for slave-net
| \
| \
| \
| \--{slave-net}
| ||| |
| ||| |
| *slave0* ---/|| |
| *slave1* ----/| |
| . -----/ |
| . |
| . |
| *slave-special* --/
| exporting /export/large-dir
| |
| |
\---[workstation-subnet]
\ \ \
| | |
*workstation0*
*workstation1*
....
I have *slave-special* exporting /data/large-dir to the world (*) at the moment. *queue-master* is a NAT routing dhcp server for all the slaves.
both *slave-special* and *queue-master* have an IP for the {slave-net} (192.168.0.X) and an IP for the [workstation-subnet] (IP via NIS/DNS).
Notice that there are two routes the slaves can take to talk to the slave-special. It could talk direct via the slave-net but it can also go through the NAT router in queue-master and the workstation-subnet. It seems to prefer the latter but I don't want to tie up unnecessary resources like that.
What I wish to accomplish:
I would like two directories (home and large-dir) to be seen by both slaves and workstations. Furthermore, when any computer looks at the home directories, they talk directly to queue-master; when any computer looks at the large-dir, they talk directly to slave-special. The home directory is not a problem because it is on the dhcp/NAT server (queue-master). The large-dir on the other hand seems to only export on a specific subnet (the workstation subnet).
With the setup as described prior, I originally thought I would only have to specify the routes to the various IPs for the slave-special (serving the large-dir). But I also had to specify the IP address of slave-special on the other slaves as they got the IP for slave-special through DNS/NIS on the workstation-subnet and thus had to go through the workstation-subnet.
SOLUTION: I merely listed all the slaves' IPs in slave-special's /etc/hosts file. And I then put slave-special's slave-subnet IP (192.168.0.X) in slave-special's /etc/hosts file which will superceed the NIS/DNS IP the slaves would normally get.
Thus the routing from slave-special to the slaves is on the slave-subnet and the routing to everything else is done through the NIS (workstation subnet).
Thanks for your help!
Johann
