|
Bugzilla – Full Text Bug Listing |
| Summary: | kde4 network manager connects to the selected connection but does not add the default gw and dns | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Victor Dimitrov <gradiento> |
| Component: | KDE4 Applications | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P1 - Urgent | CC: | asimonelli, bluedzins, forgotten_qkdF2eBG0D, forgotten_sCvTvm8ObT, gradiento, jnelson-suse, marios_hellas_23, meissner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | . | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | edit network connetion - IP address tab | ||
|
Description
Victor Dimitrov
2009-11-09 21:05:06 UTC
Created attachment 326696 [details] edit network connetion - IP address tab I found out why and when this problem happens: 1. GW and DNS (in dhcp and manual mode) are not applied when the following connection option is on: "neverdefault=true". See attached file also for its GUI representation. 2. I find odd the way "IP address" tab is presented for the connections. The drop-down list is "kind of hidden" in the bottom right corner of the tab which would prevent many people to see the very important configuration options it contains. 3. I have to relogin to be abble to apply new settings for the connections. This is a major issue I think. 4. I think Bug 550907 "Network Manager DHCP" is a duplicate bug Regards, Victor *** Bug 550907 has been marked as a duplicate of this bug. *** This definitely should be fixed ASAP since it is in the final release! I spent so much time trying to connect to the Internet through my home wireless LAN with no luck. Connecting to the local LAN, no problem but it would not route to the Internet. I tried everything and eventually found this on the forums: http://forums.opensuse.org/pre-release-beta/424435-11-2-rc2-networkmanager-ar5007eg-problems.html This was exactly my problem and it looks like this bug has been around since RC1. Bugzilla was down over the weekend (503 HTML error) so until I found this bug today and bug 550907, I could not get to the Internet. Given that most people get a computer for Internet usage, I don't think anyone new to openSUSE would be able to figure this out and will get frustrated quickly, especially if they don't have another computer to get to the Internet from! All reporters: Can you check that the 'Ignore automatically obtained routes' checkbox in the Routing section of the Ipv4 settings for your connection is not checked? SWAMPID please Test update submitted to KDE:KDE4:STABLE:Desktop I can confirm that I have that option unchecked and it works. I just found something very bad which should shed some more light on this. The two checkboxes are checked randomly by default when you create new wifi/wire connection! This is why some people report that these options should be unchecked by default. Please note that I still use RC2 (will try to upgrade tommorow). The random behaviour could by observed quite easly: 1. Goto "Manage connections" > Wireless (or wired) 2. Click "Add", goto "IP address">"routes" tab and see if any of the two options are checked by default. 3. Click OK to save the connection 4. repeat 2 and 3 few times and observe the default status of the two options. You will see that they will be checked randomly (sometimes one, sometimes both options are checked). I never expected that this was the reason for all these troubles... (In reply to comment #6) > Test update submitted to KDE:KDE4:STABLE:Desktop I just upgraded the networkmanager (to 0.9.svn1043876-1.1-i586) and I can confirm that I don't see the random behaviour from RC2. Also now I don't need to restart NetworkManager after I make changes to the connections. But please make some small reorganization of the NetworkManager GUI, here are some suggestions: 1. "IP address" tab, this tab includes options (DNS, routes) that are not close related to the name "IP address". You should put a name like "IP configuration". 2. Please see if you can remove this drop down box in the "IP address" tab and replace it with a button with the name "Advanced"(for example), which after clicked will display the "Routes" and "Additional addresses" fields (possibly in a new dialog window or why not directly in the IP address tab) I have experince with quality assurance on complex Maritime Vessel Traffic Systems so I can help with some other minor suggestions about NetworkManager if you think it would be helpfull. The SWAMPID for this issue is 28894. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/28894) update looks sensible ... if you can roll in more fixes, you can do that too. your maintenance team I can successfully connect to 2 wireless network that have wep key. I can't connect (i mean no dns and route) in networks without key. Tested it with two laptops, one with intel 3945 and another with atheros chip. So it is not a hardware issue. Hope that helps. Also, there is some usefull info here http://forums.opensuse.org/network-internet/wireless/424940-problem-wireless-wlan-works-no-internet-access-6.html I installed 11.2 last night, and ran into this networking issue. After reading through the bug, I updated NetworkManager-kde4 and NetworkManager-kde4-libs (and any dependencies) to version 0.9.svn1043876-4-4 from the KDE:KDE4:STABLE:Desktop repo. I am now able connect to my networks just fine. Any estimate as to when this fix will be moved to the update channel? Hi, I just updated to 0.9.svn1043876-4-4. As I said before, I don't experience the bug I reported but still there is another issue: After turning off the WIFI (antenna switch) then check and uncheck the "Enable Wiriless" option a few times. In the end the "Enable Wiriless" option becomes disabled (and unactive) and cannot be checked anymore even after I turn on the antenna switch ! Following is the log (note the "Wireless now disabled by radio killswitch" line), as you see the option becomes disabled after the 6th check/uncheck attempt and I have to reboot the PC to make the option active again: Nov 29 21:08:33 linux-vhsq NetworkManager: <info> (wlan1): bringing up device. Nov 29 21:08:34 linux-vhsq NetworkManager: <info> (wlan1): device state change: 2 -> 3 (reason 0) Nov 29 21:08:34 linux-vhsq NetworkManager: <info> (wlan1): supplicant interface state: starting -> ready Nov 29 21:08:42 linux-vhsq NetworkManager: <info> (wlan1): device state change: 3 -> 2 (reason 0) Nov 29 21:08:42 linux-vhsq NetworkManager: <info> (wlan1): deactivating device (reason: 0). Nov 29 21:08:42 linux-vhsq NetworkManager: <info> (wlan1): taking down device. Nov 29 21:08:51 linux-vhsq NetworkManager: <info> (wlan1): bringing up device. Nov 29 21:08:51 linux-vhsq NetworkManager: <info> (wlan1): device state change: 2 -> 3 (reason 0) Nov 29 21:08:51 linux-vhsq NetworkManager: <info> (wlan1): supplicant interface state: starting -> ready Nov 29 21:08:57 linux-vhsq NetworkManager: <info> (wlan1): device state change: 3 -> 2 (reason 0) Nov 29 21:08:57 linux-vhsq NetworkManager: <info> (wlan1): deactivating device (reason: 0). Nov 29 21:08:57 linux-vhsq NetworkManager: <info> (wlan1): taking down device. Nov 29 21:09:03 linux-vhsq NetworkManager: <info> (wlan1): bringing up device. Nov 29 21:09:03 linux-vhsq NetworkManager: <info> (wlan1): device state change: 2 -> 3 (reason 0) Nov 29 21:09:03 linux-vhsq NetworkManager: <info> (wlan1): supplicant interface state: starting -> ready Nov 29 21:09:07 linux-vhsq NetworkManager: <info> Wireless now disabled by radio killswitch Nov 29 21:09:07 linux-vhsq NetworkManager: <info> (wlan1): device state change: 3 -> 2 (reason 0) Nov 29 21:09:07 linux-vhsq NetworkManager: <info> (wlan1): deactivating device (reason: 0). Victor, please open a new bug for this issue. Thanks. update is at the test repo. http://download.opensuse.org/update/11.2-test/ could someone please test if it fixes the bug? Downloaded NetworkManager-*-svn1043876-1.1.1.i586.rpm from the update test repo, installed with 'rpm -Uvh * --force', restarted networking and knetworkmanager, and it seems to be working fine. Rebooted the system just to be sure, and all is well. Thanks! due to a mistake the update version had -1.1.1 justg as the GA version. we are respinning the updated rpms now (no other changes) so --force should not be required. thanks for testing already. we will however wait for the other 11.2-testers to complain if it does not work for the usual 7 days. *** Bug 559150 has been marked as a duplicate of this bug. *** Just tested the update rpms and i have no problems so far. regards, Carlos Update released for: NetworkManager-kde4, NetworkManager-kde4-debuginfo, NetworkManager-kde4-debugsource, NetworkManager-kde4-lang, NetworkManager-kde4-libs, NetworkManager-kde4-libs-debuginfo, NetworkManager-openvpn-kde4, NetworkManager-openvpn-kde4-debuginfo, NetworkManager-pptp-kde4, NetworkManager-pptp-kde4-debuginfo, NetworkManager-vpnc-kde4, NetworkManager-vpnc-kde4-debuginfo, plasmoid-networkmanagement, plasmoid-networkmanagement-debuginfo Products: openSUSE 11.2 (debug, i586, x86_64) update released *** Bug 561039 has been marked as a duplicate of this bug. *** *** Bug 559300 has been marked as a duplicate of this bug. *** |