1DIETFORWARDER(1)                                              DIETFORWARDER(1)
2
3
4

NAME

6       dietForwarder - DIET tool to manage ssh tunnels between DIET components
7

NAME

9       dietForwarder  - Tool for creating DIET forwarders. Forwarders are spe‐
10       cial components that serve as proxies and manage  ssh  tunnels  between
11       DIET components in complex networks.
12

SYNOPSYS

14          dietForwarder [options] ...
15

DESCRIPTION

17       Deploying  DIET  on  heterogeneous  networks  that are not reachable by
18       means other than ssh tunnels is a delicate task.  DIET  forwarders  are
19       special  DIET  components that serve as proxies between DIET components
20       by creating ssh tunnels.
21
22       dietForwarder is a command to instantiate DIET forwarders.   Forwarders
23       simplify  the  maintenance of ssh tunnels between DIET components, thus
24       improving DIET's scalability and ease of configuration in complex  net‐
25       work topologies.
26
27       Before starting a DIET forwarder, you must:
28
29       · launch omniNames on the local and remote hosts;
30
31       · launch the remote peer, specifying its name and network configuration
32         only;
33
34       · launch the local peer and give it the remote  peer's  name,  the  ssh
35         connection's details, the remote port to use and the 'pass -C' option
36         to create the ssh tunnel.
37
38       [Remark: forwarders must be launched before the DIET hierarchy.]
39

OPTIONS

41       --name [name]
42              String identifying the forwarder.
43
44       --peer-name [name]
45              String identifying its peer on the other network.
46
47       --ssh-host [host]
48              Host hosting the ssh tunnel.
49
50       --ssh-login [login]
51              Login used to establish the  ssh  connection  (default:  current
52              user login).
53
54       --ssh-key [/path/to/ssh/key]
55              Path to the ssh key (the private one!) used to establish the ssh
56              connection (default: $HOME/.ssh/id_rsa).
57
58       --remote-port [port]
59              Port the ssh host is listening on.
60
61       --remote-host [host]
62              Host to which the connection is made by the tunnel  (corresponds
63              to ssh options -L and -R).
64
65       --nb-retry [nb]
66              Number of times that the local forwarder will try to bind itself
67              to the remote forwarder (default: 3).
68
69       --peer-ior [IOR]
70              Passes the remote forwarder's IOR. By default,  the  local  for‐
71              warder will retrieve its peer's IOR.
72
73       --tunnel-wait [seconds]
74              Set  the  number  of seconds to wait before considering that the
75              tunnel has been created.
76

EXAMPLE

78       Here is a simple configuration example:
79
80       · We have two domains: net1 and net2. Forwarders will  be  launched  on
81         hosts fwd.net1 and fwd.net2.
82
83       · There's  no  link  between  hosts fwd.net1 and fwd.net2 but users may
84         access fwd.net2 from fwd.net1 using a ssh connection.
85
86       · Let's call the fwd.net1 forwarder Fwd1  and  the  fwd.net2  forwarder
87         Fwd2.
88
89       · One  SeD lives in fwd.net2 while the rest of the DIET hierarchy lives
90         on the net1 domain.
91
92       Command line for launching Fwd1
93
94          fwd.net1$ dietForwarder --name Fwd1 --peer-name Fwd2 \
95            --ssh-host fwd.net2 --ssh-login dietUser \
96            --ssh-key id rsa net2 --remote-port 50000
97
98       Command line to launch Fwd2
99
100          fwd.net2$ dietForwarder --name Fwd2
101

RATIONALE

103       DIET uses CORBA as its communication layer. While it is a flexible  and
104       robust middleware, it remains hard to deploy DIET on heterogeneous net‐
105       works that are not reachable except  through  ssh  tunnels.  DIET  for‐
106       warders help the administrator to configure their grid without manually
107       setting-up ssh tunnels, which is arguably neither simple nor  scalable.
108       DIET  forwarders  make  it  very  easy  to configure networks with such
109       topologies.
110
112   Copyright
113       (C)2011, GRAAL, INRIA Rhone-Alpes, 46 allee d'Italie, 69364 Lyon  cedex
114       07, France all right reserved <diet-dev@ens-lyon.fr>
115
116   License
117       This  program  is  free software: you can redistribute it and/or mod‐
118       ify it under the terms of the GNU  General  Public  License  as  pub‐
119       lished  by  the  Free  Software  Foundation,  either  version  3 of the
120       License, or (at your option) any later version. This  program  is  dis‐
121       tributed  in the hope that it will be useful, but WITHOUT ANY WARRANTY;
122       without even the implied warranty of MERCHANTABILITY or FITNESS  FOR  A
123       PARTICULAR  PURPOSE.  See  the  GNU  General  Public  License  for more
124       details. You should have received a copy  of  the  GNU  General  Public
125       License    along    with    this    program.    If    not,    see    <‐
126       http://www.gnu.org/licenses/>.
127

AUTHORS

129       GRAAL INRIA Rhone-Alpes 46 allee d'Italie 69364 Lyon cedex  07,  FRANCE
130       Email: <diet-dev@ens-lyon.fr> WWW: http://graal.ens-lyon.fr/DIET
131

SEE ALSO

133       omniNames(1), DIETAgent(1)
134

BUGS

136       On  some  systems,  forwarder  rules  will  not  work unless you use IP
137       addresses instead of hostnames.
138

AUTHOR

140       haikel.guemar@sysfera.com
141
142       License: CeCILL
143
145       DIET developers
146
147
148
149
1500.1                               2011-01-10                  DIETFORWARDER(1)
Impressum