Closed Bug 279160 Opened 20 years ago Closed 18 years ago

Use libnm on linux to manage offline/online status

Categories

(Core :: Networking, enhancement)

x86
Linux
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: caillon, Unassigned)

References

()

Details

Attachments

(1 file)

NetworkManager will auto detect when a network cable is (un)plugged, a wifi card
is (un)plugged, etc. when we associate with a wireless network, and can send
notifications when said events occur.  This can be used in conjunction with
firefox to prevent unneeded DNS lookups which will time out and we can go
straight to cache, or display a message to the user that there is no
connectivity.  And it will set us back online when we get a network connection back.

NetworkManager currently is shipped in Fedora Core 3 and later, and will be in
the upcoming RHEL4.
Attached patch Initial patchSplinter Review
This patch is from Dan Williams <dcbw redhat com>, author of NetworkManager.
Can we put this functionality in a separate lib, so that the dynamic dependency
won't kill the app if it's installed on an older OS?
mozilla/netwerk/build/Makefile.in
mozilla/netwerk/base/src/Makefile.in
+ifeq ($(MOZ_USE_NETWORK_MANAGER), 1)

I think the usual way is to write:
ifdef MOZ_USE_NETWORK_MANAGER
Summary: Use libmn on linux to manage offline/online status → Use libnm on linux to manage offline/online status
Assignee: darin → nobody
QA Contact: benc → networking
Fixed by checking for bug 312793
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Can this be disabled?

My network card is not supported by network-manager (whatever the reason - nm-applet would always report that I'm offline), and using a firefox-3.0a2pre.fr.linux-i686 I am unable to load any pages.
So why is NetworkManager running at all on your system if it doesn't support your hardware? That looks like the bug for me.
I'm sorry, I've uninstalled nm and this was not related (I had it installed because my distro defaults to it).
Setting network.dns.disableIPv6 to true fixed my problem.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: