[tor-commits] [community/staging] Use port 3818 instead of 9001 in our example log.

[hiro@xxxxxxxxxxxxxx]

commit 3cb1c18146838a1c0d54be462bedd7869fa88e3c
Author: Philipp Winter <phw@xxxxxxxxx>
Date:   Wed Aug 7 12:34:39 2019 -0700

    Use port 3818 instead of 9001 in our example log.
    
    Port 9001 should not be used for a bridge.
---
 .../technical-setup/bridge/centos-rhel-opensuse/contents.lr             | 2 +-
 .../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr   | 2 +-
 content/relay-operations/technical-setup/bridge/freebsd/contents.lr     | 2 +-
 content/relay-operations/technical-setup/bridge/openbsd/contents.lr     | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr
index 32fe769..a3370a4 100644
--- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr
@@ -89,7 +89,7 @@ To confirm your bridge is running with no issues, you should see something like
 [notice] Registered server transport 'obfs4' at '[::]:46396'
 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
 [notice] Bootstrapped 100%: Done
-[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
+[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
 ``` 
 
diff --git a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
index ea88cc7..913eab8 100644
--- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
@@ -75,7 +75,7 @@ To confirm your bridge is running with no issues, you should see something like
 [notice] Registered server transport 'obfs4' at '[::]:46396'
 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
 [notice] Bootstrapped 100%: Done
-[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
+[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
 ```
 ---
diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr
index 5353d5c..fe3c09c 100644
--- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr
@@ -75,7 +75,7 @@ To confirm your bridge is running with no issues, you should see something like
 [notice] Registered server transport 'obfs4' at '[::]:46396'
 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
 [notice] Bootstrapped 100%: Done
-[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
+[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
 ```
 
diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr
index f9c98e9..63d8c73 100644
--- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr
@@ -70,7 +70,7 @@ To confirm your bridge is running with no issues, you should see something like
 [notice] Registered server transport 'obfs4' at '[::]:46396'
 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
 [notice] Bootstrapped 100%: Done
-[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
+[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
 ```
 ---



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits