Opened 5 years ago

Closed 5 years ago

#13537 closed defect (fixed)

Unexpected behaviour of Tor v0.2.5.8-rc embedded with vidalia v0.2.21

Reported by: TORqueue Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Archived/Vidalia Version: Tor: 0.2.5.8-rc
Severity: Keywords: vidalia v0.2.21
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

What's going wrong with Tor v0.2.5.8-rc embedded with vidalia v0.2.21?

I started a new non-exit relay 'TORqueue 64C5E87A73C8B5FE0FE02DFB51D83BEC24131EC7' on Windows XP, using Tor v0.2.5.8-rc (from TBB v4.0) embedded with vidalia v0.2.21.

Because I am behind a router (UPnP enabled), I forwarded ORport 443 and DIRport 9030.
I have firewall permissions for ports 80 TCP, 443 TCP/UDP, 9030 TCP/UDP, 9050 TCP/UDP and 9151 TCP - tor.exe is pointed also to the Windows firewall.

vidalia shows my relay is connected and online for at least 12 hours, but 'TORqueue' relay is not show in vidalia's tor network map - atlas and consensus show also my relay is offline.

Oct 22 02:37:55.656 [Notice] Tor v0.2.5.8-rc (git-cc2477cc002ac542) running on Windows XP with Libevent 2.0.21-stable, OpenSSL 1.0.1i and Zlib 1.2.8.
Oct 22 02:37:55.656 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Oct 22 02:37:55.656 [Notice] Read configuration file "...\Data\Tor\torrc".
Oct 22 02:37:55.765 [Notice] Based on detected system memory, MaxMemInQueues is set to 2048 MB. You can override this by setting MaxMemInQueues by hand.
Oct 22 02:37:55.765 [Notice] Opening Socks listener on 127.0.0.1:9050
Oct 22 02:37:55.765 [Notice] Opening Control listener on 127.0.0.1:9151
Oct 22 02:37:55.765 [Notice] Opening OR listener on 0.0.0.0:443
Oct 22 02:37:55.765 [Notice] Opening Directory listener on 0.0.0.0:9030
Oct 22 02:37:55.984 [Notice] Parsing GEOIP IPv4 file ...\Data\Tor\geoip.
Oct 22 02:38:08.343 [Notice] Parsing GEOIP IPv6 file ...\Data\Tor\geoip6.
Oct 22 02:38:08.343 [Notice] Your Tor server's identity key fingerprint is 'TORqueue 64C5E87A73C8B5FE0FE02DFB51D83BEC24131EC7'
Oct 22 02:38:08.343 [Notice] Bootstrapped 0%: Starting
Oct 22 02:38:08.343 [Notice] We now have enough directory information to build circuits.
Oct 22 02:38:08.343 [Notice] Bootstrapped 80%: Connecting to the Tor network
Oct 22 02:38:08.343 [Notice] New control connection opened from 127.0.0.1.
Oct 22 02:38:08.343 [Notice] New control connection opened from 127.0.0.1.
Oct 22 02:38:08.343 [Notice] New control connection opened from 127.0.0.1.
Oct 22 02:38:08.343 [Notice] Guessed our IP address as 109.103.57.102 (source: 208.83.223.34).
Oct 22 02:38:08.343 [Notice] Bootstrapped 85%: Finishing handshake with first hop
Oct 22 02:38:08.343 [Notice] Bootstrapped 90%: Establishing a Tor circuit
Oct 22 02:38:08.812 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Oct 22 02:38:08.812 [Notice] Bootstrapped 100%: Done
Oct 22 02:38:08.812 [Notice] Now checking whether ORPort 109.103.57.102:443 and DirPort 109.103.57.102:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Oct 22 02:38:09.609 [Notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Oct 22 02:38:10.171 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Oct 22 02:38:13.359 [Notice] Performing bandwidth self-test...done.

This info is repeated indefinitely

Oct 22 02:41:11.000 [Info] resolve_my_address(): Guessed local hostname 'ophchsso-5ade13' resolves to a private IP address (192.168.100.2). Trying something else.
Oct 22 02:41:11.000 [Info] resolve_my_address(): Interface IP address '192.168.100.2' is a private address too. Ignoring.
Oct 22 02:41:11.000 [Info] resolve_my_address(): Address 'ophchsso-5ade13' resolves to private IP address '192.168.100.2'. Tor servers that use the default DirAuthorities must have public IP addresses.
Oct 22 02:41:11.000 [Info] router_pick_published_address(): Could not determine our address locally. Checking if directory headers provide any hints.
Oct 22 02:41:11.000 [Info] router_pick_published_address(): Success: chose address '109.103.57.102'.

When I exit from vidalia and the relay is closed on my PC, atlas and consensus show my relay is online. I don't understand what is going wrong here.

The previous version TBB v3.6.6 worked fine with vidalia v0.2.21 and my old non-exit relay worked as I expected.

For more details and pics look here http://torforum.org/viewtopic.php?f=4&t=21603

Any suggestion to fix this?

Child Tickets

Attachments (6)

vidalia screenshot.jpg (656.6 KB) - added by TORqueue 5 years ago.
vidalia screenshot.jpg
vidalia version.jpg (50.7 KB) - added by TORqueue 5 years ago.
vidalia version.jpg
atlas.jpg (178.9 KB) - added by TORqueue 5 years ago.
atlas.jpg
consensus.jpg (174.2 KB) - added by TORqueue 5 years ago.
consensus.jpg
hSF5gj7hv.jpg (117.4 KB) - added by TORqueue 5 years ago.
hSF5gj7hv.jpg
powergenerator.jpg (123.8 KB) - added by TORqueue 5 years ago.
powergenerator.jpg

Download all attachments as: .zip

Change History (12)

Changed 5 years ago by TORqueue

Attachment: vidalia screenshot.jpg added

vidalia screenshot.jpg

Changed 5 years ago by TORqueue

Attachment: vidalia version.jpg added

vidalia version.jpg

Changed 5 years ago by TORqueue

Attachment: atlas.jpg added

atlas.jpg

Changed 5 years ago by TORqueue

Attachment: consensus.jpg added

consensus.jpg

comment:1 Changed 5 years ago by teor

How many instances of tor.exe do you have running?
When vidalia is running?
When it's not?

comment:2 in reply to:  1 Changed 5 years ago by TORqueue

Replying to teor:

How many instances of tor.exe do you have running?
When vidalia is running?
When it's not?

A single instance of tor.exe started by vidalia
When vidalia is closed, tor.exe is closed also (checked in task manager)

Last edited 5 years ago by TORqueue (previous) (diff)

comment:3 Changed 5 years ago by teor

That is strange behaviour from the consensus.
How many relays are running on that public IP?
Are there or have there ever been relays with that name?

It may be that tor is incorrectly reporting uptime and downtime, but otherwise working. It's hard to tell.

comment:4 in reply to:  3 Changed 5 years ago by TORqueue

Replying to teor:

That is strange behaviour from the consensus.
How many relays are running on that public IP?
Are there or have there ever been relays with that name?

It may be that tor is incorrectly reporting uptime and downtime, but otherwise working. It's hard to tell.

The name of relay is unique.
I had old non-exit relays last week with other names (for testing purpose) on my public IP 109.103.57.102 (PowerGeneraTOR 0D00E088F4E863A338A977298F327E33A1A9EBE8 and hSF5gj7hv 731ED282BC64E828D97E9FD7ADA03873F5A784BC) and is ridiculous atlas shows these deleted relays are still online ;-)

