<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 6, 2010, at 6:01 PM, Mick wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>"Justin Aplin" <<a href="mailto:jmaplin@ufl.edu">jmaplin@ufl.edu</a>> wrote:<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">Since I don't see etherape on <a href="https://torstatus.blutmagie.de">https://torstatus.blutmagie.de</a> I'm <br></blockquote><blockquote type="cite">assuming your relay is either configured as a bridge, or you've turned </blockquote></div></blockquote><blockquote type="cite"><div><blockquote type="cite">it off. Either way, let it run interrupted for a few days and see what </blockquote><blockquote type="cite">happens.<br></blockquote><font class="Apple-style-span" color="#006312"><br></font>Etherape is a network monitoring tool, not the name of the relay.<br><br>Mick<br></div></blockquote><br></div><div>My bad. In that case, same advice, with the added suggestion to check and see if your relay is showing up in the statuses (assuming the node isn't configured as a bridge). Since Tor is publishing a server descriptor, though, I don't really think that's the issue here.</div><div><br></div><div>~Justin Aplin</div><div><br></div><br></body></html>