Remote Daemon
In most cases, programs use a local daemon, running on the same host as the program. Certain situations require a remote daemon, for example:
| • | The program runs on a laptop computer that is not directly connected to the network. Instead, the laptop connects to a workstation on the network, and the daemon runs on that workstation. |
| • | The program connects to a network at a remote site. |
For remote daemons, specify two parts (introducing the remote host name as the first part):
| • | Remote host name. |
| • | TCP socket number. |
For example: "purple_host:6555".
Once again the communication type and socket number in the daemon parameter of the transport creation call must match those given to rvd through its -listen parameter. However, the -listen parameter still receives only a two-part argument—without a remote host name.
When a client specifies a remote daemon that is not present, the client does not auto-start a daemon in that remote location.
|
Note |
For a general overview, see Direct Communication on page 91 in . |
Barring Remote Connections
A Rendezvous daemon or routing daemon can prohibit connections from remote programs by specifying -listen "127.0.0.1". The special network address 127.0.0.1 represents the local host, so this parameter specifies that only local programs may connect.
This configuration is especially important when a routing daemon runs on a firewall computer.