tyler.durden/openssh-portable
1
0
Fork 0
mirror of https://github.com/PowerShell/openssh-portable.git synced 2025-07-28 16:24:39 +02:00
Code Issues Packages Projects Releases Wiki Activity

- (djm) OpenBSD CVS Sync

Browse Source 
- otto@cvs.openbsd.org 2006/10/28 18:08:10
     [ssh.1]
     correct/expand example of usage of -w; ok jmc@ stevesk@
This commit is contained in:
Damien Miller 2006-11-05 05:31:33 +11:00
parent 4d13ecea54
commit 3975ee2c3c
2 changed files with 22 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ChangeLog
View File

@ -1,3 +1,9 @@
20061105
- (djm) OpenBSD CVS Sync
- otto@cvs.openbsd.org 2006/10/28 18:08:10
[ssh.1]
correct/expand example of usage of -w; ok jmc@ stevesk@
20061101 20061101
- (dtucker) [openbsd-compat/port-solaris.c] Bug #1255: Make only hwerr - (dtucker) [openbsd-compat/port-solaris.c] Bug #1255: Make only hwerr
events fatal in Solaris process contract support and tell it to signal events fatal in Solaris process contract support and tell it to signal
@ -2578,4 +2584,4 @@
OpenServer 6 and add osr5bigcrypt support so when someone migrates OpenServer 6 and add osr5bigcrypt support so when someone migrates
passwords between UnixWare and OpenServer they will still work. OK dtucker@ passwords between UnixWare and OpenServer they will still work. OK dtucker@
$Id: ChangeLog,v 1.4581 2006/10/31 23:28:49 dtucker Exp $ $Id: ChangeLog,v 1.4582 2006/11/04 18:31:33 djm Exp $

20
ssh.1
View File

@ -34,7 +34,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\" .\"
.\" $OpenBSD: ssh.1,v 1.264 2006/09/25 04:55:38 ray Exp $ .\" $OpenBSD: ssh.1,v 1.265 2006/10/28 18:08:10 otto Exp $
.Dd September 25, 1999 .Dd September 25, 1999
.Dt SSH 1 .Dt SSH 1
.Os .Os
@ -1077,12 +1077,22 @@ controls whether the server supports this,
and at what level (layer 2 or 3 traffic). and at what level (layer 2 or 3 traffic).
.Pp .Pp
The following example would connect client network 10.0.50.0/24 The following example would connect client network 10.0.50.0/24
with remote network 10.0.99.0/24, provided that the SSH server with remote network 10.0.99.0/24 using a point-to-point connection
running on the gateway to the remote network, from 10.1.1.1 to 10.1.1.2,
at 192.168.1.15, allows it: provided that the SSH server running on the gateway to the remote network,
at 192.168.1.15, allows it.
.Pp
On the client:
.Bd -literal -offset indent .Bd -literal -offset indent
# ssh -f -w 0:1 192.168.1.15 true # ssh -f -w 0:1 192.168.1.15 true
# ifconfig tun0 10.0.50.1 10.0.99.1 netmask 255.255.255.252 # ifconfig tun0 10.1.1.1 10.1.1.2 netmask 255.255.255.252
# route add 10.0.99.0/24 10.1.1.2
.Ed
.Pp
On the server:
.Bd -literal -offset indent
# ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.252
# route add 10.0.50.0/24 10.1.1.1
.Ed .Ed
.Pp .Pp
Client access may be more finely tuned via the Client access may be more finely tuned via the