Tor 0.1.1.20 servers no longer handle dynamic IPs?
u-281 at vif.com
Fri Jun 23 18:38:55 UTC 2006
* Roger Dingledine (arma at mit.edu) wrote:
> On Thu, Jun 01, 2006 at 04:32:13PM -0400, Marcel wrote:
> > > I've gotten a report that Tor 0.1.1.20 does not -- when the IP address
> > > changes, Tor notices, but then it never finds itself reachable. Only
> > > restarting the process fixes it.
> > >
> > > Has anybody else experienced this? Or run servers on 0.1.1.20 successfully
> > > using dynamic IP adresses?
> > IMO every version i tried so far has this problem (dirport or orport
> > not reachable until restarted) and 1.1.20 is no exception. Sometimes it
> > works, sometimes not, even after a restart. I mean it may need several
> > restarts. Other times, it handles this just right. It's no big deal, as
> > eventually I'll notice it.
> > It happened for the last time may 27th. So I don't have the logs anymore.
> > Should you need further info, I'll be happy to help.
> For all those that are experiencing this, it would be great to get debug
> logs starting from when you start your Tor server, running Tor 0.1.1.20,
> until a ways after you find yourself reachable or several hours pass
I've manage to control tor via /etc/ppp/ip-up.d and /etc/ppp/id-down.d on
debian sarge instead of /etc/init.d and so far the problem seems gone.
test -e /etc/init.d/tor2 && /etc/init.d/tor2 start
test -e /etc/init.d/torclient2 && /etc/init.d/torclient2 start
test -e /etc/init.d/tor2 && /usr/bin/killall /usr/sbin/tor
/etc/init.d/tor2 is simply /etc/init.d/tor renamed for not to start on
Jun 23 14:16:39.978 [err] signal_callback(): Catching signal TERM, exiting
Jun 23 14:16:49.637 [notice] Tor 0.1.1.21 opening log file.
Jun 23 14:17:03.314 [notice] resolve_my_address(): Your IP seems to have
Jun 23 14:17:03.388 [notice] Your Tor server's identity key fingerprint is
'GingkoBiloba 4569 0E95 E940 383B 0666 077C 7675 D60D F8D9 361E'
Jun 23 14:17:03.388 [notice] accounting_set_wakeup_time(): Configured
hibernation. This interval began at 2006-06-23 11:04:00; the
scheduled wake-up time was 2006-06-23 11:04:00; we expect to exhaust our
quota for this interval around 2006-06-24 11:04:00; the next interval
begins at 2006-06-24 11:04:00 (all times local)
Jun 23 14:17:46.051 [notice] We now have enough directory information to
Jun 23 14:17:51.211 [notice] Tor has successfully opened a circuit. Looks
like client functionality is working.
Jun 23 14:17:51.211 [notice] Now checking whether ORPort
18.104.22.168:19001 and DirPort 22.214.171.124:19030 are reachable... (this
may take up to 20 minutes -- look for log messages indicating success)
Jun 23 14:18:19.457 [notice] router_dirport_found_reachable(): Self-testing
indicates your DirPort is reachable from the outside. Excellent.
Jun 23 14:19:04.464 [notice] router_orport_found_reachable(): Self-testing
indicates your ORPort is reachable from the outside. Excellent. Publishing
I hope this will help users with dyn IP.
More information about the tor-talk