diff options
| author | joerg <joerg@FreeBSD.org> | 2001-12-30 16:40:48 +0000 |
|---|---|---|
| committer | joerg <joerg@FreeBSD.org> | 2001-12-30 16:40:48 +0000 |
| commit | 78076f70e284cd5adeba4fd2eee89eb0b128642b (patch) | |
| tree | 352d9149acdd82270837d7c4e0d7a6d06242a634 | |
| parent | 52c592a3bcb88992eaf078b96adabf244512b6b1 (diff) | |
| download | FreeBSD-src-78076f70e284cd5adeba4fd2eee89eb0b128642b.zip FreeBSD-src-78076f70e284cd5adeba4fd2eee89eb0b128642b.tar.gz | |
Document the change from 0.0.0.1 to 0.0.0.* as `any remote address is OK'.
MFC after: 1 month
| -rw-r--r-- | share/man/man4/sppp.4 | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/share/man/man4/sppp.4 b/share/man/man4/sppp.4 index af4c6b0..f1f9f0b 100644 --- a/share/man/man4/sppp.4 +++ b/share/man/man4/sppp.4 @@ -25,7 +25,7 @@ .\" .\" $FreeBSD$ .\" -.Dd December 27, 2001 +.Dd December 30, 2001 .Dt SPPP 4 .Os .Sh NAME @@ -120,11 +120,13 @@ late during the negotiation, which might cause the remote peer to make wrong assumptions. .Pp In a similar spirit the remote address can be set to the magical -value 0.0.0.1 which means that we don't care what address the remote +value +.Ns 0.0.0. Ns Em \&* +which means that we don't care what address the remote side will use, as long as it is not 0.0.0.0. This is useful if your ISP has several dial-in servers. You can of course -.Nm route Cm add Ar something_or_other 0.0.0.1 +.Nm route Cm add Ar something_or_other 0.0.0. Ns Em \&* and it will do exactly what you would want it to. .Pp The PAP and CHAP authentication protocols as described in RFC 1334, |
