444071 - WPAD:No connection after changes to network have been made

Status: RESOLVED FIXED

(Core :: Networking, defect)

Description

[Martin Arndt]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

I'm running FF3 on a notebook and I have to "travel" quite a lot within our company (e.g. from 1st floor to 2nd, etc.).
Whenever I'm moving around, I just unplug the LAN-cable, move to the appropriate room and plug the cable back in again and since we're using DHCP-servers for assigning IPs, there's no problem at all - except when it comes to Firefox..

Firefox doesn't recognize the restored network connection and fails both, reloading a tab and opening a new website within a new tab.

Reproducible: Always

Steps to Reproduce:
1. Open up Firefox
2. Load a website of your choice, e.g. google.com
3. Unplug the LAN-cable connect to your network-port
4. Wait for Windows recognizing the connection interrupt
5. Plug the cable back in
6. Wait for Windows recognizing the restored connection
7. Wait for having your IP address (re-) assigned
Actual Results:  
Firefox fails to recognize the restored network connection

Expected Results:  
Firefox should continue to browse the website

Comment 1

[Martijn Wargers (dead)]

Hmm, this looks very similar to bug 444056.

Comment 2

[Martin Arndt]

But despite some similarity, the bug you mention talks about change from WLAN to LAN and Firefox not exiting completely - I'm talking about a connection interrupt and restoring _the same_ connection type and _no_ Firefox "hanging" within the task-manager.. ;)

Though, the result is still the same: Firefox doesn't get to know the restored connection..

Comment 3

[Martijn Wargers (dead)]

Oh, sorry, yeah, I got confused.

Comment 4

[Martin Arndt]

No problem.. - But could you then confirm the bug, please? :)

Comment 5

[Martijn Wargers (dead)]

Well, I can't reproduce this issue, but maybe I don't have the right setup to be able reproduce this issue (I don't really know much about this kind of thing).
Maybe this is related to bug 356831?

Comment 6

[WADA:World Anti-bad-Duping Agency]

To Martin Baranski(bug opener):
Can following be a workaround?
  - "Work offline", then return to "Work online" again.

Comment 7

[Martin Arndt]

Martijn,
my Firefox is indeed set to use Auto-proxy detection and I've got to admit that firefox.exe got "stuck" within the task-manager (even CMD->taskkill /F /IM firefox.exe didn't kick it out of the list, although Windows reported it)..
So it might be related to https://bugzilla.mozilla.org/show_bug.cgi?id=444056

WADA,
I haven't tested it, but I'll do so ASAP..

Comment 8

[Martin Arndt]

Short update:

WADA, using "Work offline", immediately followed by "Work online" indeed solves the problem! :)

Comment 9

[benc]

If you are switching networks, and the networks use different PAC files, you might have problems.

What is your proxy UI set for?

When you go offline and online, it forces PAC to reload.

Comment 10

[Martin Arndt]

Assuming "PAC" means proxy-auto configuration, the UI (as already stated in comment #7) is set to use "Auto-detect proxy settings for this network"

Regarding my "network switching", I have to say that there's only _one_ DHCP which handles _all_ IP address-related stuff..

Comment 11

[benc]

There might be a dupe...

If you switch networks, the PAC file won't updated unless you reload it manually. So, when you press Reload in the Connection Prefs (or go offline-online) then it probably works fine?

Comment 12

[Martin Arndt]

Right, File->Work Offline => File->Work Offline (remove tick) works fine.

Comment 13

[Patrick McManus [:mcmanus]]

bagder's changes should have resolved this