178296 - On Change of Network, all network operations cease to work

Status: RESOLVED INCOMPLETE

(Core :: Networking, defect)

Description

[Louis Guillaume]

I saw a couple other bugs reporting this in the Mail product but they were only
for PC. 

I'm using a PowerBook and change networks often. After changing networks,
Mozilla must be restarted to work. This happens both in the Browser and in Mail
but there doesn't seem to be a bug reporter for both Products.

Attempts to connect to sites result in infinite hanging, and the application
needs to be killed. It doesn't even respond to mouse clicks anymore.

Perhaps you started saving the routing table in memory?

This used to work properly in Mozilla 1.0. It has been broken since 1.1. I'm
currently using 1.2b Build ID:2002110108 for Mac OS X.

Regards,

Louis

Comment 1

[Greg K.]

Louis, the Browser product covers the whole Mozilla application. Are you sure
this worked in 1.0? How about 1.0.1?

Comment 2

[hirata masakazu]

may be a dupe of bug 117613.

Comment 3

[benc]

Are we talking about new or old connections?

Does the problem happen if you go "offline" before making a network
configuration change?

Does the problem affect IP addresses and DNS names?

Comment 4

[Louis Guillaume]

This is definitely NOT a dup of 117613. The errors happen after DNS is
available. All other services on the machine work. The hostnames DO resolve but
I get (apparent) RST packets back: "Connection Refused." 

Actually, it turns out that the Browser does work. I'm not sure if this is
consistent, however. I seem to remember the browser failing as well but at this
point it's just the Mail.

The problem does NOT show up when switching interfaces, for example: from wired
network to AirPort. Everything works properly when this is the scenario.

The problem DOES show up if you change networks by say, putting the machine to
sleep at work, taking it home, plugging it into the network at home and waking
it up. I suppose it could also be simulated by plugging into another network,
I'll test this next time I'm at work (where I have several networks to test with.) 

I'll also test going offline before switching networks.

Louis

Comment 5

[Louis Guillaume]

I've done some more testing.

If I change networks behind the same firewall, i.e. the IP number of the Mail
server is the SAME, things appear to work fine.

If I leave this LAN and go to another, outside the firewall, the address of the
Mail server is now different and the problem pops up.

So It may very well be a DNS thing. The IP number derived from a query to the
"internal" DNS is stored. It is not re-looked-up on the "external" DNS during a
subsequent request to the same server from a different network.

Comment 6

[benc]

DNS is cached and never refreshed or expired.

So you are saying that the internal IP address is different than the external IP
address?

If so, I've got a dupe and a summary change for you.

Comment 7

[benc]

per bug 181135: all bugs owned by previous default owner that were not futured
are being reassigned to default owner.

Comment 8

[Pat Suwalski]

This bug must be promoted. I'm surprised more people have not noticed this. It's
a huge hit to mobility, especially if you're a user of wireless networks.

Comment 9

[Louis Guillaume]

This appeared to be fixed with 1.6, but now (with 1.7b 2004040505) the Mail and
Newsgroup component hangs after a change of network. On OS X 10.3.3 we get the
beach ball.

Also - where the Browser component would retain (for example) htaccess
authentication data on 1.6, it now re-prompts for username and password when you
change networks. This may be intentional and perhaps a good thing.

Comment 10

[Louis Guillaume]

can someone please try to replicate this problem and promote the bug from
"Unconfirmed" if appropriate?

It looks like comment no. 8 confirmed it: "It's a huge hit to mobility". I would
change the status, but I added this bug and don't believe it's my place to do so.

Thank you 

Comment 11

[louis bennett]

re: comment 5, did you put the machine to sleep between networks? if so, that
may have been fixed by a recent check-in fixing issues related thereto.

Comment 12

[Frankie]

This sounds a lot like bug 186981

Comment 13

[Doug Turner (:dougt)]

mass reassigning to nobody.

Comment 14

[Wayne Mery (:wsmwk)]

Do you still see this problem when using Firefox 3?

Comment 15

[Tyler Downer [He/Him]]

@Reporter, we have not heard back from you in a while, so I am closing this bug as INCOMPLETE. You can reopen this bug if more information becomes available.