Tor-server and dyndns Problems!

[Oliver Niesner <digi_news@xxxxxx>]

Dear, all

After problems with telling Tor that my server-IP has changed, i 
followed the suggestion of Peter Palfrader and installed the actual
CVS version. Peter told me that this version has better handling with
dynamic ip checking.
But unfortunately it seems not work very well, here some snippets from 
my logfiles:

Yesterday my IP changed to:

> Oct 18 18:27:20 src@www pppd[7319]: CHAP authentication succeeded
> Oct 18 18:27:21 src@www pppd[7319]: local  IP address xxx.xxx.133.10  <--this is the correct IP!! 
> Oct 18 18:27:21 src@www pppd[7319]: remote IP address xxx.xxx.84.197

Tor recognizes this:

> Oct 18 18:28:00.489 [notice] resolve_my_address(): Your IP seems to have changed. Updating.
> Oct 18 18:29:00.298 [notice] Tried for 60 seconds to get a connection to [scrubbed]:9030. Giving up.
> Oct 18 18:30:01.996 [notice] Tried for 60 seconds to get a connection to [scrubbed]:9030. Giving up.
> Oct 18 18:31:03.767 [notice] Tried for 60 seconds to get a connection to [scrubbed]:9030. Giving up.
> Oct 18 18:31:40.373 [notice] Tor has successfully opened a circuit. Looks like it's working.
> Oct 18 18:31:40.373 [notice] Now checking whether ORPort 80.171.230.159:9001 and DirPort 80.171.230.159:9030 are reachable... (this may take several minutes)
> Oct 18 18:31:55.356 [notice] connection_ap_expire_beginning(): Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Oct 18 18:31:55.357 [notice] circuit_log_path(): exit circ (length 3): Pegdymmiv2(open) aaf9200ab4053a5d19c(open) moria2(open)
> Oct 18 18:32:04.496 [notice] Tried for 60 seconds to get a connection to [scrubbed]:9030. Giving up.
> Oct 18 18:33:05.206 [notice] Tried for 60 seconds to get a connection to [scrubbed]:9030. Giving up.
> Oct 18 18:33:41.305 [warn] check_descriptor_ipaddress_changed(): Our IP Address seems to be flapping.  

It has changed twice within one hour (from 80.171.230.159 to 
xxx.xxx.133.10 this time).  Ignoring for now.

Why it is ignoring my new IP? As you can see the xxx.xxx.133.10 is the 
correct one but it is ignored!

Tor now try to use still the old and not updated IP
> Oct 18 20:08:00.075 [warn] Your server (80.171.230.159:9001) has not managed to confirm that its ORPort is reachable. Please
> check your firewalls, ports, address, /etc/hosts file, etc.
> Oct 18 20:08:00.075 [warn] Your server (80.171.230.159:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
> Oct 18 20:09:59.583 [notice] connection_ap_expire_beginning(): Stream is 15 seconds late on address '[scrubbed]'. Retrying.

...and again

> Oct 18 21:36:07.718 [warn] check_descriptor_ipaddress_changed(): Our IP Address seems to be flapping.  
It has changed twice within one hour (from 80.171.230.159 to 
xxx.xxx.133.10 this time).  Ignoring for now.

> Oct 19 06:54:13.354 [warn] Your server (80.171.230.159:9030) has not managed to confirm that its DirPort is reachable. 
Please check your firewalls, ports, address, /etc/hosts file, etc.

Today in the morning i checked the log and i send a HUP to my tor and
it works:

> Oct 19 10:14:16.969 [notice] Received sighup. Reloading config.
> Oct 19 10:14:17.000 [warn] expand_abbrev(): The configuration option 'SocksBindAddress' is deprecated; use 'SocksListenAddress' instead.
> Oct 19 10:14:17.156 [notice] Tor 0.1.1.8-alpha-cvs opening log file.
> Oct 19 10:14:17.157 [notice] accounting_set_wakeup_time(): Configured hibernation.  This interval began at 2005-10-18 12:00:00; the scheduled wake-up time was 2005-10-18 12:06:03; we expect to exhaust our quota for this interval around 2005-10-19 11:59:03; the next interval begins at 2005-10-19 12:00:00 (all times local)
> Oct 19 10:14:53.343 [notice] Tor has successfully opened a circuit. Looks like it's working.
> Oct 19 10:14:53.343 [notice] Now checking whether ORPort xxx.xxx.133.10:9001 and DirPort xxx.xxx.133.10:9030 are reachable... (this may take several minutes)
> Oct 19 10:14:55.041 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.

Maybe someone can help me to solve the problem.
I think it is not very elegant to HUP my Tor-server every 24 hours by 
cron or similar things.
I also could not understand why Tor "thinks" that my ip has changed 
twice in one hour and ignoring the correct IP.
Hope that someone can help me to keep my Tor-server up 24/7!
Maybe it helps if someone can explain how exactly Tor finds the correct 
IP of a server?

Thanks a lot

Olli