Red Hat Bugzilla – Bug 480874
no longer notices network changes automatically
Last modified: 2018-04-11 08:39:21 EDT
Description of problem:
When I bring up or bring down the VPN with NetworkManager, Firefox no longer automatically notices and adjusts its DNS search accordingly. I either have to wait ~30-40 seconds for a request to time out (at which point it switches), or manually toggle offline/online.
In 3.0, this worked fine.
Version-Release number of selected component (if applicable):
DNS search is not something which Firefox would deal with -- why this isn't NM bug? And of course, I don't think Firefox cares at all about VPNs -- it checks from NM only whether the network connection is up or down, but which connection doesn't concern it, AFAIK.
Putting Dan on CC of this bug, but I think that this should belong to NM component.
I am assuming that it's a firefox bug, in that it used to work, firefox was updated from 3.0.x to 3.1beta, and now it does not work.
can I get here an output of nm-tool when the network connection is up and Firefox doesn't see it, please?
Matej: NM changes /etc/resolv.conf when you connect to the VPN. The glibc resolver does not notice changes to /etc/resolv.conf automatically, applications must call __res_init() manually. FF *used* to internally call __res_init() before any DNS lookup to ensure that it had the right DNS servers if /etc/resolv.conf had changed since it started up. Perhaps that's no longer the case.
Either apps need to handle /etc/resolv.conf changing themselves, or the user needs to run 'nscd', or glibc needs to detect changes to /etc/resolv.conf.
I don't think I can triage anything here, and hopefully the situation is clear to Christopher. Enjoy this!
Is this resolved with xulrunner-1.9.1-0.7.beta2.fc11 ?
Appears to be.