Re: Re: Re: Re: My tor exit node is STILL gone from the node list
I haven't had the time and sufficient knowledge to work out what's wrong, but for some reason the node is back online for a 'record' of nearly 48 hours now: http://torstatus.blutmagie.de/router_detail.php?FP=d3eb313299a0082a4a4e10e0eb758e4f0163f4f0 I didn't change anything and the ISP didn't inform me about any changes on their side. -Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro
Re: Re: Re: My tor exit node is STILL gone from the node list
Hi Alexandru, On 8/4/09, Alexandru Cezar t...@ze.ro wrote: Hi list, hi Lee, 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. I have again spoken to my ISP and they say routing is fine. Routing could very well be just fine PMUTD still be broken.. but it looks like the problem is with Ecatel network announcements. Check this out: http://bgplay.routeviews.org/bgplay/ give it your network (89.248.169.0/24), select the last few days and watch how the route bounces around. I'd suggest getting a list of the directory servers and creating a script that tries to connect to each one every 20-30 minutes. Log the status of each connection attempt and, assuming there's some failures, go back to your provider with the list of IP addresses and times when you couldn't connect to them. Give them specific times IP addresses and they might be able to fix whatever it is. 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.. I'm interested in that as well. I still cannot get it to be flagged 'Running' reliably. Would TOR logging on my side help on this? I guess not? I have no idea, but it couldn't hurt to enable logging and see if there's anything interesting logged. Appreciate any help, I'm sure you don't mind getting 4MB/s exits back. ;-) It'd be nice if somebody could give you the status/timestamp of your server as seen from the directory servers. That might be enough to help your provider figure out what the problem is. Regards, Lee
Re: Re: Re: My tor exit node is STILL gone from the node list
Hi list, hi Lee, 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. I have again spoken to my ISP and they say routing is fine. 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.. I'm interested in that as well. I still cannot get it to be flagged 'Running' reliably. Would TOR logging on my side help on this? I guess not? Appreciate any help, I'm sure you don't mind getting 4MB/s exits back. ;-) Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro
Re: My tor exit node is STILL gone from the node list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 thus Scott Bennett spake: | On Tue, 21 Jul 2009 00:03:10 +0300 Alexandru Cezar t...@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. | | I've never worked with Xen, so I can't answer that. However, it is | certainly possible to misconfigure other virtualization environments in | ways that would probably cause those symptoms. OTOH, it strikes me as | more likely that the host system's packet filtering/redirection/NAT software | may be misconfigured. Xen doesn't yet run on the BSDs, AFAIK, so I'll guess | that it's running on a LINUX system of some flavor, so iptables is probably | the filtering package. Beyond that, I can't tell you much. Some of the | LINUX users on this list ought to be able to give you some help in figuring | out whether the problem is with Xen or with the host system. | | | Scott Bennett, Comm. ASMELG, CFIAG hi, a vif-bridge in Xen does, what it's name says: It bridges. So when your domU has a 'proper' (plain standard seen from within the domU itself) IP setup, there's no difference to a bare metal host. However, as I see, your problem's already fixed? Best, Timo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFKZWMqfg746kcGBOwRAjMgAKC37tgWTftU17sEoLR47yC23I55AACaAyjf aKA5vUmSbC8YXFuU+tGpofI= =7lXw -END PGP SIGNATURE-
Re: My tor exit node is STILL gone from the node list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 thus Alexandru Cezar spake: | Hi list, | | I am still struggling to get my server back on the list of Tor nodes. For several months it | was among the top 5 nodes, pumping 15TB a month. I am paying a lot of money for that machine, | and I don't see why it just doesn't work any more. | | Let me reiterate what's happening: Since April, the node disappears from the node list after a | few hours of running. I have tried to change exit policies, node name, node keys, ports and IP | (within the same subnet). After the IP change the node was listed (and used) for several hours | before it vanished. There's nothing about in the log file. | | 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? | | Information about the node: | | Current IP 89.248.169.109 (previously 89.248.169.108) | Nickname kyirong2 (previously kyirong) | Fingerprint D3EB 3132 99A0 082A 4A4E 10E0 EB75 8E4F 0163 F4F0 | (Old fp: A8BD 32A9 C2F2 0C4F 8ED2 C26C E477 0A24 85E3 CD22) | | Tor 0.2.1.17-rc Debian | DirPort 80, ORPort 8080 | | | -- | Alexandru Hi again, besides the routing stuff I saw that on the mentioned IP (see above) there's a nice disclaimer-like website that impresses me. I'm still not sure whether to pimp my node to be an exit node or not (due to the supressing that happens here in Germany). However, this suits me well. Is this a usual practice for TOR admins, and if yes, is there a multilingual approach? Best, Timo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFKZWkwfg746kcGBOwRAlwMAJ0XgV8rkGMq+5r4pc8yO+KI/RsMdwCguzb1 fErXJrwX3tlaUXGvtqlcr1Y= =z1Ji -END PGP SIGNATURE-
Re: My tor exit node is STILL gone from the node list
On Tue, 21 Jul 2009 08:41:46 +0200 Timo Schoeler timo.schoe...@riscworks.net wrote: thus Scott Bennett spake: Actually, no, I didn't, but I did write :-) : | On Tue, 21 Jul 2009 00:03:10 +0300 Alexandru Cezar t...@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. | | I've never worked with Xen, so I can't answer that. However, it is | certainly possible to misconfigure other virtualization environments in | ways that would probably cause those symptoms. OTOH, it strikes me as | more likely that the host system's packet filtering/redirection/NAT software | may be misconfigured. Xen doesn't yet run on the BSDs, AFAIK, so I'll guess | that it's running on a LINUX system of some flavor, so iptables is probably | the filtering package. Beyond that, I can't tell you much. Some of the | LINUX users on this list ought to be able to give you some help in figuring | out whether the problem is with Xen or with the host system. | | | Scott Bennett, Comm. ASMELG, CFIAG hi, a vif-bridge in Xen does, what it's name says: It bridges. So when your domU has a 'proper' (plain standard seen from within the domU itself) IP setup, there's no difference to a bare metal host. However, as I see, your problem's already fixed? Actually, it was Alexandru reporting the problem, not I, but it's not obvious that it is fixed. kyirong2 has been missing from the consensus for quite a few hours now. I don't know whether that means he is trying different Xen tricks, is working with his ISP, or some other possibility that would leave his node down or unreachable for now. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * **
Re: My tor exit node is STILL gone from the node list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 thus Scott Bennett spake: | On Tue, 21 Jul 2009 08:41:46 +0200 Timo Schoeler | timo.schoe...@riscworks.net wrote: | thus Scott Bennett spake: | Actually, no, I didn't, but I did write :-) : | | On Tue, 21 Jul 2009 00:03:10 +0300 Alexandru Cezar t...@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. | | | | I've never worked with Xen, so I can't answer that. However, it is | | certainly possible to misconfigure other virtualization environments in | | ways that would probably cause those symptoms. OTOH, it strikes me as | | more likely that the host system's packet filtering/redirection/NAT | software | | may be misconfigured. Xen doesn't yet run on the BSDs, AFAIK, so I'll | guess | | that it's running on a LINUX system of some flavor, so iptables is | probably | | the filtering package. Beyond that, I can't tell you much. Some of the | | LINUX users on this list ought to be able to give you some help in | figuring | | out whether the problem is with Xen or with the host system. | | | | | | Scott Bennett, Comm. ASMELG, CFIAG | | hi, | | a vif-bridge in Xen does, what it's name says: It bridges. So when your | domU has a 'proper' (plain standard seen from within the domU itself) IP | setup, there's no difference to a bare metal host. | | However, as I see, your problem's already fixed? | | Actually, it was Alexandru reporting the problem, not I, I know; sorry for my misleading eMail. I was responding to the thoughts WRT Xen. | but it's not | obvious that it is fixed. kyirong2 has been missing from the consensus | for quite a few hours now. I don't know whether that means he is trying | different Xen tricks, is working with his ISP, or some other possibility | that would leave his node down or unreachable for now. I came across the web page on the machine after I scanned it, to be honest. The results from this scan show a 'healthy' node regarding its network configuration (except one little thing that I will tell the TS), so it might be a routing issue (ISP) or an application problem. Best, Timo | Scott Bennett, Comm. ASMELG, CFIAG -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFKZXolfg746kcGBOwRAusqAJ9QpPp92OX8752nd3b12KZHW/8eiwCfUhO5 5lB8KIOFbfvYW/q7E27Eui4= =oLl/ -END PGP SIGNATURE-
Tor Exit Node Notice (was: Re: Re: My tor exit node is STILL gone from the node list)
Hi Timo, besides the routing stuff I saw that on the mentioned IP (see above) there's a nice disclaimer-like website that impresses me. I'm still not sure whether to pimp my node to be an exit node or not (due to the supressing that happens here in Germany). However, this suits me well. Is this a usual practice for TOR admins, and if yes, is there a multilingual approach? I basically got it from https://tor-svn.freehaven.net/svn/tor/trunk/contrib/tor-exit-notice.html and slightly modified the template. Feel free to use it. I don't know of any multilingual approaches, but I guess it would be nice to have that. -- Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro
My tor exit node is STILL gone from the node list
Hi list, I am still struggling to get my server back on the list of Tor nodes. For several months it was among the top 5 nodes, pumping 15TB a month. I am paying a lot of money for that machine, and I don't see why it just doesn't work any more. Let me reiterate what's happening: Since April, the node disappears from the node list after a few hours of running. I have tried to change exit policies, node name, node keys, ports and IP (within the same subnet). After the IP change the node was listed (and used) for several hours before it vanished. There's nothing about in the log file. 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? Information about the node: Current IP 89.248.169.109 (previously 89.248.169.108) Nickname kyirong2 (previously kyirong) Fingerprint D3EB 3132 99A0 082A 4A4E 10E0 EB75 8E4F 0163 F4F0 (Old fp: A8BD 32A9 C2F2 0C4F 8ED2 C26C E477 0A24 85E3 CD22) Tor 0.2.1.17-rc Debian DirPort 80, ORPort 8080 -- Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro
Re: My tor exit node is STILL gone from the node list
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
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.se...@blutmagie.de 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
RE: My tor exit node is STILL gone from the node list
Moria now thinks you are at 89.248.169.109 Traceroute and Netcat both fail from AS13285 in the UK: ... 8 openhosting-pp-1-thn.as13285.net (78.144.3.17) 34.393 ms 33.99 ms 63.96 ms 9 xe-2-3-0.bb1.ams1.nl.gbxs.net (193.27.64.81) 343.545 ms 73.367 ms 72.335 ms 10 * * * nc -v -w10 89.248.169.108 8080 89.248.169.108: inverse host lookup failed: Unknown server error (UNKNOWN) [89.248.169.108] 8080 (http-alt) : Operation timed out GD To: or-talk@freehaven.net Subject: My tor exit node is STILL gone from the node list From: t...@ze.ro Date: Mon, 20 Jul 2009 18:46:03 +0300 Hi list, I am still struggling to get my server back on the list of Tor nodes. For several months it was among the top 5 nodes, pumping 15TB a month. I am paying a lot of money for that machine, and I don't see why it just doesn't work any more. Let me reiterate what's happening: Since April, the node disappears from the node list after a few hours of running. I have tried to change exit policies, node name, node keys, ports and IP (within the same subnet). After the IP change the node was listed (and used) for several hours before it vanished. There's nothing about in the log file. 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? Information about the node: Current IP 89.248.169.109 (previously 89.248.169.108) Nickname kyirong2 (previously kyirong) Fingerprint D3EB 3132 99A0 082A 4A4E 10E0 EB75 8E4F 0163 F4F0 (Old fp: A8BD 32A9 C2F2 0C4F 8ED2 C26C E477 0A24 85E3 CD22) Tor 0.2.1.17-rc Debian DirPort 80, ORPort 8080 -- Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro _ NEW mobile Hotmail. Optimized for YOUR phone. Click here. http://windowslive.com/Mobile?ocid=TXT_TAGLM_WL_CS_MB_new_hotmail_072009
Re: My tor exit node is STILL gone from the node list
Lee schrieb: 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: oops, you're right! The same here. I didn't notice that before. Nevertheless blocking icmp at peering points is very unusual. Maybe path mtu discovery is broken if icmp is completely blocked. Olaf
Re: My tor exit node is STILL gone from the node list
On 7/20/09, downie - downgeo...@hotmail.com wrote: Moria now thinks you are at 89.248.169.109 Traceroute and Netcat both fail from AS13285 in the UK: Try netcat with the current address of 89.248.169.109 instead of .108 ..snip.. nc -v -w10 89.248.169.108 8080 89.248.169.108: inverse host lookup failed: Unknown server error (UNKNOWN) [89.248.169.108] 8080 (http-alt) : Operation timed out GD To: or-talk@freehaven.net Subject: My tor exit node is STILL gone from the node list From: t...@ze.ro Date: Mon, 20 Jul 2009 18:46:03 +0300 Hi list, I am still struggling to get my server back on the list of Tor nodes. For several months it was among the top 5 nodes, pumping 15TB a month. I am paying a lot of money for that machine, and I don't see why it just doesn't work any more. Let me reiterate what's happening: Since April, the node disappears from the node list after a few hours of running. I have tried to change exit policies, node name, node keys, ports and IP (within the same subnet). After the IP change the node was listed (and used) for several hours before it vanished. There's nothing about in the log file. 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? Information about the node: Current IP 89.248.169.109 (previously 89.248.169.108) Nickname kyirong2 (previously kyirong) Fingerprint D3EB 3132 99A0 082A 4A4E 10E0 EB75 8E4F 0163 F4F0 (Old fp: A8BD 32A9 C2F2 0C4F 8ED2 C26C E477 0A24 85E3 CD22) Tor 0.2.1.17-rc Debian DirPort 80, ORPort 8080 -- Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro _ NEW mobile Hotmail. Optimized for YOUR phone. Click here. http://windowslive.com/Mobile?ocid=TXT_TAGLM_WL_CS_MB_new_hotmail_072009
Re: My tor exit node is STILL gone from the node list
On 7/20/09, Olaf Selke olaf.se...@blutmagie.de wrote: Lee schrieb: 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: oops, you're right! The same here. I didn't notice that before. Nevertheless blocking icmp at peering points is very unusual. Maybe path mtu discovery is broken if icmp is completely blocked. No maybe about it - if icmp is completely blocked path mtu discovery _is_ broken. 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. Lee
RE: My tor exit node is STILL gone from the node list
Date: Mon, 20 Jul 2009 14:23:04 -0400 Subject: Re: My tor exit node is STILL gone from the node list From: ler...@gmail.com To: or-talk@freehaven.net On 7/20/09, downie - downgeo...@hotmail.com wrote: Moria now thinks you are at 89.248.169.109 Traceroute and Netcat both fail from AS13285 in the UK: Try netcat with the current address of 89.248.169.109 instead of .108 Oops - I guess I didn't copy the address when I thought I had. I can reach 89.248.169.109 ok. GD _ Windows Live™ Hotmail®: Celebrate the moment with your favorite sports pics. Check it out. http://www.windowslive.com/Online/Hotmail/Campaign/QuickAdd?ocid=TXT_TAGLM_WL_QA_HM_sports_photos_072009cat=sports
Re: My tor exit node is STILL gone from the node list
On Mon, 20 Jul 2009 18:34:27 +0200 Olaf Selke olaf.se...@blutmagie.de 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 I'm in northern Illinois (USA) about 60 miles west of Chicago on Comcast's network. Here's what I get: Script started on Mon Jul 20 14:33:03 2009 [hellas] 101 % traceroute -v 89.248.169.109 traceroute to 89.248.169.109 (89.248.169.109), 64 hops max, 40 byte packets 1 * * * 2 te-3-1-sr01.dekalb.il.chicago.comcast.net (68.86.115.133) 36 bytes to 68.57.205.126 90.772 ms 74.883 ms 41.637 ms 3 te-8-1-ur02.wchicago.il.chicago.comcast.net (68.87.230.125) 36 bytes to 68.57.205.126 13.959 ms 22.571 ms 9.445 ms 4 po-10-ur01.wchicago.il.chicago.comcast.net (68.87.230.109) 36 bytes to 68.57.205.126 9.799 ms 23.337 ms 23.484 ms 5 68.87.210.53 (68.87.210.53) 36 bytes to 68.57.205.126 13.377 ms 11.778 ms 55.350 ms 6 be-10-ar01.area4.il.chicago.comcast.net (68.87.229.109) 36 bytes to 68.57.205.126 28.540 ms 13.578 ms 31.751 ms 7 pos-1-12-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.53) 36 bytes to 68.57.205.126 139.361 ms 99.498 ms 105.380 ms 8 xe-2-1-0.chi10.ip4.tinet.net (77.67.68.37) 36 bytes to 68.57.205.126 90.902 ms 22.550 ms 14.896 ms 9 xe-0-0-0.ams10.ip4.tinet.net (89.149.186.233) 36 bytes to 68.57.205.126 115.629 ms xe-1-0-0.ams10.ip4.tinet.net (89.149.186.241) 36 bytes to 68.57.205.126 163.175 ms 118.991 ms 10 joint-transit-gw.ip4.tinet.net (77.67.72.30) 36 bytes to 68.57.205.126 116.769 ms 117.725 ms 120.046 ms 11 access.carrier.jointtransit.nl (213.207.0.245) 36 bytes to 68.57.205.126 135.225 ms 287.784 ms 138.462 ms 12 * * * 13 * 36 bytes from 193.11.161.132 to 68.57.205.126: icmp type 5 (Redirect) code 1 4: x2845 8: x00408061 12: x36750630 16: x7ecd3944 20: x56a10bc1 24: x59072923 28: x906ded12 32: x * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * ^C [hellas] 102 % exit exit Script done on Mon Jul 20 14:35:32 2009 I'm wondering why 193.11.161.132 (u193-11-161-132.studentnatet.se) is issuing the redirect. Why is the original routing going to Sweden? Trying traceroute from mp.cs.niu.edu, which is where I deal with email and is here in the same town (actually, it's only a few blocks away), I get: Script started on Mon Jul 20 14:48:31 2009 mp% traceroute -v 89.248.169.109 traceroute to 89.248.169.109 (89.248.169.109), 30 hops max, 40 byte packets 1 131-156-145-001.eng.niu.edu (131.156.145.1) 56 bytes to 131.156.145.41 0.845 ms 0.572 ms 0.415 ms 2 10.3.17.2 (10.3.17.2) 56 bytes to 131.156.145.41 0.501 ms 0.454 ms 0.372 ms 3 131-156-168-009.eng.niu.edu (131.156.168.9) 56 bytes to 131.156.145.41 0.387 ms 0.405 ms 0.390 ms 4 131-156-168-018.eng.niu.edu (131.156.168.18) 56 bytes to 131.156.145.41 0.516 ms 0.485 ms 0.483 ms 5 131.156.168.34 (131.156.168.34) 56 bytes to 131.156.145.41 2.577 ms 15.241 ms 2.407 ms 6 STATIC_86.240.220.206.gramtel.net (206.220.240.86) 56 bytes to 131.156.145.41 2.647 ms 2.646 ms 2.578 ms 7 so-1-3-0.0.rtr.newy32aoa.net.internet2.edu (64.57.28.15) 168 bytes to 131.156.145.41 30.226 ms 29.822 ms 30.046 ms 8 paix-ny.3-2.r1.ny.hwng.net (198.32.118.76) 56 bytes to 131.156.145.41 30.398 ms 29.754 ms 29.548 ms 9 1-1.r1.lo.hwng.net (69.16.191.50) 56 bytes to 131.156.145.41 100.471 ms 100.518 ms 109.836 ms 10 5-3.r3.lo.hwng.net (209.197.1.198) 56 bytes to 131.156.145.41 100.577 ms 112.211 ms 100.507 ms 11 5-2.r2.am.hwng.net (209.197.1.202) 56 bytes to 131.156.145.41 107.838 ms 107.886 ms 111.272 ms 12 5-1.r1.am.hwng.net (69.16.191.121) 56 bytes to 131.156.145.41 108.377 ms * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 ^Cmp% exit mp% script done on Mon Jul 20 14:51:27 2009 Best of luck getting your provider to straighten out the routing. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu *
Re: Re: My tor exit node is STILL gone from the node list
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. -- Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro
Re: Re: My tor exit node is STILL gone from the node list
On 7/20/09, Alexandru Cezar t...@ze.ro 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
Re: Re: My tor exit node is STILL gone from the node list
On Tue, 21 Jul 2009 00:03:10 +0300 Alexandru Cezar t...@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. I've never worked with Xen, so I can't answer that. However, it is certainly possible to misconfigure other virtualization environments in ways that would probably cause those symptoms. OTOH, it strikes me as more likely that the host system's packet filtering/redirection/NAT software may be misconfigured. Xen doesn't yet run on the BSDs, AFAIK, so I'll guess that it's running on a LINUX system of some flavor, so iptables is probably the filtering package. Beyond that, I can't tell you much. Some of the LINUX users on this list ought to be able to give you some help in figuring out whether the problem is with Xen or with the host system. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * **
Re: Re: My tor exit node is STILL gone from the node list
On 7/20/09, Alexandru Cezar t...@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.. 1094 ms92 ms93 ms te7-3.ccr01.lon01.atlas.cogentco.com [66.28.4.190] 1196 ms94 ms94 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] 1399 ms98 ms99 ms 149.6.129.22 1495 ms95 ms94 ms access.carrier.jointtransit.nl [213.207.0.245] 15 *** Request timed out. 1697 ms 101 ms96 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.. 1014 ms14 ms14 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] 1399 ms99 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 ms99 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
Re: Re: Re: My tor exit node is STILL gone from the node list
Hi Lee, Have you talked to your provider about reachability? Earlier I couldn't do a traceroute to your machine now I can: I haven't spoken to them, no. What I did was reconfigure the firewall to allow ICMP. Could it be momentarily routing problems that cause this? At the moment, the node seems to be, too. -- Alexandru -- - www.posta.ro - Romanias first free webmail since 1998! _ - powered by www.posta.ro
Re: Re: Re: My tor exit node is STILL gone from the node list
Hi Alexandru, On 7/20/09, Alexandru Cezar t...@ze.ro wrote: Hi Lee, Have you talked to your provider about reachability? Earlier I couldn't do a traceroute to your machine now I can: I haven't spoken to them, no. What I did was reconfigure the firewall to allow ICMP. Could it be momentarily routing problems that cause this? Yes, it would be routing problems. But it would be your provider that's having the routing problems; it's not because of anything you did/didn't do. Are you working now? http://moria.seul.org:9032/tor/status/authority says r kyirong2 0+sxMpmgCCpKThDg63WOTwFj9PA SdJCPHovwFEvv/p417iYV1Fdpgw 2009-07-20 23:20:39 89.248.169.109 8080 80 s Exit Fast Running V2Dir Valid opt v Tor 0.2.1.17-rc Regards, Lee
