You won't get the Exit flag unless you exit to at least one IPv4 /8, on at least: * port 80 & 443, or * port 80 & 6667, or * port 443 & 6667. It's a documented issue that a relay can still get the Exit flag by exiting to an unused IPv4 /8 that's not in Tor's list of private addresses.
I don't know if Atlas does this because your relay doesn't have the Exit flag, or because your relay's policy rejects everything, or because your relay's policy doesn't allow IPv4.
What is the exit policy in your relay's descriptor?
(Tor 0.2.7 was fixed to make accept6/reject6 only produce IPv6 rules.) Let me do some testing to see if you've uncovered a bug.
This is wise. Tor will block your own IPv6 address, but it doesn't know about your subnet:
Tor blocks private addresses by default, so these lines are redundant, but harmless:
Tor doesn't block 6to4 addresses by default, so this is useful:
This should make sure most IPv6 ports are accepted, because it comes before the reject rules. You could try: "ExitPolicy accept6 *6:*", but it should have exactly the same outcome.
This actually blocks private IPv4 and IPv6, and it's redundant because Tor blocks private addresses by default:
This actually blocks IPv4 and IPv6:
Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F |
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays