NetworkManager 0.7~~svn20081008t224042-0ubuntu1 breaks Knetworkmanager

Bug #280919 reported by Roderick B. Greening
6
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: network-manager

Recent updates for intrepid introduced a new version of network-manager. It has broken network-manager-kde (once again).

In order to get back online, I had to manually perform a ifconfig on eth0.

Revision history for this message
Roderick B. Greening (roderick-greening) wrote :

Just in case I am the only poor person affected, please post any suggestions on what to test/try?

description: updated
Revision history for this message
Scott Kitterman (kitterman) wrote :

Wireless works for me, but if I boot with wired only it seems problematic. Per conversation on IRC, the reporter was using a wired connection.

Changed in network-manager:
status: New → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

It seems that if I boot with wireless it works. If I switch to wired it works, but is very laggy. If I boot with wired only, something is definitely wrong.

Revision history for this message
Roderick B. Greening (roderick-greening) wrote :

I just tested with wireless, and was able to connect.

There is definately some kind of regression affecting network-manager-kde with the new network-manager.

Changed in network-manager:
importance: Undecided → Medium
milestone: none → ubuntu-8.10
Revision history for this message
Scott Kitterman (kitterman) wrote :

[19:04] <asac> ScottK: unlikely that the regression window really is the latest upload. at least if its a knetworkmanager specific issue
[19:05] <asac> ScottK: read: no dbus api changes in the last upload.
[19:05] <asac> ScottK: do you use a "hybrid" setup, e.g. one connection managed by ifup/ifdown and the wireless with NM?

[06:08] <ScottK> asac: About NM, not on purpose I don't use a hybrid setup. Everyone who tried it (there were three of us, IIRC) saw similar issues on Kubuntu.
[06:08] --> philwyett has joined this channel (n=philip@79-69-150-162.dynamic.dsl.as9105.com).
[06:09] <asac> ScottK: hybrid == /etc/network/interfaces has a configuration ;)
[06:10] <ScottK> asac: It says auto eth0. Does that count?
[06:10] <asac> ScottK: if there is no iface eth0 ... line then it shouldnt
[06:11] <ScottK> Nope
[06:11] <ScottK> The only iface line I have is for lo
[06:11] <asac> ScottK: please paste your route -n output when you see these packet losses
[06:11] <ScottK> OK. Will do.
[06:11] <asac> ScottK: i have received other complains, but couldnt reproduce here except for a hybrid setup
[06:12] <asac> ScottK: for me "wired" interfaces always have a metric/prio of "1" and wireless have a metric/prio of "2"
[06:12] <asac> which should tie-break the path the packages travel - assuming that both interfaces provide a route to the same net
[06:13] <ScottK> OK.

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Scott Kitterman (kitterman) wrote :

This is one wireless when it's working fine:

$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.111.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.111.254 0.0.0.0 UG 0 0 0 wlan0

Revision history for this message
Scott Kitterman (kitterman) wrote :

Wireless and wired active working OK (adding wired to wireless and switching was problematic for me yesterday):

$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.111.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
192.168.111.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.111.254 0.0.0.0 UG 0 0 0 eth0

Revision history for this message
Scott Kitterman (kitterman) wrote :

Booting to wired with wireless disabled (works, but slow and the Knetworkmanager icon is now a green globe instead of showing a wired connection):

$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.111.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.111.254 0.0.0.0 UG 0 0 0 eth0

Revision history for this message
Scott Kitterman (kitterman) wrote :

Note: When I switched to the config in comment 7 (switched to wired from wireless, both active) my router started screaming about a syn flood attack. I'll try and capture data with wireshark later today.

After starting on a wired connection if I re-enable wireless it doesn't work (it knows there's a wireless adapter, but can't see the AP).

relevant lspci in case this is hardware specific:

09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

Revision history for this message
Ilya Minkov (i-minkov) wrote :

Hello,

I can confirm the problem.

Made a clean install of intrepid kubuntu yesterday and updated everything. All configuration in /etc/network is left as it is by default, i.e. nothing configured. Went on to configure my network with kde networkmanager. I have a manually assigned static IP. It was unable to connect, but showed no specific error either.

To be able to update kubuntu, i made the network work temporarily using ifconfig, route and a write to /etc/resolv.conf, which are all nonpermanent measures i believe.

I don't have any wireless networking to test at the moment.

Additionally i installed the gnome version of networkmanager, killed the KDE one, started nm-applet, made settings there, and had network working instantly. Just to make sure, i went back to KDE version, but was still unable to make it working.

I also noticed that the profiles i created in Gnome and in KDE versions are not shared between them - i don't know whether this is supposed to be like that.

If i can make any further diagnostics, let me know.

Also it is somewhat annoying that knetworkmanager uses Qt3, as one would normally want to avoid running too many different UI toolkits all the time, Gnome version almost makes more sense atm within KDE.

-i.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.

Changed in knetworkmanager (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.