Hi, again!
I postet a similar question a few time ago but the problem still
exists and i found no reason for that behavior, maybe someone else
can make my mind clear?
My Tor-server is behind a firewall in my internal net.
The firewall (a devil-linux based system) keep also track
of my broadband connection.
After 24 hours my connection is interrupted by my isp as usual.
This also happened today:
-->Oct 11 18:25:54 src@www pppd[3732]: Connect time 1440.1 minutes.
-->Oct 11 18:25:54 src@www pppd[3732]: Sent 2071180493 bytes, received 1595348321 bytes.
-->Oct 11 18:25:54 src@www divert: no divert_blk to free, ppp0 not ethernet
-->Oct 11 18:25:54 src@www pppd[3732]: Exit.
-->Oct 11 18:25:54 src@www adsl-connect: ADSL connection lost; attempting re-connection.
-->Oct 11 18:25:59 src@www pppd[4308]: pppd 2.4.2 started by
-->Oct 11 18:25:59 src@www divert: not allocating divert_blk for non-ethernet device ppp0
-->Oct 11 18:25:59 src@www pppd[4308]: Using interface ppp0
-->Oct 11 18:25:59 src@www pppd[4308]: Connect: ppp0 <--> /dev/pts/0
-->Oct 11 18:26:00 src@www pppoe[4309]: PADS: Service-Name: ''
-->Oct 11 18:26:00 src@www pppoe[4309]: PPP session is 1387
-->Oct 11 18:26:03 src@www pppd[4308]: CHAP authentication succeeded
-->Oct 11 18:26:03 src@www pppd[4308]: local IP address 80.171.xxx.xxx
-->Oct 11 18:26:03 src@www pppd[4308]: remote IP address 213.191.xxx.xxx
As you can see at 18:26:03 i have a new ip!
But my Tor-server(0.1.1.7-alpha) could not be reached correctly by the
Dir-Servers since then.
-->Oct 11 18:30:55.912 [notice] conn_close_if_marked(): Something wrong with your network connection?
-->Conn (addr [scrubbed], fd 130, type Directory, state 6) tried to write 182753 bytes but timed out. (Marked at main.c:586)
ThatŽs ok for a few minutes, but should not be at 20:44 local time!
-->Oct 11 20:44:43.518 [info] connection_or_finished_connecting(): OR connect() to router at 18.244.0.188:9001 finished.
-->Oct 11 20:44:43.522 [info] connection_or_finished_connecting(): OR connect() to router at 18.244.0.114:443 finished.
-->Oct 11 20:44:43.953 [info] TLS error: unexpected close while reading
-->Oct 11 20:44:43.953 [info] connection_read_to_buf(): tls error. breaking (nickname moria1, address 18.244.0.188).
-->Oct 11 20:44:43.954 [info] conn_close_if_marked(): Cleaning up connection (fd -1).
-->Oct 11 20:44:43.954 [info] connection_remove(): removing socket -1 (type OR), nfds now 16
-->Oct 11 20:44:44.070 [info] TLS error: unexpected close while reading
-->Oct 11 20:44:44.070 [info] connection_read_to_buf(): tls error. breaking (nickname moria2, address 18.244.0.114).
-->Oct 11 20:44:44.071 [info] conn_close_if_marked(): Cleaning up connection (fd -1).
-->Oct 11 20:44:44.071 [info] connection_remove(): removing socket -1 (type OR), nfds now 15
-->Oct 11 20:44:44.397 [info] retry_listeners(): Already have OR listener on 0.0.0.0:9001
-->Oct 11 20:44:44.397 [info] retry_listeners(): Already have Directory listener on 0.0.0.0:9030
-->Oct 11 20:44:44.398 [info] retry_listeners(): Already have Socks listener on 127.0.0.1:9050
-->Oct 11 20:45:46.007 [info] retry_listeners(): Already have OR listener on 0.0.0.0:9001
-->Oct 11 20:45:46.007 [info] retry_listeners(): Already have Directory listener on 0.0.0.0:9030
-->Oct 11 20:45:46.008 [info] retry_listeners(): Already have Socks listener on 127.0.0.1:9050
..and a lot more messages like that
When i send HUP to my Tor-server everything works fine again!
Can anyone explain how Tor finds my server normaly, when my ip has changed?
-->Oct 11 21:16:11.749 [notice] Received sighup. Reloading config.
-->Oct 11 21:16:11.953 [notice] resolve_my_address(): Your IP seems to have changed. Updating.
-->Oct 11 21:16:11.992 [notice] Tor 0.1.1.7-alpha opening log file.
-->Oct 11 21:16:11.993 [notice] accounting_set_wakeup_time(): Configured hibernation. This interval began at 2005-10-11 12:00:00; the scheduled wake-up time was 2005-10-11 12:00:00; we expect to exhaust our quota for this interval around 2005-10-12 12:00:00; the next interval begins at 2005-10-12 12:00:00 (all times local)
-->Oct 11 21:16:54.239 [notice] Tor has successfully opened a circuit. Looks like it's working.
-->Oct 11 21:16:54.240 [notice] Now checking whether ORPort 80.171.xxx.xxx:9001 and DirPort 80.171.xxx.xxx:9030 are reachable... (this may take several minutes)
-->Oct 11 21:17:39.904 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Thanks for your help
Oliver