net-ssh 1.1.2 → 1.1.3
Sign up to get free protection for your applications and to get access to all the features.
- data/ChangeLog +15 -0
- data/NEWS +3 -0
- data/bin/rb-keygen +0 -0
- data/lib/net/ssh/transport/packet-stream.rb +20 -7
- data/lib/net/ssh/version.rb +1 -1
- data/test/transport/tc_packet_stream.rb +1 -0
- metadata +49 -54
- data/doc/manual-html/chapter-1.html +0 -388
- data/doc/manual-html/chapter-2.html +0 -552
- data/doc/manual-html/chapter-3.html +0 -470
- data/doc/manual-html/chapter-4.html +0 -413
- data/doc/manual-html/chapter-5.html +0 -525
- data/doc/manual-html/chapter-6.html +0 -456
- data/doc/manual-html/chapter-7.html +0 -343
- data/doc/manual-html/index.html +0 -235
- data/doc/manual-html/stylesheets/manual.css +0 -270
- data/doc/manual-html/stylesheets/ruby.css +0 -17
|
@@ -1,456 +0,0 @@
|
|
|
1
|
-
<html>
|
|
2
|
-
<head>
|
|
3
|
-
<title>Net::SSH Manual :: Chapter 6: Port Forwarding</title>
|
|
4
|
-
<link type="text/css" rel="stylesheet" href="stylesheets/manual.css" />
|
|
5
|
-
</head>
|
|
6
|
-
|
|
7
|
-
<body>
|
|
8
|
-
<div id="banner">
|
|
9
|
-
<table border='0' cellpadding='0' cellspacing='0' width='100%'>
|
|
10
|
-
<tr><td valign='top' align='left'>
|
|
11
|
-
<div class="title">
|
|
12
|
-
<span class="product">Net::SSH—</span><br />
|
|
13
|
-
<span class="tagline">Secure Shell for Ruby</span>
|
|
14
|
-
</div>
|
|
15
|
-
</td><td valign='middle' align='right'>
|
|
16
|
-
<div class="info">
|
|
17
|
-
Net::SSH Version: <strong>1.1.2</strong><br />
|
|
18
|
-
Manual Last Updated: <strong>2007-06-18 18:12 UTC</strong>
|
|
19
|
-
</div>
|
|
20
|
-
</td></tr>
|
|
21
|
-
</table>
|
|
22
|
-
</div>
|
|
23
|
-
|
|
24
|
-
<table border='0' width='100%' cellpadding='0' cellspacing='0'>
|
|
25
|
-
<tr><td valign='top'>
|
|
26
|
-
|
|
27
|
-
<div id="navigation">
|
|
28
|
-
<h1>Net::SSH Manual</h1>
|
|
29
|
-
|
|
30
|
-
<h2>Chapters</h2>
|
|
31
|
-
<ol type="I">
|
|
32
|
-
|
|
33
|
-
<li>
|
|
34
|
-
<a href="chapter-1.html">
|
|
35
|
-
Introduction
|
|
36
|
-
</a>
|
|
37
|
-
|
|
38
|
-
<ol type="1">
|
|
39
|
-
|
|
40
|
-
<li><a href="chapter-1.html#s1">What is Net::SSH?</a></li>
|
|
41
|
-
|
|
42
|
-
<li><a href="chapter-1.html#s2">What isn’t Net::SSH?</a></li>
|
|
43
|
-
|
|
44
|
-
<li><a href="chapter-1.html#s3">Getting Net::SSH</a></li>
|
|
45
|
-
|
|
46
|
-
<li><a href="chapter-1.html#s4">License Information</a></li>
|
|
47
|
-
|
|
48
|
-
<li><a href="chapter-1.html#s5">Support</a></li>
|
|
49
|
-
|
|
50
|
-
<li><a href="chapter-1.html#s6">About the Author</a></li>
|
|
51
|
-
|
|
52
|
-
</ol>
|
|
53
|
-
</li>
|
|
54
|
-
|
|
55
|
-
<li>
|
|
56
|
-
<a href="chapter-2.html">
|
|
57
|
-
Starting a Session
|
|
58
|
-
</a>
|
|
59
|
-
|
|
60
|
-
<ol type="1">
|
|
61
|
-
|
|
62
|
-
<li><a href="chapter-2.html#s1">Using Net::SSH.start</a></li>
|
|
63
|
-
|
|
64
|
-
<li><a href="chapter-2.html#s2">Using a Public/Private Key</a></li>
|
|
65
|
-
|
|
66
|
-
<li><a href="chapter-2.html#s3">Options</a></li>
|
|
67
|
-
|
|
68
|
-
<li><a href="chapter-2.html#s4">Using Net::SSH::Session</a></li>
|
|
69
|
-
|
|
70
|
-
</ol>
|
|
71
|
-
</li>
|
|
72
|
-
|
|
73
|
-
<li>
|
|
74
|
-
<a href="chapter-3.html">
|
|
75
|
-
Channels
|
|
76
|
-
</a>
|
|
77
|
-
|
|
78
|
-
<ol type="1">
|
|
79
|
-
|
|
80
|
-
<li><a href="chapter-3.html#s1">What are Channels?</a></li>
|
|
81
|
-
|
|
82
|
-
<li><a href="chapter-3.html#s2">Session.loop</a></li>
|
|
83
|
-
|
|
84
|
-
<li><a href="chapter-3.html#s3">Channel Types</a></li>
|
|
85
|
-
|
|
86
|
-
<li><a href="chapter-3.html#s4">Opening a Channel</a></li>
|
|
87
|
-
|
|
88
|
-
<li><a href="chapter-3.html#s5">Callbacks</a></li>
|
|
89
|
-
|
|
90
|
-
<li><a href="chapter-3.html#s6">Channel Operations</a></li>
|
|
91
|
-
|
|
92
|
-
</ol>
|
|
93
|
-
</li>
|
|
94
|
-
|
|
95
|
-
<li>
|
|
96
|
-
<a href="chapter-4.html">
|
|
97
|
-
Executing Commands
|
|
98
|
-
</a>
|
|
99
|
-
|
|
100
|
-
<ol type="1">
|
|
101
|
-
|
|
102
|
-
<li><a href="chapter-4.html#s1">Using Channels</a></li>
|
|
103
|
-
|
|
104
|
-
<li><a href="chapter-4.html#s2">Using #process.open</a></li>
|
|
105
|
-
|
|
106
|
-
<li><a href="chapter-4.html#s3">Using #process.popen3</a></li>
|
|
107
|
-
|
|
108
|
-
</ol>
|
|
109
|
-
</li>
|
|
110
|
-
|
|
111
|
-
<li>
|
|
112
|
-
<a href="chapter-5.html">
|
|
113
|
-
User Shells
|
|
114
|
-
</a>
|
|
115
|
-
|
|
116
|
-
<ol type="1">
|
|
117
|
-
|
|
118
|
-
<li><a href="chapter-5.html#s1">Introduction</a></li>
|
|
119
|
-
|
|
120
|
-
<li><a href="chapter-5.html#s2">Using Channels</a></li>
|
|
121
|
-
|
|
122
|
-
<li><a href="chapter-5.html#s3">Shell Service</a></li>
|
|
123
|
-
|
|
124
|
-
<li><a href="chapter-5.html#s4">SyncShell Service</a></li>
|
|
125
|
-
|
|
126
|
-
<li><a href="chapter-5.html#s5">Terminal Clients</a></li>
|
|
127
|
-
|
|
128
|
-
</ol>
|
|
129
|
-
</li>
|
|
130
|
-
|
|
131
|
-
<li><strong>
|
|
132
|
-
<a href="chapter-6.html">
|
|
133
|
-
Port Forwarding
|
|
134
|
-
</a>
|
|
135
|
-
</strong> <big>←</big>
|
|
136
|
-
<ol type="1">
|
|
137
|
-
|
|
138
|
-
<li><a href="chapter-6.html#s1">Introduction</a></li>
|
|
139
|
-
|
|
140
|
-
<li><a href="chapter-6.html#s2">Local-to-Remote</a></li>
|
|
141
|
-
|
|
142
|
-
<li><a href="chapter-6.html#s3">Remote-to-Local</a></li>
|
|
143
|
-
|
|
144
|
-
<li><a href="chapter-6.html#s4">Direct Channels</a></li>
|
|
145
|
-
|
|
146
|
-
<li><a href="chapter-6.html#s5">Remote-to-Local Handlers</a></li>
|
|
147
|
-
|
|
148
|
-
</ol>
|
|
149
|
-
</li>
|
|
150
|
-
|
|
151
|
-
<li>
|
|
152
|
-
<a href="chapter-7.html">
|
|
153
|
-
Using Proxies
|
|
154
|
-
</a>
|
|
155
|
-
|
|
156
|
-
<ol type="1">
|
|
157
|
-
|
|
158
|
-
<li><a href="chapter-7.html#s1">Introduction</a></li>
|
|
159
|
-
|
|
160
|
-
<li><a href="chapter-7.html#s2"><span class="caps">HTTP</span></a></li>
|
|
161
|
-
|
|
162
|
-
<li><a href="chapter-7.html#s3"><span class="caps">SOCKS</span></a></li>
|
|
163
|
-
|
|
164
|
-
</ol>
|
|
165
|
-
</li>
|
|
166
|
-
|
|
167
|
-
</ol>
|
|
168
|
-
|
|
169
|
-
<h2>Other Documentation</h2>
|
|
170
|
-
|
|
171
|
-
<ul>
|
|
172
|
-
<li><a href="http://net-ssh.rubyforge.org/api/index.html">Net::SSH API</a></li>
|
|
173
|
-
<li><a href="http://rubyforge.org/tracker/?atid=1842&group_id=274&func=browse">Net::SSH FAQ</a></li>
|
|
174
|
-
</ul>
|
|
175
|
-
|
|
176
|
-
<h2>Tutorials</h2>
|
|
177
|
-
<ol>
|
|
178
|
-
|
|
179
|
-
</ol>
|
|
180
|
-
|
|
181
|
-
<p align="center"><strong>More To Come...</strong></p>
|
|
182
|
-
|
|
183
|
-
<div class="license">
|
|
184
|
-
<a href="http://creativecommons.org/licenses/by-sa/2.0/"><img alt="Creative Commons License" border="0" src="http://creativecommons.org/images/public/somerights" /></a><br />
|
|
185
|
-
This manual is licensed under a <a href="http://creativecommons.org/licenses/by-sa/2.0/">Creative Commons License</a>.
|
|
186
|
-
</div>
|
|
187
|
-
</div>
|
|
188
|
-
|
|
189
|
-
</td><td valign='top' width="100%">
|
|
190
|
-
|
|
191
|
-
<div id="content">
|
|
192
|
-
|
|
193
|
-
<div class="top"><div class="prevnext">
|
|
194
|
-
|
|
195
|
-
<a href="chapter-5.html">Previous (5. User Shells)</a> |
|
|
196
|
-
|
|
197
|
-
<a href="index.html">Up</a>
|
|
198
|
-
|
|
199
|
-
| <a href="chapter-7.html">Next (7. Using Proxies)</a>
|
|
200
|
-
|
|
201
|
-
</div></div>
|
|
202
|
-
|
|
203
|
-
<h1>6. Port Forwarding</h1>
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
<h2>
|
|
208
|
-
<a name="s1"></a>
|
|
209
|
-
6.1. Introduction
|
|
210
|
-
</h2>
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
<div class="section">
|
|
215
|
-
<p>Port forwarding is a feature of the <span class="caps">SSH</span> protocol that allows you to specify a port on one of the hosts, and have network connections on that port forwarded to a port on a different host, using the <span class="caps">SSH</span> connection as a proxy. There are basically two ways to use this forwarding:</p>
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
<ol>
|
|
219
|
-
<li>A port on the local host is forwarded via the remote host to another machine. Any connection to the specified port will cause all subsequent data to be sent over the connection to the remote host, where it will then be forwarded to the requested destination host.</li>
|
|
220
|
-
<li>A port on the remote host is forwarded over the connection to the local host, and from there to (potentially) some other remote destination. Any connection to the specified port on the remote host is forwarded over the connection to the local host, which then makes a connection to the specified remote destination and sends the data there.</li>
|
|
221
|
-
</ol>
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
<p>All port forwarding in the Net::SSH library is managed by the <code>#forward</code> service. Just invoke methods on that service to set up any of various port forwarding configurations.</p>
|
|
225
|
-
|
|
226
|
-
|
|
227
|
-
<div class='figure'>
|
|
228
|
-
<span class='caption'>Accessing the #forward service [ruby]</span>
|
|
229
|
-
<div class='body'><table border='0' cellpadding='0' cellspacing='0'><tr><td class='lineno'>1<br />2<br />3<br />4<br />5<br /></td><td width='100%'><link rel='stylesheet' type='text/css' href='stylesheets/ruby.css' /><div class='ruby'><pre><span class="constant">Net</span><span class="punct">::</span><span class="constant">SSH</span><span class="punct">.</span><span class="ident">start</span><span class="punct">(</span> <span class="punct">'</span><span class="string">host</span><span class="punct">'</span> <span class="punct">)</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">session</span><span class="punct">|</span>
|
|
230
|
-
<span class="ident">forward</span> <span class="punct">=</span> <span class="ident">session</span><span class="punct">.</span><span class="ident">forward</span>
|
|
231
|
-
<span class="punct">...</span>
|
|
232
|
-
<span class="ident">session</span><span class="punct">.</span><span class="ident">loop</span>
|
|
233
|
-
<span class="keyword">end</span></pre></div></td></tr></table></div></div>
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
<p>You can define any number of forwards before invoking the main loop, in which case all of those forwards will be handled transparently (and silently) in parallel, over the same connection. (Isn’t <span class="caps">SSH</span> lovely?)</p>
|
|
237
|
-
|
|
238
|
-
|
|
239
|
-
<p>Naturally, you can also have remote processes, <span class="caps">SFTP</span> sessions, and more all working at the same time on the connection.</p>
|
|
240
|
-
</div>
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
<h2>
|
|
245
|
-
<a name="s2"></a>
|
|
246
|
-
6.2. Local-to-Remote
|
|
247
|
-
</h2>
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
|
|
251
|
-
<div class="section">
|
|
252
|
-
<p>Forwarding a local connection to a remote destination is simply a matter of invoking the <code>#local</code> method of the <code>#forward</code> service. The simplest version of the method just takes three parameters: the local port to listen on, and the remote host and port to forward the connection to:</p>
|
|
253
|
-
|
|
254
|
-
|
|
255
|
-
<div class='figure'>
|
|
256
|
-
<span class='caption'>Forwarding a local port [ruby]</span>
|
|
257
|
-
<div class='body'><table border='0' cellpadding='0' cellspacing='0'><tr><td class='lineno'>1<br />2<br />3<br />4<br /></td><td width='100%'><link rel='stylesheet' type='text/css' href='stylesheets/ruby.css' /><div class='ruby'><pre><span class="constant">Net</span><span class="punct">::</span><span class="constant">SSH</span><span class="punct">.</span><span class="ident">start</span><span class="punct">(</span> <span class="punct">'</span><span class="string">host</span><span class="punct">'</span> <span class="punct">)</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">session</span><span class="punct">|</span>
|
|
258
|
-
<span class="ident">session</span><span class="punct">.</span><span class="ident">forward</span><span class="punct">.</span><span class="ident">local</span><span class="punct">(</span> <span class="number">1234</span><span class="punct">,</span> <span class="punct">'</span><span class="string">www.google.com</span><span class="punct">',</span> <span class="number">80</span> <span class="punct">)</span>
|
|
259
|
-
<span class="ident">session</span><span class="punct">.</span><span class="ident">loop</span>
|
|
260
|
-
<span class="keyword">end</span></pre></div></td></tr></table></div></div>
|
|
261
|
-
|
|
262
|
-
|
|
263
|
-
<p>In the above example, then, any connection received on port 1234 will be forwarded to port 80 on “www.google.com”. This means that if you were to point a browser at “http://localhost:1234”, it would pull up <a href="http://www.google.com">Google</a>.</p>
|
|
264
|
-
|
|
265
|
-
|
|
266
|
-
<p>By default, only connections <em>from the local host</em> are accepted. This is because the default bind address is 127.0.0.1. You can specify any bind address you want (including 0.0.0.0 to allow connections from anywhere) by specifying that address as the first parameter to <code>#local</code>, with the local port number immediately following.</p>
|
|
267
|
-
|
|
268
|
-
|
|
269
|
-
<div class='figure'>
|
|
270
|
-
<span class='caption'>Specifying the bind address when forwarding a local port [ruby]</span>
|
|
271
|
-
<div class='body'><link rel='stylesheet' type='text/css' href='stylesheets/ruby.css' /><div class='ruby'><pre><span class="ident">session</span><span class="punct">.</span><span class="ident">forward</span><span class="punct">.</span><span class="ident">local</span><span class="punct">(</span> <span class="punct">'</span><span class="string">0.0.0.0</span><span class="punct">',</span> <span class="number">1234</span><span class="punct">,</span> <span class="punct">'</span><span class="string">www.google.com</span><span class="punct">',</span> <span class="number">80</span> <span class="punct">)</span></pre></div></div></div>
|
|
272
|
-
|
|
273
|
-
|
|
274
|
-
<p>In this configuration, anyone from anywhere can connect to your machine on port 1234 and be forwarded to Google.</p>
|
|
275
|
-
</div>
|
|
276
|
-
|
|
277
|
-
|
|
278
|
-
|
|
279
|
-
<h2>
|
|
280
|
-
<a name="s3"></a>
|
|
281
|
-
6.3. Remote-to-Local
|
|
282
|
-
</h2>
|
|
283
|
-
|
|
284
|
-
|
|
285
|
-
|
|
286
|
-
<div class="section">
|
|
287
|
-
<p>Forwarding remote connections to the local host is also straightforward; simply call the <code>#remote_to</code> method of the <code>#forward</code> service. This takes three (or four) parameters: the local port and host to be forwarded to (in that order), and the remote port to listen on. The fourth parameter is optional, and is the bind address on the remote machine; this defaults to “127.0.0.1”.</p>
|
|
288
|
-
|
|
289
|
-
|
|
290
|
-
<div class='figure'>
|
|
291
|
-
<span class='caption'>Forwarding a remote port [ruby]</span>
|
|
292
|
-
<div class='body'><table border='0' cellpadding='0' cellspacing='0'><tr><td class='lineno'>1<br />2<br />3<br />4<br /></td><td width='100%'><link rel='stylesheet' type='text/css' href='stylesheets/ruby.css' /><div class='ruby'><pre><span class="constant">Net</span><span class="punct">::</span><span class="constant">SSH</span><span class="punct">.</span><span class="ident">start</span><span class="punct">(</span> <span class="punct">'</span><span class="string">host</span><span class="punct">'</span> <span class="punct">)</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">session</span><span class="punct">|</span>
|
|
293
|
-
<span class="ident">session</span><span class="punct">.</span><span class="ident">forward</span><span class="punct">.</span><span class="ident">remote_to</span><span class="punct">(</span> <span class="number">80</span><span class="punct">,</span> <span class="punct">'</span><span class="string">www.google.com</span><span class="punct">',</span> <span class="number">1234</span> <span class="punct">)</span>
|
|
294
|
-
<span class="ident">session</span><span class="punct">.</span><span class="ident">loop</span>
|
|
295
|
-
<span class="keyword">end</span></pre></div></td></tr></table></div></div>
|
|
296
|
-
|
|
297
|
-
|
|
298
|
-
<p>The above example causes any connection on port 1234 of the remote machine (<em>from</em> the remote machine) to be forwarded via the local host to port 80 at www.google.com. To make things a bit more open, you could specify a bind address of 0.0.0.0:</p>
|
|
299
|
-
|
|
300
|
-
|
|
301
|
-
<div class='figure'>
|
|
302
|
-
<span class='caption'>Specifying the bind address when forwarding a remote port [ruby]</span>
|
|
303
|
-
<div class='body'><link rel='stylesheet' type='text/css' href='stylesheets/ruby.css' /><div class='ruby'><pre><span class="ident">session</span><span class="punct">.</span><span class="ident">forward</span><span class="punct">.</span><span class="ident">remote_to</span><span class="punct">(</span> <span class="number">80</span><span class="punct">,</span> <span class="punct">'</span><span class="string">www.google.com</span><span class="punct">',</span> <span class="number">1234</span><span class="punct">,</span> <span class="punct">'</span><span class="string">0.0.0.0</span><span class="punct">'</span> <span class="punct">)</span></pre></div></div></div>
|
|
304
|
-
</div>
|
|
305
|
-
|
|
306
|
-
|
|
307
|
-
|
|
308
|
-
<h2>
|
|
309
|
-
<a name="s4"></a>
|
|
310
|
-
6.4. Direct Channels
|
|
311
|
-
</h2>
|
|
312
|
-
|
|
313
|
-
|
|
314
|
-
|
|
315
|
-
<div class="section">
|
|
316
|
-
<p>Sometimes it might be nice to programmatically simulate a network connection on a local port and have it forwarded to the remote host. You can do this by means of the <code>#direct_channel</code> method.</p>
|
|
317
|
-
|
|
318
|
-
|
|
319
|
-
<p>The <code>#direct_channel</code> method looks similar to <code>#local</code>: the first three parameters are the local port to simulate the connection from, and the remote host and port that the connection should be forwarded to. The fourth parameter, however, is a <em>handler</em>, an object that is used as a callback for a variety of different events.</p>
|
|
320
|
-
|
|
321
|
-
|
|
322
|
-
<p>The handler for the <code>#direct_channel</code> method may implement any of the following callbacks (all are optional, though you probably want to implement at least one or two of them):</p>
|
|
323
|
-
|
|
324
|
-
|
|
325
|
-
<table class="list">
|
|
326
|
-
<tr>
|
|
327
|
-
<th>Callback </th>
|
|
328
|
-
<th>Description </th>
|
|
329
|
-
</tr>
|
|
330
|
-
<tr>
|
|
331
|
-
<td style="vertical-align:top;text-align:center;"><code>confirm</code> </td>
|
|
332
|
-
<td> This is invoked when the channel has been opened and the remote host has confirmed it. This accepts four parameters: the channel itself, the local port, remote host, and remote port. (In this way, the same handler may be used for multiple forward requests.)</td>
|
|
333
|
-
</tr>
|
|
334
|
-
<tr>
|
|
335
|
-
<td style="vertical-align:top;text-align:center;"><code>process</code> </td>
|
|
336
|
-
<td> After the channel has been confirmed, this is invoked, to process the channel. This callback will be invoked in a new Thread, so that if your handler needs to listen to a socket and then send data received from it over the channel, it can do so without blocking the main loop. The callback accepts a single parameter, the channel handle itself.</td>
|
|
337
|
-
</tr>
|
|
338
|
-
<tr>
|
|
339
|
-
<td style="vertical-align:top;text-align:center;"><code>on_close</code> </td>
|
|
340
|
-
<td> This is called when the channel over which this forwarded connection is being processed has been closed. The callback accepts a single parameter, the channel itself.</td>
|
|
341
|
-
</tr>
|
|
342
|
-
<tr>
|
|
343
|
-
<td style="vertical-align:top;text-align:center;"><code>on_eof</code> </td>
|
|
344
|
-
<td> When the remote machine indicates it will send no more data, this callback will be invoked. It accepts a single parameter, the channel itself.</td>
|
|
345
|
-
</tr>
|
|
346
|
-
<tr>
|
|
347
|
-
<td style="vertical-align:top;text-align:center;"><code>on_receive</code> </td>
|
|
348
|
-
<td> This is invoked when data is received from the remote machine. It accepts two parameters: the channel handle, and the data that was received.</td>
|
|
349
|
-
</tr>
|
|
350
|
-
</table>
|
|
351
|
-
|
|
352
|
-
|
|
353
|
-
|
|
354
|
-
|
|
355
|
-
<p>For example, the following example pretends to be a client that has connected to the local host on a forwarded port:</p>
|
|
356
|
-
|
|
357
|
-
|
|
358
|
-
<div class='figure'>
|
|
359
|
-
<span class='caption'>Using a handler object to mimic a forwarded port [ruby]</span>
|
|
360
|
-
<div class='body'><table border='0' cellpadding='0' cellspacing='0'><tr><td class='lineno'>1<br />2<br />3<br />4<br />5<br />6<br />7<br />8<br />9<br />10<br />11<br />12<br />13<br />14<br />15<br />16<br />17<br /></td><td width='100%'><link rel='stylesheet' type='text/css' href='stylesheets/ruby.css' /><div class='ruby'><pre><span class="keyword">class </span><span class="class">Handler</span>
|
|
361
|
-
<span class="keyword">def </span><span class="method">on_receive</span><span class="punct">(</span> <span class="ident">channel</span><span class="punct">,</span> <span class="ident">data</span> <span class="punct">)</span>
|
|
362
|
-
<span class="ident">puts</span> <span class="punct">"</span><span class="string">got data: <span class="expr">#{data.inspect}</span></span><span class="punct">"</span>
|
|
363
|
-
<span class="ident">channel</span><span class="punct">.</span><span class="ident">send_data</span> <span class="punct">"</span><span class="string">subsequent request</span><span class="punct">"</span>
|
|
364
|
-
<span class="keyword">end</span>
|
|
365
|
-
|
|
366
|
-
<span class="keyword">def </span><span class="method">process</span><span class="punct">(</span> <span class="ident">channel</span> <span class="punct">)</span>
|
|
367
|
-
<span class="ident">channel</span><span class="punct">.</span><span class="ident">send_data</span> <span class="punct">"</span><span class="string">initial request</span><span class="punct">"</span>
|
|
368
|
-
<span class="keyword">end</span>
|
|
369
|
-
<span class="keyword">end</span>
|
|
370
|
-
|
|
371
|
-
<span class="constant">Net</span><span class="punct">::</span><span class="constant">SSH</span><span class="punct">.</span><span class="ident">start</span><span class="punct">(</span> <span class="punct">'</span><span class="string">host</span><span class="punct">'</span> <span class="punct">)</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">session</span><span class="punct">|</span>
|
|
372
|
-
<span class="ident">session</span><span class="punct">.</span><span class="ident">forward</span><span class="punct">.</span><span class="ident">direct_channel</span><span class="punct">(</span> <span class="number">1234</span><span class="punct">,</span> <span class="punct">'</span><span class="string">somewhere.else.net</span><span class="punct">',</span>
|
|
373
|
-
<span class="number">4321</span><span class="punct">,</span> <span class="constant">Handler</span><span class="punct">.</span><span class="ident">new</span> <span class="punct">)</span>
|
|
374
|
-
|
|
375
|
-
<span class="ident">session</span><span class="punct">.</span><span class="ident">loop</span>
|
|
376
|
-
<span class="keyword">end</span></pre></div></td></tr></table></div></div>
|
|
377
|
-
|
|
378
|
-
|
|
379
|
-
<p>The local port number for <code>#direct_channel</code> has no real purpose, other than to report to the <span class="caps">SSH</span> server that the “virtual” connection occurred on that port.</p>
|
|
380
|
-
</div>
|
|
381
|
-
|
|
382
|
-
|
|
383
|
-
|
|
384
|
-
<h2>
|
|
385
|
-
<a name="s5"></a>
|
|
386
|
-
6.5. Remote-to-Local Handlers
|
|
387
|
-
</h2>
|
|
388
|
-
|
|
389
|
-
|
|
390
|
-
|
|
391
|
-
<div class="section">
|
|
392
|
-
<p>You can use handlers going in the other direction, too. If you want to programmatically process forwarded data from a remote host, you can use the <code>#remote</code> method. This takes two parameters, with an optional third parameter. The two required parameters are the handler to use, and the remote port that should be listened to. The optional parameter is the remote bind address, which defaults to ‘127.0.0.1’.</p>
|
|
393
|
-
|
|
394
|
-
|
|
395
|
-
<p>(Incidentally, if the port is 0, a new port will be allocated for you automatically by the server.)</p>
|
|
396
|
-
|
|
397
|
-
|
|
398
|
-
<p>Whenever connections are received on the remote port, they will be forwarded to the handler, which may implement the following callbacks:</p>
|
|
399
|
-
|
|
400
|
-
|
|
401
|
-
<table class="list">
|
|
402
|
-
<tr>
|
|
403
|
-
<th>Callback </th>
|
|
404
|
-
<th>Description </th>
|
|
405
|
-
</tr>
|
|
406
|
-
<tr>
|
|
407
|
-
<td style="vertical-align:top;text-align:center;"><code>error</code> </td>
|
|
408
|
-
<td> This is invoked if the forward could not be initiated. It accepts a single parameter, which is the error message. </td>
|
|
409
|
-
</tr>
|
|
410
|
-
<tr>
|
|
411
|
-
<td style="vertical-align:top;text-align:center;"><code>on_close</code> </td>
|
|
412
|
-
<td> This is invoked when the channel that was assigned to process this forwarded connection has been closed. The callback takes one parameter: the channel itself. </td>
|
|
413
|
-
</tr>
|
|
414
|
-
<tr>
|
|
415
|
-
<td style="vertical-align:top;text-align:center;"><code>on_eof</code> </td>
|
|
416
|
-
<td> This is invoked when the remote end of the connection has promised not to send any more data. The local end of the channel may continue to send data, however. This callback takes on parameter: the channel itself.</td>
|
|
417
|
-
</tr>
|
|
418
|
-
<tr>
|
|
419
|
-
<td style="vertical-align:top;text-align:center;"><code>on_open</code> </td>
|
|
420
|
-
<td> This is invoked when a new connection is received over the forwarded channel. It accepts five parameters: the channel object, the connected address, the connected port, the originator address, and the originator port. </td>
|
|
421
|
-
</tr>
|
|
422
|
-
<tr>
|
|
423
|
-
<td style="vertical-align:top;text-align:center;"><code>on_receive</code> </td>
|
|
424
|
-
<td> This is invoked when data is received over the channel from the remote connection. It accepts two parameters: the channel object, and the data that was received. </td>
|
|
425
|
-
</tr>
|
|
426
|
-
<tr>
|
|
427
|
-
<td style="vertical-align:top;text-align:center;"><code>setup</code> </td>
|
|
428
|
-
<td> This is invoked immediately after the forward request has been acknowledged as successful. It accepts a single parameter, which is the port that was assigned to this forward. If the port parameter to <code>#remote</code> was not 0, then that same value will be passed to the callback. Otherwise, the newly allocated port number will be passed to the callback. </td>
|
|
429
|
-
</tr>
|
|
430
|
-
</table>
|
|
431
|
-
|
|
432
|
-
|
|
433
|
-
|
|
434
|
-
|
|
435
|
-
<p>Note that the <code>on_receive</code> handler is required—all other callbacks may remain unimplemented by the handler.</p>
|
|
436
|
-
</div>
|
|
437
|
-
|
|
438
|
-
|
|
439
|
-
|
|
440
|
-
<div class="bottom"><div class="prevnext">
|
|
441
|
-
|
|
442
|
-
<a href="chapter-5.html">Previous (5. User Shells)</a> |
|
|
443
|
-
|
|
444
|
-
<a href="index.html">Up</a>
|
|
445
|
-
|
|
446
|
-
| <a href="chapter-7.html">Next (7. Using Proxies)</a>
|
|
447
|
-
|
|
448
|
-
</div></div>
|
|
449
|
-
|
|
450
|
-
|
|
451
|
-
</div>
|
|
452
|
-
|
|
453
|
-
</td></tr>
|
|
454
|
-
</table>
|
|
455
|
-
</body>
|
|
456
|
-
</html>
|