From bd0614a3d10b14d07ead70b46bed8f44857ff970 Mon Sep 17 00:00:00 2001 From: ru Date: Fri, 28 Feb 2003 15:41:45 +0000 Subject: Don't pretend natd(8) doesn't work with ppp(8) interfaces. While there's probably a better way to achieve the same, nothing precludes us from using natd(8) on tun(4) links. Noticed by: bde --- sbin/natd/natd.8 | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) (limited to 'sbin/natd') diff --git a/sbin/natd/natd.8 b/sbin/natd/natd.8 index 326a009..a6bf1b6 100644 --- a/sbin/natd/natd.8 +++ b/sbin/natd/natd.8 @@ -1,5 +1,5 @@ .\" $FreeBSD$ -.Dd June 27, 2000 +.Dd February 28, 2003 .Dt NATD 8 .Os .Sh NAME @@ -41,11 +41,16 @@ with .Xr divert 4 sockets under .Fx . -It is intended for use with NICs - if you want to do NAT on a PPP link, -use the +.Pp +(If you need NAT on a PPP link, +.Xr ppp 8 +provides the .Fl nat -switch to -.Xr ppp 8 . +option that gives most of the +.Nm +functionality, and uses the same +.Xr libalias 3 +library.) .Pp The .Nm @@ -581,6 +586,7 @@ Running the script in the background should be enough to prevent this disaster. .El .Sh SEE ALSO +.Xr libalias 3 , .Xr divert 4 , .Xr protocols 5 , .Xr rc.conf 5 , -- cgit v1.1