diff options
-rw-r--r-- | ChangeLog | 8 | ||||
-rw-r--r-- | ssh.1 | 20 |
2 files changed, 22 insertions, 6 deletions
@@ -1,3 +1,9 @@ | |||
1 | 20061105 | ||
2 | - (djm) OpenBSD CVS Sync | ||
3 | - otto@cvs.openbsd.org 2006/10/28 18:08:10 | ||
4 | [ssh.1] | ||
5 | correct/expand example of usage of -w; ok jmc@ stevesk@ | ||
6 | |||
1 | 20061101 | 7 | 20061101 |
2 | - (dtucker) [openbsd-compat/port-solaris.c] Bug #1255: Make only hwerr | 8 | - (dtucker) [openbsd-compat/port-solaris.c] Bug #1255: Make only hwerr |
3 | events fatal in Solaris process contract support and tell it to signal | 9 | events fatal in Solaris process contract support and tell it to signal |
@@ -2578,4 +2584,4 @@ | |||
2578 | OpenServer 6 and add osr5bigcrypt support so when someone migrates | 2584 | OpenServer 6 and add osr5bigcrypt support so when someone migrates |
2579 | passwords between UnixWare and OpenServer they will still work. OK dtucker@ | 2585 | passwords between UnixWare and OpenServer they will still work. OK dtucker@ |
2580 | 2586 | ||
2581 | $Id: ChangeLog,v 1.4581 2006/10/31 23:28:49 dtucker Exp $ | 2587 | $Id: ChangeLog,v 1.4582 2006/11/04 18:31:33 djm Exp $ |
@@ -34,7 +34,7 @@ | |||
34 | .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF | 34 | .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF |
35 | .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. | 35 | .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
36 | .\" | 36 | .\" |
37 | .\" $OpenBSD: ssh.1,v 1.264 2006/09/25 04:55:38 ray Exp $ | 37 | .\" $OpenBSD: ssh.1,v 1.265 2006/10/28 18:08:10 otto Exp $ |
38 | .Dd September 25, 1999 | 38 | .Dd September 25, 1999 |
39 | .Dt SSH 1 | 39 | .Dt SSH 1 |
40 | .Os | 40 | .Os |
@@ -1077,12 +1077,22 @@ controls whether the server supports this, | |||
1077 | and at what level (layer 2 or 3 traffic). | 1077 | and at what level (layer 2 or 3 traffic). |
1078 | .Pp | 1078 | .Pp |
1079 | The following example would connect client network 10.0.50.0/24 | 1079 | The following example would connect client network 10.0.50.0/24 |
1080 | with remote network 10.0.99.0/24, provided that the SSH server | 1080 | with remote network 10.0.99.0/24 using a point-to-point connection |
1081 | running on the gateway to the remote network, | 1081 | from 10.1.1.1 to 10.1.1.2, |
1082 | at 192.168.1.15, allows it: | 1082 | provided that the SSH server running on the gateway to the remote network, |
1083 | at 192.168.1.15, allows it. | ||
1084 | .Pp | ||
1085 | On the client: | ||
1083 | .Bd -literal -offset indent | 1086 | .Bd -literal -offset indent |
1084 | # ssh -f -w 0:1 192.168.1.15 true | 1087 | # ssh -f -w 0:1 192.168.1.15 true |
1085 | # ifconfig tun0 10.0.50.1 10.0.99.1 netmask 255.255.255.252 | 1088 | # ifconfig tun0 10.1.1.1 10.1.1.2 netmask 255.255.255.252 |
1089 | # route add 10.0.99.0/24 10.1.1.2 | ||
1090 | .Ed | ||
1091 | .Pp | ||
1092 | On the server: | ||
1093 | .Bd -literal -offset indent | ||
1094 | # ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.252 | ||
1095 | # route add 10.0.50.0/24 10.1.1.1 | ||
1086 | .Ed | 1096 | .Ed |
1087 | .Pp | 1097 | .Pp |
1088 | Client access may be more finely tuned via the | 1098 | Client access may be more finely tuned via the |