Re: [tor-relays] Relay - Conflicting data (Atlas != log)

2013-12-02 Thread Mark Jamsek
On 3/12/2013 11:52 AM, Roger Dingledine wrote: $ telnet 110.146.133.98 9001 Trying 110.146.133.98... It looks like it's not up currently. I've restarted, this time as a service from root -- not as a daemon from user. Don't think it's been long enough for Atlas to have updated. Not sure

Re: [tor-relays] Relay - Conflicting data (Atlas != log)

2013-12-02 Thread Roger Dingledine
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 an

[tor-relays] Relay - Conflicting data (Atlas != log)

2013-12-02 Thread Mark Jamsek
I am trying to run a restricted exit relay on FreeBSD 9.2-RELEASE in a jail. I tested it out a couple days ago on an old(er) box, and everything worked fine: https://atlas.torproject.org/#details/A5CA10E554124289C1B42B4CCA68F0CACFE503DC Decided to get it running on a fresher rig, all appears w