https://atlas.torproject.org/#details/0D00E088F4E863A338A977298F327E33A1A9EBE8
https://atlas.torproject.org/#details/731ED282BC64E828D97E9FD7ADA03873F5A784BC

I had running for months an old non-exit relay on other public IP (hSF5gj7hv), but I changed my ISP and I lost the old TOR DATA files.

I also tweaked my TBB v4.0 for increase the annonimity on WEB

On the Embeddings tab check Forbid Java, Forbid adobe flash, Forbid microsoft silverlight, Forbid other plugins, Forbid <AUDIO> / <VIDEO>, Forbid <IFRAME>, Forbid <FRAME>, Forbid @font-face. Check "ask for confirmation..." and click Okay.

about:config

javascript.enabled			false
network.http.sendRefererHeader		0
network.http.sendSecureXSiteReferrer	false
extensions.torbutton.saved.sendSecureXSiteReferrer	false
network.cookie.cookieBehavior		2
browser.cache.memory.enable		false

I have these extra settings in my torrc

AvoidDiskWrites 1
ORPort 443
DirPort 9030
SocksPort 9050
ControlPort 9151
RelayBandwidthBurst 4194304
RelayBandwidthRate 3145728
SafeSocks 1
TestSocks 1
NewCircuitPeriod 10
CircuitBuildTimeout 30
Address

Now it looks my new non-exit relay (3 MB/s up to 4 MB/s) is useless.

Last edited 5 years ago by TORqueue (previous) (diff)

Changed 5 years ago by TORqueue

Attachment: hSF5gj7hv.jpg added

hSF5gj7hv.jpg

Changed 5 years ago by TORqueue

Attachment: powergenerator.jpg added

powergenerator.jpg

comment:5 Changed 5 years ago by TORqueue

It looks that changing the default ORport 443 and DIRport 9030 to some random ports does the trick and now I can see my relay running at https://atlas.torproject.org and https://torstatus.rueckgr.at/

comment:6 Changed 5 years ago by TORqueue

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.