Closed Bug 27975 Opened 25 years ago Closed 9 years ago

[meta] "Conn:" network availability features

Categories

(Core :: Networking, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: warrensomebody, Unassigned)

References

Details

(Keywords: meta)

Attachments

(1 file)

Currently we don't deal very well with the the absence of a network connection. We hang on unix, and bring up the dialer on Windows. (Not sure about Mac.) I understand that Travis might have access to some code to implement this for Windows. Assigning to him for now. See bug 7428 about the hang on unix. Bug 21835 about SetOffline (an alternative perhaps).
Blocks: 7428
Target Milestone: --- → Future
-> gagan
Assignee: valeski → gagan
mass move, v2. qa to me.
QA Contact: tever → benc
Early bug number, no mindlessly long discussion... so I'm going to meta all the general connectivity bugs here.
Keywords: meta, mozilla1.0
OS: Windows NT → All
Hardware: PC → All
Summary: need to detect if network is available → [meta] network availability features
These sorts of bugs?
Depends on: 81150, 81208
Sure. Hopefully I can clean everything up at once this week...
Summary: [meta] network availability features → [meta] "Conn:" network availability features
Ha ha. "last week"... Okay, I'm working on this more now... Here's a summary of what I am looking at: 1- Behavior if disconnected (no PPP or PPPoE connection when launched). 2- Behavior when network changes. Since these problems are often system specific, I'm creating one bug per OS per feature. If necessary, I might create an intermediate layer of meta bugs per feature that glob the OS bugs, since that is the most likely way people will want to fix problems. Lots of thse bugs are lying around the component, so the dupe cleanup maybe out of order, even though I prefer to dupe to the lowest number bug, it may not be possible this time. Since we are a network application using the system stack, the basic model is that we call for data, and if it doesn't come back, we should error accurately, and if possibly helpfully. Assuming all basic network errors in an environment with good connectivity work, the most basic bug needed is: bug 164715. Some operating systems offer dial-on demand features. If we can work with them, we should. Mac OS X has dial on demand, but the implementation is not transparent. See bug 150729. I'll continue to add more information here.
Depends on: 150729, 164715
Mozilla 1.1 and Netscape 7.0 seem to do dial on-demand in Win98. I do not recall this working before. I do not use dialup on my Linux system currently, so if someone could help, that would be great. Quick-launch and VPN software are two other items that need to be addressed.
Assignee: gagan → new-network-bugs
Whiteboard: checklinux
Refresh of DNS servers, needed for continutity of DNS service after switching networks, seems to work correctly in Win98 and somewhat (as mentioned above) in Mac OS X. In Linux, it seems to be broken, after being fixed for a while. I need to verify the fix with an old build, then file or find a new bug for the regression.
Depends on: 165654
adt: removed nsbeta1 nomination. Please nominate individual bugs as appropriate.
Keywords: nsbeta1
No longer depends on: 165654
The DNS problem was fixed some time ago.
No longer blocks: 7428
Keywords: mozilla1.2
Whiteboard: checklinux
Assignee: general → rvitillo
Assignee: rvitillo → general
:bagder has done a lot of work here.. followups with specifc action items welcome.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: