Re: Re: My tor exit node is STILL gone from the node list

[Lee <ler762@xxxxxxxxx>]

On 7/20/09, Alexandru Cezar <tor@xxxxx> wrote:
>> 89.248.169.109 doesn't answer a ping, so I don't know of an easy way
>> to check if that's the problem or no.
>
> It at least shouldn't be a problem for TOR, because it has worked with that
> setup for months.

Unless you know for sure that nothing has changed on the path between
your server and all the directory servers you don't know if path MTU
discovery being broken (if it really is) is a new problem or not.

> To avoid further confusion, I have enabled answers to ICMP
> requests.

Thanks.  Path MTU discovery isn't a problem between me & your server -
1500 bytes gets there and back no problem:
C:\>ping -f -l 1472 89.248.169.109

Pinging 89.248.169.109 with 1472 bytes of data:

Reply from 89.248.169.109: bytes=1472 time=118ms TTL=48
Reply from 89.248.169.109: bytes=1472 time=118ms TTL=48
Reply from 89.248.169.109: bytes=1472 time=118ms TTL=48
Reply from 89.248.169.109: bytes=1472 time=118ms TTL=48

Ping statistics for 89.248.169.109:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 118ms, Maximum = 118ms, Average = 118ms

(On Windows it's 1472 bytes of data + 20 bytes IP header + 8 bytes
ICMP header = 1500)

What all do the directory servers need to do/see before marking your
server as a good exit?  It'd be nice to know what they can't do that's
keeping your server from being marked as a good exit..

Lee