[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
IP changed, then...
- To: or-talk@xxxxxxxxxxxxx
- Subject: IP changed, then...
- From: Pei Hanru <peihanru@xxxxxxxxx>
- Date: Sat, 29 Apr 2006 20:20:50 +0800
- Delivered-to: email@example.com
- Delivered-to: firstname.lastname@example.org
- Delivered-to: email@example.com
- Delivery-date: Sat, 29 Apr 2006 08:21:02 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=oh9/3C8DfBZHTKleWtMXQyCbKX/EF/DXc7VXeTBMFPLbi5gF0FnNtwE9x42lWCsszeJYUI4C6veS9gZwU1YgT0vZTieRyr6b/1fh9XQzZl1PcyrV2DvWc2oAB4sj4kOydkhFLTUunok5v3q4V2eOgmckscfwqLLQgIXpflmNt28=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Thunderbird 220.127.116.11 (Windows/20060308)
I'm behind a NAT, running a Tor node. My ISP will unreasonably change my
IP every 48 hours. Usually Tor runs well, but when my IP changes, I will
get an entry in Tor log like this:
[notice] resolve_my_address(): Your IP seems to have changed. Updating.
[warn] second_elapsed_callback(): Your server (xxx.xxx.xxx.xxx:9001) has
not managed to confirm that its ORPort is reachable. Please check your
firewalls, ports, address, /etc/hosts file, etc.
The "[warn] second_elapsed_callback()..." is added to the log every 20
minutes and will lasts forever. By contrast, if I restart Tor, then it
[notice] Now checking whether ORPort xxx.xxx.xxx.xxx:9001 is
reachable... (this may take up to 20 minutes -- look for log messages
[notice] router_orport_found_reachable(): Self-testing indicates your
ORPort is reachable from the outside. Excellent. Publishing server
So, should I restart Tor manually every time when my IP changes? In FAQ,
I get an answer said no, but what's wrong here?