[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: My tor exit node is STILL gone from the node list
Considering how many places block ICMP, traceroute is not a good way
to determine connectivity.
telnet 89.248.169.109 80
works for me and traceroute doesn't:
C:\>tracert 89.248.169.109
Tracing route to 89.248.169.109 over a maximum of 30 hops
<.. snip ..>
15 105 ms 105 ms 105 ms 149.6.129.22
16 104 ms 102 ms 104 ms access.carrier.jointtransit.nl [213.207.0.245]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Regards,
Lee
On 7/20/09, Olaf Selke <olaf.selke@xxxxxxxxxxxx> wrote:
> Alexandru Cezar schrieb:
>>
>> It seems as if the node is unreachable from some of the authority servers,
>> but I have no idea
>> what to do about that. My ISP says that routing is fine and everything
>> should work as
>> expected. I don't understand why the node stays listed for a few hours
>> before disappearing.
>> Can someone please help me get this >100EUR/mnth node up again?
>
> traceroute from blutmagie ends at amsix peering
>
> anonymizer2:~# traceroute 89.248.169.108
> traceroute to 89.248.169.108 (89.248.169.108), 30 hops max, 60 byte packets
> 1 195.71.90.1 (195.71.90.1) 0.557 ms 0.547 ms 0.541 ms
> 2 xmws-gtso-de01-vlan-176.nw.mediaways.net (195.71.109.218) 1.381 ms
> 1.475 ms 1.522 ms
> 3 rmwc-gtso-de01-ge-0-2-0-0.nw.mediaways.net (195.71.12.57) 28.666 ms
> 28.665 ms 28.681 ms
> 4 rmwc-amsd-nl02-gigaet-2-0-0.nw.mediaways.net (195.71.254.182) 11.460 ms
> 11.458 ms 11.454 ms
> 5 * * *
> 6 * * *
> 7 * * *
> 8 * * *
> 9 * * *
> 10 *^C
>
> Olaf
>