use reserved documentation IPs instead of 1.2.3.4

willamowius · Sep 24, 2023 · 97662d9 · 97662d9
1 parent 4eab915
commit 97662d9
Show file tree

Hide file tree

Showing 6 changed files with 15 additions and 15 deletions.
diff --git a/docs/manual/acct.sgml b/docs/manual/acct.sgml
@@ -1444,7 +1444,7 @@ need to be accessible for everybody who wants to call into your network,
 but that should not be allowed to support external to external calls.
 
 <itemize>
-<item><tt>Networks=192.168.1.0/24,1.2.3.4/24</tt><newline>
+<item><tt>Networks=192.168.1.0/24,192.0.2.0/24</tt><newline>
 Default: <tt>N/A</tt>
 <p>
 List the networks your gatekeeper supports. Either the source or the destination of

diff --git a/docs/manual/mainconfig.sgml b/docs/manual/mainconfig.sgml
@@ -323,7 +323,7 @@ will not register with this gatekeeper again.
 compliant endpoints.
 
 <label id="alternategks">
-<item><tt/AlternateGKs=1.2.3.4;1719;false;1;GnuGk2/<newline>
+<item><tt/AlternateGKs=192.0.2.4;1719;false;1;GnuGk2/<newline>
 Default: <tt>N/A</tt><newline>
 <p>
 If the endpoint loses connectivity with GnuGk it should automatically try 
@@ -355,7 +355,7 @@ You may specify multiple alternate gatekeepers as a comma separated list.
 This global definition can be overriden by a per IP specification in
 <ref id="rassrvalternategatekeeper" name="[RasSrv::AlternateGatekeeper]">.
 
-<item><tt/SendTo=1.2.3.4:1719/<newline>
+<item><tt/SendTo=192.0.2.4:1719/<newline>
 Default: <tt>N/A</tt><newline>
 <p>
 Although this information is contained in AlternateGKs, you must still
@@ -364,7 +364,7 @@ address due to multihomed systems, so it's a separate config option.
 
 You can specify multiple gatekeepers in a comma separated list.
 
-<item><tt/SkipForwards=1.2.3.4,5.6.7.8/<newline>
+<item><tt/SkipForwards=192.0.2.4,192.0.2.5/<newline>
 Default: <tt>N/A</tt><newline>
 <p>
 To avoid circular forwarding, you shouldn't forward RRQs you get from the
@@ -405,7 +405,7 @@ User passwords can be set in the <ref id="gkstatusauth" name="[GkStatus::Auth]">
 
 Example connection command:
 <tscreen><verb>
-ssh -p 7000 gnugk@1.2.3.4
+ssh -p 7000 gnugk@192.0.2.4
 </verb></tscreen>
 
 <label id="statuseventbacklog">

diff --git a/docs/manual/ras.sgml b/docs/manual/ras.sgml
@@ -295,8 +295,8 @@ all other networks will use the globally defined alternate gatekeeper.
 
 <tscreen><verb>
 [RasSrv::AlternateGatekeeper]
-192.168.0.0/18=1.2.3.4;1719;true;1;GnuGk4
-192.168.1.10=1.2.3.10;1719;true;1;GnuGk10
+192.168.0.0/18=192.0.2.4;1719;true;1;GnuGk4
+192.168.1.10=192.0.2.10;1719;true;1;GnuGk10
 </verb></tscreen>
 
 </descrip>

diff --git a/docs/manual/routedmode.sgml b/docs/manual/routedmode.sgml
@@ -1002,7 +1002,7 @@ which only looks at the IP inside the message.
 AllowSignaledIPsFrom= works better than AllowSignaledIPs= to whitelist private IPs from your own
 network that may also be inside messages from outside that happen to use the same private IPs behind a NAT.
 
-<item><tt>AllowAnyRTPSourcePortForH239From=1.2.3.4</tt><newline>
+<item><tt>AllowAnyRTPSourcePortForH239From=192.0.2.4</tt><newline>
 Default: <tt>n/a</tt><newline>
 <p>
 Some devices signal an incorrect RTCP port for H.239 channels in OLC which leads GnuGk
@@ -1084,7 +1084,7 @@ This helps some endpoints, especially for H.239, but may break some connections
 pick different RTP sessions and receiving ports for different directions of the same session
 type (eg. some LifeSize endpoints and EdgeProtect devices).
 
-<item><tt>MatchH239SessionsByIDOnly=1.2.3.4,10.0.0.0/8</tt><newline>
+<item><tt>MatchH239SessionsByIDOnly=192.0.2.4,10.0.0.0/8</tt><newline>
 Default: <tt>n/a</tt><newline>
 <p>
 Never match the reverse H.239 channels by type on messages received from these IPs or networks.

diff --git a/docs/manual/routing.sgml b/docs/manual/routing.sgml
@@ -697,9 +697,9 @@ Example JSON responses:
 <item><tt>{ "reject": true }</tt>
 <item><tt>{ "reject": true, "reject-reason": 2 }</tt>
 <item><tt>{ "destination": "support" }</tt>
-<item><tt>{ "destination": "1.2.3.4" }</tt>
-<item><tt>{ "destination": "support", "gateway": "1.2.3.4:1720" }</tt>
-<item><tt>[ { "destination": "support", "gateway": "1.2.3.4:1720" }, { "destination": "support", "gateway": "5.6.7.8:1720" } ]</tt>
+<item><tt>{ "destination": "192.0.2.4" }</tt>
+<item><tt>{ "destination": "support", "gateway": "192.0.2.4:1720" }</tt>
+<item><tt>[ { "destination": "support", "gateway": "192.0.2.4:1720" }, { "destination": "support", "gateway": "192.0.2.8:1720" } ]</tt>
 </itemize>
 
 
@@ -857,7 +857,7 @@ create table gnugk.forwards (
 <label id="routingcatchall">
 <p>
 <itemize>
-<item><tt/CatchAllIP=1.2.3.4/<newline>
+<item><tt/CatchAllIP=192.0.2.4/<newline>
 Default: <tt>(empty)</tt><newline>
 <p>
 Specify an IP address to route all calls to. This overrides CatchAllAlias.

diff --git a/docs/manual/tutorial.sgml b/docs/manual/tutorial.sgml
@@ -31,7 +31,7 @@ thereby allowing the gatekeeper to creating an association between the user
 "jan" and their IP address.  
 
 SimpH323 will attempt to automatically locate the gatekeeper, but if the auto
-detection fails, use "<tt/-g 1.2.3.4/" to specify the IP address.
+detection fails, use "<tt/-g 192.0.2.4/" to specify the IP address.
 
 On the second client run simph323 this way:
 
@@ -333,7 +333,7 @@ Because the gatekeeper has a lot of control over the calls,
 it can also be used to terminate them. While
 connected to the status port, you can list all active calls
 with "<tt/PrintCurrentCalls/". To terminate a call, type
-"<tt/Disconnectip 1.2.3.4/" for one of the endpoints.
+"<tt/Disconnectip 192.0.2.5/" for one of the endpoints.
 
 For example, a simple script could be written to connect to
 the status port, obtain a list of ongoing calls and terminate