(Illustration by Gaich Muramatsu)
On Wed, May 24, 2000 at 03:22:53AM +0900, Stephen J. Turnbull wrote: > Is there any way to force venus to use the configured server address > to talk to the codasrv? What configured server address? The `rootservers' configuration option only tells venus which machines to ask for volume location information. The volume location database (VLDB), which is used to locate the server that stores a volume, contains one ip-address for a server, the first one returned from gethostbyname(gethostname()). For server to client SFTP transfers, the ipaddress/port are probably sent along with the initial request. In general, what you want is to have your machines listed with one (publicly known) ip-address, and then add static host routes to redirect internal traffic over the VPN. | LAN --+------------+-----------------+-- | 130.158.x.1 | 130.158.x.2 ----------- ----------- | server | | client | ----------- ----------- | 192.168.1.1 | 192.168.1.2 --+------------------------------+-- VPN So, "nslookup client" would return 130.158.x.2, and the server would have an entry in the routing table like this: route add 130.158.x.2 gw 192.168.1.2 Similarily for the client. It is pretty much impossible to have any other way of letting the client know what the preferred route to a server is. JanReceived on 2000-05-23 15:43:53