Fwd: New tor node not acting as an exit server?
I scrapped my previous exit node and set up a new one on a different machine. It's been running for 6 and a half hours, but does not have the exit flag. The logs say both my ORPort and DirPort are reachable from the outside, and using arm from a different machine shows two circuits open.
From the config file: ExitPolicy reject 192.168.0.0/16:*,accept *:80,accept *:443,reject *:*
Anyone know why my new node isn't being used or recognized as an exit node? Did I forget a config option? Fingerprint: 1e598cdb9bbc751d753146d880b326952886d73b
On Sun, Sep 08, 2013 at 05:23:12PM -0400, Niles Rogoff wrote:
I scrapped my previous exit node and set up a new one on a different machine. It's been running for 6 and a half hours, but does not have the exit flag. The logs say both my ORPort and DirPort are reachable from the outside, and using arm from a different machine shows two circuits open.
From the config file: ExitPolicy reject 192.168.0.0/16:*,accept *:80,accept *:443,reject *:*
Anyone know why my new node isn't being used or recognized as an exit node? Did I forget a config option?
Fingerprint: 1e598cdb9bbc751d753146d880b326952886d73b
Looks like it's working as you expected: https://atlas.torproject.org/#details/1E598CDB9BBC751D753146D880B326952886D7... (Six and a half hours is a short time to wait.) --Roger
I'll take your word for it, but it seems more than a little odd that it doesn't have the "exit" flag applied
participants (2)
-
Niles Rogoff -
Roger Dingledine