<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR>
<STYLE>@font-face {
font-family: 宋体;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: @宋体;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
LI.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
DIV.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: Verdana; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
UNKNOWN {
FONT-SIZE: 10pt
}
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="FONT-SIZE: 10pt; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana size=2>
<DIV><FONT face=Verdana size=2><SPAN>Hi Scott Bennett</SPAN>,</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV style="TEXT-INDENT: 2em">Thanks for your kind reply. I agree with your
deduction that the possibility you
mentioned that inside tor somewhere that causes tor to forget to post a descriptor update after the usual 18 hours have
elapsed. I will read the source code about it.</DIV>
<DIV style="TEXT-INDENT: 2em"> </DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT face=Verdana size=2></DIV></FONT></FONT><FONT face=Verdana
color=#000080 size=2><FONT color=#000000></FONT>
<HR>
</FONT></DIV></DIV>
<DIV><FONT face=Verdana size=2><STRONG>发件人：</STRONG> Scott Bennett </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>发送时间：</STRONG> 2009-06-04 18:10:32
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>收件人：</STRONG> lingzhen1982; or-talk
</FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>抄送：</STRONG> </FONT></DIV>
<DIV><FONT face=Verdana size=2><STRONG>主题：</STRONG> Re: My exit node is gone
from the node list </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>
<DIV> On Thu, 4 Jun 2009 11:55:28 +0800 "lingzhen1982" <lingzhen1982@gmail.com></DIV>
<DIV>wrote:</DIV>
<DIV>>For several months, I've been running a tor exit node (Nickname: AllenHomeTor, IP address: 98.216.176.128, Version:0.2.0.30(r15956)). Since a few days, it seems to have vanished from the list of nodes. And I try to make it reappear by using a new nickname AllenUSATor(fingerprint: 443E 035C B856 5904 AE98 8DAB 3059 9A0D 2C4C 340C), but I am failed. How can I make it reappear? </DIV>
<DIV></DIV>
<DIV> First, you should not be running that version of tor. Currently valid</DIV>
<DIV>versions in the stable branch are 0.2.0.33 and 0.2.0.34 for both clients and</DIV>
<DIV>relays.</DIV>
<DIV> Second, when tor starts up, does it issue a message that says that your</DIV>
<DIV>node is reachable from outside? If not, then you probably have a NAT/RDR</DIV>
<DIV>problem to settle with your gateway.</DIV>
<DIV> Third, if tor does find itself reachable soon after startup, does it ever</DIV>
<DIV>issue a message that says its IP address appears to have changed? Or that its</DIV>
<DIV>DNS queries appear to be hijacked? In the former case tor should, after</DIV>
<DIV>passing another reachability test, simply publish a new descriptor bearing the</DIV>
<DIV>new IP address. In the latter case, tor should stop operating as an exit and</DIV>
<DIV>issue a message to that effect, while continuing to operate as a non-exit</DIV>
<DIV>relay.</DIV>
<DIV></DIV>
<DIV>>In addtion, my traffic logs suggest that the node is used as much as it could be. There are much traffic like BitTorrent. I am confused. How can these guys select my exit node even my node has vanished from the list of nodes? BTW, to avoid too much BitTorrent traffic, I change my exit policy to only accept port 80 now.</DIV>
<DIV></DIV>
<DIV> How can you tell what sort of traffic it is if your node is no longer an</DIV>
<DIV>exit node? Why close all those other non-Bittorrent ports as well?</DIV>
<DIV></DIV>
<DIV>>I look forward from your feedback, and thank all responders in advance.</DIV>
<DIV></DIV>
<DIV> There remains another possibility. As several of us have reported here</DIV>
<DIV>in the past, there has been a gremlin lurking inside tor somewhere that causes</DIV>
<DIV>tor to forget to post a descriptor update after the usual 18 hours have</DIV>
<DIV>elapsed. I haven't yet seen it happen with 0.2.1.14-rc, but it was a headache</DIV>
<DIV>with some earlier versions. However, when you changed your torrc, whether for</DIV>
<DIV>the change of nickname and identifier or for the change of exit policy, tor</DIV>
<DIV>should still have published a new descriptor reflecting either of those</DIV>
<DIV>changes, so the authorities ought to have a new descriptor for at least another</DIV>
<DIV>18 hours. Try upgrading to a current version of tor, and then check it a</DIV>
<DIV>couple of times a day (or more often if you like) for a while to see whether</DIV>
<DIV>the problem recurs.</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV> Scott Bennett, Comm. ASMELG, CFIAG</DIV>
<DIV>**********************************************************************</DIV>
<DIV>* Internet: bennett at cs.niu.edu *</DIV>
<DIV>*--------------------------------------------------------------------*</DIV>
<DIV>* "A well regulated and disciplined militia, is at all times a good *</DIV>
<DIV>* objection to the introduction of that bane of all free governments *</DIV>
<DIV>* -- a standing army." *</DIV>
<DIV>* -- Gov. John Hancock, New York Journal, 28 January 1790 *</DIV>
<DIV>**********************************************************************</DIV></FONT></DIV></BODY></HTML>