update sppp(4) docs to mention remote address range hack

As already documented in pppoe(4). I missed updating sppp(4) years
ago when support for the wildcard address range was added.

diff --git a/share/man/man4/sppp.4 b/share/man/man4/sppp.4
index 295767a..026e660 100644 (file)
--- a/share/man/man4/sppp.4
+++ b/share/man/man4/sppp.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: sppp.4,v 1.27 2023/02/21 07:47:24 jmc Exp $
+.\" $OpenBSD: sppp.4,v 1.28 2023/03/23 12:43:38 stsp Exp $
 .\"
 .\" Copyright (c) 1997 Joerg Wunsch
 .\"
@@ -25,7 +25,7 @@
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\"
-.Dd $Mdocdate: February 21 2023 $
+.Dd $Mdocdate: March 23 2023 $
 .Dt SPPP 4
 .Os
 .Sh NAME
@@ -126,9 +126,9 @@ Due to the way the IPCP option negotiation works, this address is
 supplied late during the negotiation, which could cause the remote peer
 to make false 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
-side will use, as long as it is not 0.0.0.0.
+In a similar spirit the remote address can be set to a magical value in
+the range 0.0.0.1 to 0.0.0.255, 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
 .Ic route add