Command line options

The DIET forwarder executable takes several options to be launched:

• --name: to define the name of the forwarder.
• --peer-name: the name of its peer on the other network.
• --ssh-host: the ssh host for the tunnel creation.
• --ssh-port: the port to use to establish the ssh connection (by default: 22).
• --ssh-login: the login to use to establish the ssh connection (by default: current user login).
• --ssh-key: the private key to use to establish the ssh connection (by default: $HOME/.ssh/id_rsa).
• --remote-port: the port to listen on the ssh host (by default: the remote forwarder tries to dermine an available port automatically, note that if the connection fails when you do not use this option, then you have to specify the remote port).
• --remote-host: the host to which the connection is made by the tunnel (corresponds to host in the ssh options -L and -R).
• --nb-retry: the number of times the local forwarder tries to bind itself to the distant forwarder (default is 3).
• --peer-ior: if you already know the IOR of the distant forwarder, then you can pass it to your local forwarder. By default, the local forwarder retrieves the IOR of its peer.
• --tunnel-wait: the time is seconds that the forwarder will wait while opening the ssh tunnel.
• --net-config|--config: provide the name of a file that contains the configuration options, as an alternative way to configure the dietForwarder. See section 18.2.2 for more details.
• --orb-config: provide the name of the ORB configuration file that contains the necessary information to select the correct IP for publish the objects. If it is not provided, it will do it on all interfaces instead. See section 18.2.2 for more details.

Other options will be ignored by the DIET forwarder executable, but will be forwarded the ommiORB when configuring the forwarder object.

The remote port can be chosen randomly among the available TCP ports on the remote host. Sometimes, depending on the configuration of sshd, you will need to set --remote-host to localhost or 127.0.0.1 (or the address of the local loopback if it is not 127.0.0.1) for the tunnel to work correctly (in fact, most problems come from a badly configured tunnel).

In order, to activate a DIET forwarder, users must:

• Launch omniNames on the remote and local hosts.
• Launch the first peer on the remote host, only defining its name and its network configuration.
• Launch the second peer, passing it it the first peer name, the ssh connection informations, the remote port to use and its network configuration.

Rem: The forwarders must be launched before the DIET hierarchy.