[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
quick question about my bridge relay...
- To: or-talk <or-talk@xxxxxxxxxxxxx>
- Subject: quick question about my bridge relay...
- From: Joseph Lorenzo Hall <joehall@xxxxxxxxx>
- Date: Mon, 31 Jan 2011 09:26:33 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Mon, 31 Jan 2011 09:26:40 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ayhLG1lxlXHdXX7CZObwI7Uv4y8KD0x3IJ1/VJiFzew=; b=YmJMSv4pTSxTSOs9nxbBRR5bazpHucuCp3SriZngcCXXNI9xr7+4pJzSEjmwDg/GKu tljYW9Hb5JP+PtMe3ND49t46BAHCtF6krlV+2Wlvv2ctqiuPinVzBM3TvtG+t0nPwQrA 94sZv672dFfHobvDoIStGm6Au03rkxvw/yUSM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fITQPgvmB6n+IwoOmGZ0OT82FlbaOh3lkus6KBUii6RdUVKYUnrtWolNt6AD7KNsl2 L3G2r07WGykloRoRe2Q4kxfxVBDOsNLWYvYZabEYfSvVHXxd6GXp6QZwO+X/nYyvs/KI GUqJJhw7V/I5Wi2nY7Wk+tGzxRZ1ie953Nbc4=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
(I've redacted my IP address and relay name and fingerprint here.)
I've set up a bridge relay and it seems to work for a bit and then
stop routing traffic. I'm wondering if I've misconfigured it or
The box running it is behind a NAT and I've port-forwarded to the
Relay Port and Directory Port (I'm using the 0.2.2.22-alpha for OS X
Power PC via Vidalia).
Looking at the logs, I see this frequently:
Jan 31 08:54:39.925 [Info] resolve_my_address(): Guessed local
hostname 'foo.local' resolves to a private IP address (10.0.1.2).
Trying something else.
Jan 31 08:54:39.943 [Info] get_interface_address6(): connect() failed:
Jan 31 08:54:39.947 [Info] resolve_my_address(): Could not get local
interface IP address. Too bad.
Jan 31 08:54:39.950 [Info] resolve_my_address(): Address
'tarantula.local' resolves to private IP address '10.0.1.2'. Tor
servers that use the default DirServers must have public IP addresses.
However, if I simply click on "Setup Relaying" in Vidalia control
panel and just click "OK" in the sharing pane (to not change
anything), it seems to start routing traffic again:
Jan 31 08:52:25.245 [Notice] Your Tor server's identity key
fingerprint is 'foo xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
Jan 31 08:52:25.248 [Info] configure_nameservers(): No change to
Jan 31 08:52:36.232 [Info] connection_ap_make_link(): Making internal
anonymized tunnel to [scrubbed]:443 ...
Jan 31 08:52:36.235 [Info] onion_pick_cpath_exit(): Using requested
exit node 'Tonga'
Jan 31 08:52:36.239 [Info] circuit_send_next_onion_skin(): First hop:
finished sending CREATE cell to 'TolFuin'
Jan 31 08:52:36.242 [Info] connection_ap_make_link(): ... application
connection created and linked.
It goes along happily at least for a few minutes, but then goes back
to the first sequence above and doesn't seem to handle any more
traffic (until I click through the setup relaying pane in settings).
And at other times, it does seems to guess my public IP address
correctly after the first sequence I quote above:
Jan 31 08:52:25.238 [Info] router_pick_published_address(): Could not
determine our address locally. Checking if directory headers provide
Jan 31 08:52:25.241 [Info] router_pick_published_address(): Success:
chose address 'xxx.xxx.xxx.xxx'.
So, I guess I'm wondering how do I tell Tor what my public IP address
is? (I maybe completely misunderstanding the problem here, of
best and thanks, Joe
Joseph Lorenzo Hall
ACCURATE Postdoctoral Research Associate
UC Berkeley School of Information
Princeton Center for Information Technology Policy
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/