commit 8b81e16dc15de36ddea985d55a4324ec3afa69e8 Author: nusenu <nusenu-github@riseup.net> Date: Sat Feb 10 14:00:25 2018 +0000 FAQ (relay section): put most relevant answer in this question at the beginning --- docs/en/faq.wml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/en/faq.wml b/docs/en/faq.wml index ba7d9854..4dc00320 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -2136,6 +2136,11 @@ need to be?</a></h3> </p> <ul> + <li>It's fine if the relay goes offline sometimes. The directories + notice this quickly and stop advertising the relay. Just try to make + sure it's not too often, since connections using the relay when it + disconnects will break. + </li> <li>Tor has built-in support for <a href="#BandwidthShaping"> rate limiting</a>. Further, if you have a fast @@ -2155,11 +2160,6 @@ your relay, you can set it up to only allow connections to other Tor relays. </li> - <li>It's fine if the relay goes offline sometimes. The directories - notice this quickly and stop advertising the relay. Just try to make - sure it's not too often, since connections using the relay when it - disconnects will break. - </li> <li>If your relay is behind a NAT and it doesn't know its public IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port forwarding. Forwarding TCP connections is system dependent but