changing the wired network profile, doesn't work

Bug #443235 reported by Schmirrwurst
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Network
Unknown
Medium
plasma-widget-networkmanagement (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

Binary package hint: kdenetwork

I have two wired network profiles :
- with dhcp, everything automatic
- with fixed ip address, gw ...

The dhcp profile is the default one, but when I click on the other profile, nothing is happening....

ProblemType: Bug
Architecture: amd64
Date: Mon Oct 5 18:10:14 2009
DistroRelease: Ubuntu 9.10
Package: kdenetwork (not installed)
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SourcePackage: kdenetwork
Uname: Linux 2.6.31-10-generic x86_64

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :
affects: kdenetwork (Ubuntu) → plasma-widget-networkmanagement (Ubuntu)
Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

I'm not sure it is liked with plasma widget, as under karmic, I have no network widget anymore , but a network applet in the system tray... ??

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

The naming is a little confusing, but the system tray knetworkmanager applet comes from the same source package.

Changed in plasma-widget-networkmanagement (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Changed in plasma-widget-networkmanagement (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Flemming Bjerke (flem) wrote :

Same thing. Plasma-widget-networkmanagement doesn't work with fixed ip-add. on my hp550 with kubuntu karmic.
My configuration:
SSID: default
Mode: Ad hoc or Infrastructure
BSSID:
Interface: eth2
MTU: Automatic
Security: None
Configure: Manual
IP-address: 192.168.1.100
Subnetwork mask: 255.255.255.0
Gateway: 192.168.1.1
Search domians:
DNS-servers: 208.67.222.222, 208.67.220.220

What seems to happen, is that the widget does not route through the gateway:
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 2 0 0 eth2
link-local * 255.255.0.0 U 1000 0 0 eth2
root@l# host dk-hostmaster.dk
;; connection timed out; no servers could be reached
root@lap# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=127 time=7.41 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=127 time=2.54 ms
root@lap# route add default gw 192.168.1.1
root@lap# host dk-hostmaster.dk
dk-hostmaster.dk has address 193.163.102.23
dk-hostmaster.dk mail is handled by 10 vocal.dk-hostmaster.dk.

If I restart the connection, the gateway route is lost again, but immediately re-established by:
root@lap# route add default gw 192.168.1.1

If I set Configure: Automatic (dhcp), everything works fine, and it routes throgh the gateway.

Conclusion, the bug is that manual fixing addresses etc does not establish a routing through the gateway.

Revision history for this message
Flemming Bjerke (flem) wrote :

Incidentally, when I select automatic DHCP addresses only in the manage connection window wireless-tap, and I insert opendns ip-addresser, dns does not work either. The ip-addresses do not turn up in /etc/resolv.conf.

This and a number of other bugs in (kde) networkmanager are so serious for everyday practical use. I know at least 5-6 programmers who just laugh of nm because it so hopelessly buggy. They won't ever bother about writing bug reports because this is too far out. They just use other programs such as wicd. As I have written in another bug-report, it doesn't work for HUAWEI modem either. But, since I made a simple script for wvdial, it works EVERY time. Calling the importance of these bugs "low" is just out of proportions. It is so critical that even clever programmers avoid using the program on their laptops.

I hope the developers soon will fix these absolutely critical bugs and test networkmanager properly.

Changed in kdenetwork:
status: Unknown → New
Changed in kdenetwork:
importance: Unknown → Medium
Changed in kdenetwork:
status: New → Unknown
Revision history for this message
Maarten Bezemer (veger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 443235 and any other logs that are relevant for this particular issue.

Changed in plasma-widget-networkmanagement (Ubuntu):
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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