My tor exit node is STILL gone from the node list

[Lee]

On 7/20/09, Alexandru Cezar <tor at ze.ro> wrote:
>> Best of luck getting your provider to straighten out the routing.
>
> I have limited experience in running servers. From what I found out, my Xen
> dom0 is traceable
> (89.248.169.106), while the virtual host running TOR is not (89.248.169.109,
> vif-bridge). I can
> still access the web server running on 109 though.
> Is this a Xen misconfiguration? I can't think of anything that I have
> changed.

Have you talked to your provider about reachability?   Earlier I
couldn't do a traceroute to your machine & now I can:

C:\>tracert 89.248.169.106

Tracing route to 89.248.169.106 over a maximum of 30 hops
..snip..
 10    94 ms    92 ms    93 ms  te7-3.ccr01.lon01.atlas.cogentco.com
[66.28.4.190]
 11    96 ms    94 ms    94 ms  te2-7.mpd04.ams03.atlas.cogentco.com
[130.117.1.37]
 12   101 ms   101 ms   100 ms  te2-2.mpd03.ams03.atlas.cogentco.com
[130.117.3.62]
 13    99 ms    98 ms    99 ms  149.6.129.22
 14    95 ms    95 ms    94 ms  access.carrier.jointtransit.nl [213.207.0.245]
 15     *        *        *     Request timed out.
 16    97 ms   101 ms    96 ms  89.248.169.106

Trace complete.

C:\>tracert 89.248.169.109

Tracing route to 89.248.169.109 over a maximum of 30 hops
..snip..
 10    14 ms    14 ms    14 ms  te3-3.ccr02.jfk02.atlas.cogentco.com
[154.54.5.245]
 11   105 ms   108 ms   106 ms  te9-1.mpd03.jfk02.atlas.cogentco.com
[154.54.25.141]
 12   104 ms   103 ms   105 ms  te3-8.mpd01.ymq02.atlas.cogentco.com
[154.54.5.118]
 13    99 ms    99 ms   101 ms  te8-2.ccr01.ams03.atlas.cogentco.com
[154.54.0.69]
 14   101 ms   114 ms   111 ms  vl3493.mpd03.ams03.atlas.cogentco.com
[130.117.0.242]
 15   104 ms   104 ms   104 ms  149.6.129.22
 16   100 ms    99 ms   101 ms  access.carrier.jointtransit.nl [213.207.0.245]
 17     *        *        *     Request timed out.
 18   102 ms   101 ms   102 ms  89.248.169.109

Trace complete.

Seems rather strange that traceroute didn't work and now it does.

Lee