[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Tor server not seen

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Tor server not seen
From: phobos@xxxxxxxxxx
Date: Tue, 17 Jul 2007 16:08:15 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Tue, 17 Jul 2007 16:08:23 -0400
In-reply-to: <469D0C05.6040402@xxxxx>
Mail-followup-to: or-talk@xxxxxxxxxxxxx
References: <20070709091654.GA22071@xxxxxxxxxx> <20070711075036.GD19777@xxxxxxxxxxxx> <20070711085513.GB5074@xxxxxxxxxx> <20070712195840.GD3513@xxxxxxxxxxxx> <469D0C05.6040402@xxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.4.1i

On Tue, Jul 17, 2007 at 08:35:49PM +0200, jszymona@xxxxx wrote 1.1K bytes in 30 lines about:
: Jul 17 14:08:22.871 [notice] Our IP Address has changed from
: 83.28.31.108 to 83.28.4.122; rebuilding descriptor.
: Jul 17 14:09:33.150 [notice] eventdns: Nameserver 192.168.1.1 is back up
: Jul 17 14:28:22.151 [warn] Your server (83.28.4.122:9001) has not
: managed to confirm that its ORPort is reachable. Please check your
: firewalls, ports, address, /etc/hosts file, etc.
: [...]

Your server isn't reachable from the outside world is the first problem.
A tcptraceroute to port 9001 stops at do.lub-ru2.z.lub-r1.tpnet.pl
(212.160.0.22).  As far as I can tell, no traffic is allowed inbound
past that point.

-- 
Andrew

Follow-Ups:
- Re: Tor server not seen
  - From: Przemyslaw Orzechowski

References:
- New Torbutton (1.1.4-alpha)
  - From: Mike Perry
- Re: New Torbutton (1.1.4-alpha)
  - From: Jens Kubieziel
- Re: New Torbutton (1.1.4-alpha)
  - From: Mike Perry
- Re: New Torbutton (1.1.4-alpha)
  - From: Jens Kubieziel
- Tor server not seen
  - From: jszymona

Prev by Author: Re: two unseemly tor behaviors
Next by Author: Re: Blocking child pornography exits
Previous by thread: Tor server not seen
Next by thread: Re: Tor server not seen
Index(es):
- Author
- Thread