Opened 8 years ago

Closed 4 years ago

#5327 closed defect (invalid)

Vidalia 0.3.1 reports changed external IP for TBB

Reported by: bastik Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version: Vidalia: 0.3.0-alpha
Severity: Normal Keywords:
Cc: bastik Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

On Windows 7 64bit, Vidalia 0.3.1 from "tor-browser-2.3.12-alpha-1_en-US" reports that the external IP has changed.

"External IP Address Changed - Tor has determined your relay's public IP address is currently [there was an IP] ([there was a name]). If that is not correct, please consider setting the 'Address' option in your relay's configuration."

The point is that Tor is running as a client, not as relay. It's true that there's a relay on the same system.

Child Tickets

Attachments (1)

vidalia.conf (734 bytes) - added by bastik 8 years ago.
TBB vidalia.conf

Download all attachments as: .zip

Change History (8)

comment:1 Changed 8 years ago by chiiph

Could you provide your vidalia.conf?

Changed 8 years ago by bastik

Attachment: vidalia.conf added

TBB vidalia.conf

comment:2 Changed 8 years ago by bastik

I added the unmodified vidalia.conf from TBB. I spotted Control Port 9051, but Vidalia (TBB) is set to "automatically")

Note that for the relay Vidalia's Control port is 9052. (Socks is 0)

comment:3 Changed 8 years ago by bastik

On the system in question are running three Vidalia instances and three Tor instances.

In order of launching.

1) Relay (Latest unstable bundle) launched as limited user
ControlPort 9052
Socks 0

2) Client (tor-browser-2.2.35-7.1_en-US) for IRC launched as limited user
ControlPort 9051
Socks 9050

3) Client (tor-browser-2.3.12-alpha-1_en-US) for browsing, limited user
ControlPort automatically
Socks automatically

I launched instance 3) before instance 2) a couple of times to see if the automatic port selection worked well with the browser. It did, but I needed a "stable" Socks Port for IRC and so I launched instance 2) before I re-launched instance 3)

Instance 1 was launched at 07:40 (local time) and only reported that it's running and that the ORPort is reachable. I'm getting Heartbeats every x hours (just like I set) My I has not changed since then.

Instance 2 was launched at 08:53 (local time) and reported at 15:26 that my IP has changed.

Instance 3 was launched at 08:54 and reported at 11:29 that my IP has changed. (This is the instance this ticket was about)

comment:4 Changed 8 years ago by bastik

I guess it's required to change the summary. (Not sure if I'm supposed to do that) This does not affect 0.3.1 alone. It's in 0.2.17 as well.

I might found a way to reproduce this. It's pretty easy.

How to reproduce:

  • Launch TBB
  • Click "settings"

When you look at the basic message log you'll see the notice. There's nothing in the advanced log. For me it appears in the same second as the settings open. Best noticed with the alpha bundle.

Note that the relay is running in my case. It's not good when I turn it down just for testing. I also assume that it does not matter.

comment:5 Changed 6 years ago by lunar

Keywords: Vidalia change o f IP address for client removed

remove useless keywords

comment:6 Changed 5 years ago by bastik

My set-up has changed since then. I have not been on IRC for ages now, so there's no Tor instance for that anymore. The bridge is still there and that comes with Vidalia on Windows.

For occasional Tor browsing I use TB, which ships without Vidalia. I'm not actually using Tor or TB, and don't have inspected the logs of TB.

Since everything is different now, with Vidalia no longer maintained and replaced (although not fully) is it not the best to close this ticket?

comment:7 Changed 4 years ago by bastik

Resolution: invalid
Severity: Normal
Status: newclosed

Vidalia is gone.

Note: See TracTickets for help on using tickets.