<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Hi,</div><div dir="ltr"><br><blockquote type="cite">On 27 Mar 2020, at 02:00, niftybunny <abuse-contact@to-surf-and-protect.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=utf-8">My bad. Never seen this before. I there a good reason for the <span style="color: rgb(51, 51, 51); font-family: Menlo, Monaco, Consolas, "Courier New", monospace; font-size: 13px; background-color: rgb(245, 245, 245);" class="">accept 133.0.0.0/8:80 ?</span><div class=""><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 26. Mar 2020, at 15:06, <a href="mailto:gerard@bulger.co.uk" class="">gerard@bulger.co.uk</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">"btw, you need to have at least port 80 and 443 … port 80 is missing …"<br class=""><br class="">It there. But to a /8 area IPV4, all IPv6<br class=""><br class="">I have not changed my exit policy for years. Port 80 is there, just limited to a /8 network and all IPv6 addresses port 80 allowed.<br class="">443 all there IPv4 and IPv6<br class=""><br class="">Testing seems to be exiting OK, but badexit tag still there.<br></div></div></blockquote></div></div></div></blockquote><br><div>The Exit flag only request one IPv4 /8 :</div><div><a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2628">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2628</a></div><div><br></div><div>But if the network health team is testing a different IPv4 /8, then your</div><div>relay might appear down.</div><div><br></div><div>(If the DNS for the site they are testing has both IPv4 and IPv6, then</div><div>the outcome will depend on their tor version and config. 0.4.3 and</div><div>later will prefer IPv6 by default.)</div><div><br></div><div>T</div></body></html>