[Bug 473714] New: wvdial fails to update DNS if NetworkManager is enabled.
https://bugzilla.novell.com/show_bug.cgi?id=473714 Summary: wvdial fails to update DNS if NetworkManager is enabled. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Uniacke1@yahoo.ca QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 Using wvdial to connect to dial-up internet results in a nameserver failure error from wvdial. If nameservers are manually added to /etc/resolv.conf, connection works normally. Wvdial has auto dns option enabled, and disabling networkManager via YAST causes the connection to work properly without the need to manually add nameservers. Reproducible: Always Steps to Reproduce: 1.launch wvdial to connect to ISP on system with network manager enabled. After connecting, wvdial states 'Warning, no nameserver found '/etc/resolv.conf' Nameserver (DNS) failure, your connection may not work", though wvdial receives IP and DNS addresses from ISP. Actual Results: As described Expected Results: Nameservers should be added to /etc/resolv.conf after connection. This worked fine in SuSE 10-11, first broken in 11.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User dominique.leuenberger@tmf-group.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c1 Dominique Leuenberger <dominique.leuenberger@tmf-group.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dominique.leuenberger@tmf-g | |roup.com --- Comment #1 from Dominique Leuenberger <dominique.leuenberger@tmf-group.com> 2009-02-10 01:58:07 MST --- *** Bug 470523 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=470523 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 Martin Vidner <mvidner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |hvogel@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c2 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |aj@novell.com Resolution| |INVALID --- Comment #2 from Andreas Jaeger <aj@novell.com> 2009-02-25 06:41:41 MST --- If you use NetworkManager, you have to use it for the whole system. NetworkManager has dial-up functionality, please use that. If you use manually wvdial and have NetworkManager running, you run two things that do not work together. This breaks - and we will not fix it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User dominique.leuenberger@tmf-group.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c3 --- Comment #3 from Dominique Leuenberger <dominique.leuenberger@tmf-group.com> 2009-02-25 06:51:28 MST --- Partially true only: NM does NOT support dialing using a 'modem' (phone) connected using Bluetooth... so there is no way around wvdial in such a case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User Uniacke1@yahoo.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c4 B. Wielens <Uniacke1@yahoo.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #4 from B. Wielens <Uniacke1@yahoo.ca> 2009-02-25 16:18:44 MST --- If that is the case, then WHERE THE HELL IS IT? my modem is configured Via YAST, kInternet can use it, (which also fails to set DNS servers, BTW) and there is NO dial-up option anywhere in networkManager. NM only finds eth0 and wlan0, but no modem. I recall when it was first introduced, there was an option for dial-up, but it disappeared after the next release of openSuSE and I have not seen it since. Believe me, if NM had a dial-up option I would be using it, so as to avoid Firefox whining about being in offline mode every single time I start it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c5 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hvogel@novell.com |tambet@novell.com Severity|Major |Enhancement --- Comment #5 from Andreas Jaeger <aj@novell.com> 2009-02-25 23:04:59 MST --- Seems that Dominque is right. So, let me restate: Use the traditional setup if you need this to work. to have Modem support in NM is a feature request, and let's move it to Tambet for that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User dominique.leuenberger@tmf-group.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c6 --- Comment #6 from Dominique Leuenberger <dominique.leuenberger@tmf-group.com> 2009-02-26 00:57:09 MST --- (In reply to comment #5)
So, let me restate: Use the traditional setup if you need this to work.
Yaiks... BT modems are mostlyu sed (I guess :) ) on notebooks, where NM is almost mandatory to be used (office network, home network, wifi at the airport and so on) and in cases nothing else is available you (at least me) fall back to GPRS over BT connection. For the time being I think I stay with 'wvdial and then fixing /etc/resolv.conf'. Is there a good way to tell the system that 'there is a connection' so that FF does not believe to have the need to work in offline mode? (also other apps..) I think there was a d-bus call that could be issued for this
to have Modem support in NM is a feature request, and let's move it to Tambet for that.
Great. Thanks for this. Tambet: if you need any help in testing, feel free: I'm here and looking forward in being able to use this feature ;) so far NM supports Mobile Broadband, but it's not possible to use it over a BT connected 'modem'. I think that the upstream discussed 'Modem Manager' might be of some uise here? (there was some upstream work in trunk, but not in the 0.7 series). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c7 --- Comment #7 from Tambet Ingo <tambet@novell.com> 2009-02-26 01:33:04 MST --- Proper Bluetooth support will come with the next major NetworkManager release (not sure the version name, 0.8 maybe). In the mean time, I'll add support for probing serial devices so if the BT modem is manually made available (using bluez tools) then ModemManager (and NetworkManager) will be able to use it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User Uniacke1@yahoo.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c8 --- Comment #8 from B. Wielens <Uniacke1@yahoo.ca> 2009-02-26 04:50:48 MST --- FWIW, I'm actually not using a BT modem... it is an internal laptop modem, device ID 11c11040, accessed through /dev/ttyAGS3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c9 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |Uniacke1@yahoo.ca --- Comment #9 from Tambet Ingo <tambet@novell.com> 2009-02-26 05:07:21 MST --- Sorry, I got carried away with comments that do not belong to this bug. So as a general information, if your modem does not work with NetworkManager, please open a new bug and assign it to me. It's not useful to have one bug "My modem does not work with NetworkManager" as there will always be a modem which doesn't. What kind of modem do you have? Please attach the output of 'lshal' command here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User Uniacke1@yahoo.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c10 --- Comment #10 from B. Wielens <Uniacke1@yahoo.ca> 2009-02-26 12:53:13 MST --- Created an attachment (id=275797) --> (https://bugzilla.novell.com/attachment.cgi?id=275797) lshal output as requested. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User Uniacke1@yahoo.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c11 --- Comment #11 from B. Wielens <Uniacke1@yahoo.ca> 2009-02-26 12:59:11 MST --- I've attached said output, but I do not think it will be of particularly much use- the modem is based off the sound card HDA interface, hence it is not detected by YAST, and must be added manually. aplay -l does not list it either, but if I recall properly, there is a patch somewhere that addresses this issue. The most useful information I can provide is lspci and the content of /proc/asound/card0/codec#1 (the modem codec) Codec: LSI ID 1040 Address: 1 Vendor Id: 0x11c11040 Subsystem Id: 0x11c10001 Revision Id: 0x100200 Modem Function Group: 0x1 as for lspci, here are the details on the audio device, I've attached lspci -vv. Please don't hesitate to ask for anything else you may need. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User Uniacke1@yahoo.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c12 B. Wielens <Uniacke1@yahoo.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|Uniacke1@yahoo.ca | --- Comment #12 from B. Wielens <Uniacke1@yahoo.ca> 2009-02-26 13:08:29 MST --- Created an attachment (id=275799) --> (https://bugzilla.novell.com/attachment.cgi?id=275799) lspci output for sound card info. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c13 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #13 from Tambet Ingo <tambet@novell.com> 2009-02-27 00:44:32 MST --- Ah, so it's a landline modem. These are not supported in NM. The main reason is that these modems can't be automatically detected. Most of these are softmodems requiring closed source binaries and being a dying technology doesn't help either. So we're back to your original bug report. :) The reason why wvdial can't update your /etc/resolv.conf is that the script (netconfig) that modifies that file refuses to do so when NM is used for networking. There have been other similar bugs and the resolution has been "works as designed". If NM doesn't provide the functionality you require and "traditional method" does, then there's no other way than to use the method that works. Mixing the two does not work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User Uniacke1@yahoo.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c14 --- Comment #14 from B. Wielens <Uniacke1@yahoo.ca> 2009-02-27 05:46:19 MST --- Hmmm... as I've said before, NM did at one point have support for these types of modems- there definitely was a dial-up option. Is that the reason it was deleted? If so, it seems rather strange, since one doesn't really need to have NM detect the modem- all it would need to do is see if one is configured in YAST, and if so, read and use those settings for modem serial port etc. However, I'm not familiar with how these things are implemented, so I don't know if it is quite as simple to do from a programming perspective. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c15 --- Comment #15 from Tambet Ingo <tambet@novell.com> 2009-02-27 06:52:09 MST --- Yes, the reason why this "support" got removed was that it wasn't really what you think it was. You can add a launcher to the panel which runs "ifup ppp0" and it would be as much integrated with NM as that was (because that's what that thing did in nm-applet). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User aspiers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c16 --- Comment #16 from Adam Spiers <aspiers@novell.com> 2009-03-02 07:13:24 MST --- I also see this. My USB Sierra Wireless AirCard 875U doesn't work with (k)networkmanager, so as per comment #9 I'll submit a separate bug for that. In the mean time, I'll have to use wvdial and manually edit resolv.conf as a workaround. Therefore I would VERY much appreciate an answer to the following: (In reply to comment #6)
Is there a good way to tell the system that 'there is a connection' so that FF does not believe to have the need to work in offline mode? (also other apps..) I think there was a d-bus call that could be issued for this
I have searched high and low on the internet for a way of doing this, but despite finding many other people who also need it, I found no solution, and I couldn't find docs on the NetworkManager dbus methods either. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c17 --- Comment #17 from Tambet Ingo <tambet@novell.com> 2009-03-02 08:07:35 MST --- No. These applications use NetworkManager API to determine the online/offline state and if the connections is brought up using some other means, NM has no way of knowing about it. It is not possible to tell NM "lie to apps and say we're online", because then it'll need to provide all the other details as well (like IP configuration, routes, DNS, ...), handle global state (like default route, resolv.conf), and monitor the connection to change the status when the connection goes down. All that can be summarized with "add support for the device in NM", so if someone is up to it, NM gladly accepts patches. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User Uniacke1@yahoo.ca added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c18 --- Comment #18 from B. Wielens <Uniacke1@yahoo.ca> 2009-03-02 08:32:26 MST --- Seems to me the easiest way to do this (and avoid the need to actually detect devices) is to read the modem config from YAST, and then use that config connect and dial- That way, there is no need for individual support for each device. If I had more C experience I'd be willing to try this, but as it stands, my forté is other languages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User aspiers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c19 --- Comment #19 from Adam Spiers <aspiers@novell.com> 2009-03-02 08:43:38 MST --- (In reply to comment #17)
No. These applications use NetworkManager API to determine the online/offline state and if the connections is brought up using some other means, NM has no way of knowing about it. It is not possible to tell NM "lie to apps and say we're online", because then it'll need to provide all the other details as well (like IP configuration, routes, DNS, ...), handle global state (like default route, resolv.conf), and monitor the connection to change the status when the connection goes down. All that can be summarized with "add support for the device in NM", so if someone is up to it, NM gladly accepts patches.
Ah - I was thinking that the "we're online" message was a "push" broadcast on dbus from NM, but from what you're saying it sounds like it's a "pull" the other way around, i.e. firefox/pidgin etc. individually ask NM for the current network status. Did I understand that right? Why do programs like firefox/pidgin need to know any more than the offline/online toggle bit though? Surely resolv.conf, routes etc. are irrelevant to them? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c20 --- Comment #20 from Tambet Ingo <tambet@novell.com> 2009-03-02 09:34:37 MST --- The applications call NetworkManager DBus API and add signal listeners for changes. Yes, firefox and pidgin might not care about the details, but some other applications might. It's the matter of having consistent public API. For example, an application might take advantage of details like "Are we connected to wireless AP 'foo'?" or "do we have connection to the corporate private network (either directly or through VPN)?". What would the /nm-tool/nm-applet/main menu/... show for connection details? Which device would it mark as active? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473714 User aspiers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473714#c21 --- Comment #21 from Adam Spiers <aspiers@novell.com> 2009-03-09 12:38:29 MST --- Makes sense, thanks a lot for the info! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com