Opened 5 years ago

Last modified 2 years ago

#15302 needs_information defect

Tor browser doesn't recognize change of network interface which provides internet

Reported by: krichter Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When there're two network interface available which both provide internet access and one connection is dropped (cable unplugged) and the other is established, Tor browser uses 100 % of one CPU core until the connection times out (after ~2 minutes). It only succeeds randomly to recognize the new connection. firefox 36.0.1 has no problem dealing with that situation.

experienced with Tor browser 4.0.4 on Ubuntu 14.10 amd64 with Linux 3.19.1

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by gk

Status: newneeds_information

And how does that look like for Firefox 36.0.1 which is using Tor? Or are you already talking about that case? How about plain Firefox 31 (with and without Tor)?

comment:2 Changed 5 years ago by krichter

firefox 36.0.1 has no problem dealing with that situation.

I'm not using firefox 36.0.1 with tor(button). I meant that sentence as a reference to a non-tor-related software which relies on internet connection and works in order to exclude some possible causes (e.g. internet doesn't work at all, etc.). The described issue is for the modified firefox which comes with the Tor browser bundle 4.0.4.

And how does that look like for Firefox 36.0.1 which is using Tor?

I would have to learn about setting it up. Does it really help to fix this issue? Then I'd do it...

comment:3 in reply to:  2 Changed 5 years ago by gk

Replying to krichter:

And how does that look like for Firefox 36.0.1 which is using Tor?

I would have to learn about setting it up. Does it really help to fix this issue? Then I'd do it...

The problem is that I need to know which part of Tor Browser the culprit is. It could be Tor, the browser or something else. If your vanilla Firefox + Tor has the same problem but not the Firefox without it, I'd start looking closer at Tor. If not, closer at the browser within Tor Browser. So, you could open your Tor Browser as usual and then your Firefox as usual. In the latter go to Preferences -> Advanced -> Network -> Settings... and enter "127.0.0.1" in the SOCKS Host: box and "9150" (both without the quotes) in the respective Port: box. Then check the Remote DNS option, click okay and try to reproduce the problem in your Firefox.

comment:4 Changed 2 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.