On Tue, Dec 03, 2013 at 11:08:48AM +1100, Mark Jamsek wrote:
Dec 02 15:49:34.000 [notice] Now checking whether ORPort 110.146.133.98:9001 and DirPort 110.146.133.98:9030 are reachable... (this may take up to 20 minutes --
[snip]
Apart from the DNS hijacking entry(?), Tor is apparently up and running. However, according to Atlas, it is not: https://atlas.torproject.org/#details/EE16D7A4FBCF6494FEE75C856D76782295CB9D... (forgot to backup tor key; hence, the different print)
$ telnet 110.146.133.98 9001 Trying 110.146.133.98...
It looks like it's not up currently.
Not sure what to think or do. Is it advertised on Atlas as false due to this entry: [notice] Not advertising DirPort (Reason: AccountingMax enabled)
No, that just means it's going to write '0' for its dirport in its relay descriptor, discouraging clients from using it for fetching directory information.
Or is one of the two sources (system or Atlas) wrongly reporting? Thank you.
https://metrics.torproject.org/relay-search.html?search=110.146.133.98 looks like it was up for that one consensus period and then down after that. Are you doing port forwarding (wrong)?
--Roger