If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
If you have copied text output that contains formatting (colors, highlighting, etc.), please do not enclose it in QUOTE or CODE tags. Just right-click your mouse and choose "Paste Without Formatting" or similar (Paste as plain text).
One really needs to know what is installed instead of guessing.
In II 8.10, the following network manager packages are installed (on my system):
network-manger network-manager-kde
knetworkworkmanager is not installed.
network-manager
NetworkManager attempts to keep an active network connection available at all
times. It is intended only for the desktop use-case, and is not intended for
usage on servers. The point of NetworkManager is to make networking
configuration and setup as painless and automatic as possible. If using DHCP,
NetworkManager is _intended_ to replace default routes, obtain IP addresses
from a DHCP server, and change nameservers whenever it sees fit.
network-manager-kde
ystray applet for controlling network connections managed by
NetworkManager. It is mainly written for KDE but also works for
other desktop environments like GNOME or Xfce.
This package provides the userspace daemons.
knetworkmanger
systray applet for controlling network connections managed by
NetworkManager. It is mainly written for KDE but also works for
other desktop environments like GNOME or Xfce.
This is a dummy package to depend on network-manager-kde for
upgrades, it can be safely removed.
Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
I had a problem getting a static n/w link to work using knetworkmanager - based on input from bug 279409 on launchpad I altered the netmask for my static definition from 255.255.255.0 to 24.0.0.0 and the link now starts & works.
KNetworkManager provides the netmask in decimal notation, but NetworkManager expects it to be in CIDR-notation. I'm not comfortable enough in this codes to provide a patch, but there is an easy workaround you can use until this problem ist fixed. Instead of given the netmask in dotted decimal ("255.255.255.0"), just put the CIDR value into the first field and insert Zeros into the others: "24.0.0.0".
That explains a lot of the problems people are having with knetworkmanager, wired and wireless. 24 is the CIDR value for 255.255.255.0. Of course I still like my method of not using a network manager, just modify your interfaces file to work.
Comment