Alternative to Networkmanager

What is the best GUI software alternative for Knetworkmanager in repos. I have some issues with this software. Currently i am using ifup, and it work great than KNetworkmanager.
I was facing speed issue and now is fine, while using ifup method.

Any ideas?

Don’t know if there is an alternative gui for kde. You could try the gnome gui.
Personally, I’ve always used ifup and it does everything the gui does but just needs a bit of command-line typing. Try ipup --help for all the switches.

Try ipup --help for all the switches.

I think you meant

ifup --help

You can also have a look at

man ifup

What is the best GUI software alternative for Knetworkmanager in repos.

Are you using KDE3 or KDE4? I remember I use to use KInternet to control both my modem, wireless, and ethernet interfaces with 10.2.

I am using kde4.2.3.

On Mon, 2009-06-01 at 18:06 +0000, mmarif4u wrote:
> What is the best GUI software alternative for Knetworkmanager in repos.
> I have some issues with this software. Currently i am using ifup, and it
> work great than KNetworkmanager.
> I was facing speed issue and now is fine, while using ifup method.

NetworkManager’s goal is to attempt to make the BEST GUESS at the
desired network path/connection. By definition, it is probabilistic…
so is the network connection routine in Windows. The reason why some
consider this better is because most WINDOWS users have no clue as to
what a network is… and so you need to PULL THEM THROUGH the process.

Is that right? IMHO, no. The problem isn’t taking pot shots (with
errors) at making a network connection, but rather, the problem is that
people on the Internet, do not know nearly enough to be a responsible
user of the technology. Instead of encouraging ignorance, we should be
educating people.

I use ifup… I want to KNOW how I’m getting connected. No guessing. I
just hope that openSUSE doesn’t continue to erode into a Windows-esque
distro.

I’d much rather have something that “pull me though” by saying, “I tried
this (with detail), it didn’t work, here are some reasons why, and oh…
this (with detail) might be an option as well, can I try that for you?”
You CAN educate people while taking guesses… that’s NOT the goal of
NetworkManager. It is a tool designed to work like WINDOWS… that is,
you are too stupid and too “important” to be concerned with this (very
important) thing I’m doing.

When a really easy/good Linux distro network threat is devised, look for
the NetworkManager users to spread it like wildfire… they’ll also be
the ones to complain the loudest about how “Linux” let them down.

I know I didn’t answer you’re question… but ifup with a bit of work,
could be really great.

I don’t use knetworkmanager because it interferes with profile switching.
Instead of using “raw” ifup/ifdown etc., one may use Yast itself to configure the network devices. It’s GUI is good. You can always look in the directory /etc/sysconfig/nerwork to see the saved configuration files if you want to fine-tune something.
knetworkmanager assumes a “windo$-like user” and has got the same problems of windo$ when it fails to determine something properly.

Thanks to all.
Currently using the yast one. it is working fine than Knetworkmanager. There is also another kde3 application called KInternet. But also like Networkmanager.
Some other application which i found bu searching are:
1- Kwlan
2- Wireless Assistant
3- Wifi Radar
Most of them are KDE3 compatible.
So for now, Yast ifup is fine to stick around than others.

I am also thinking of to switch to gnome desktop. becoz i have some other problems with screen too.

Sorry, It was double posted, bcoz of internet problem…
I had edited it.

kinternet is useful when you want to handle dial-up connections. It goes well with Yast configuration.

KDE version 4.0 or later is not good. To eliminate most of the issues, you may upgrade to at least 4.2.

I have KDE 4.2.3 now and system is fully updated with all updated driver releases.
But not still not sure, why this screen issue still there.

WCID is very good. Don’t know if it has issues with KDE though.

I think its gnome app, Am i right.

It says no Gnome dependencies, although it does require GTK. See wicd - home

On Tue, 2009-06-02 at 05:36 +0000, mmarif4u wrote:
> I have KDE 4.2.3 now and system is fully updated with all updated driver
> releases.
> But not still not sure, why this screen issue still there.

KDE 4 is NOT an upgrade to KDE 3.5. It’s a totally different beast.
It will take quite some time (if ever) for KDE 4 to be as functional
as KDE 3, especially with regards to integration with other non-KDE
applications. I use KDE 3.5 on my 11.1 environment… why? Because it
works well with compiz, where KDE 4 does NOT (and KDE’s attempt at
compositing is so poor… well… nuff said).

I really wish the KDE 4 developers had tried to include the features of
KDE 3 into their design. Arguably, the design of KDE 4 prevents that
from ever happening (forcing the non-KDE apps to change to adapt to KDE4
isms… sigh).

As gminnerup said, WICD is a very very good network manager for both all desktop with a systray support (gnome, kde x.x.x, xfce, etc.)
It run flawlessly for me for months now (already uninstalled knetworkmanager on my computer)

Here is the one-click install : http://software.opensuse.org/ymp/home:dmitry_serpokryl:Enlightenment-cvs-core-metapackage/openSUSE_11.0/wicd.ymp

Edit: I forgot to tell you that the one-click install provided here is for openSuse 11.0. Check herefor openSuse 11.1

Does it go well with multiple profiles? Any experience?

Yes. Multiple profiles for multiple cards are supported. Work only for wired and wireless connections (not for ppp/umts/3G connections at the moment), which is sufficient for most cases nowadays

Yep. I vote for ifup also.
Network Manager has never worked right for me.

I used knetworkmanager in KDE 3 and KDE 4.3beta.
What is strange is that it behaves differently in each version.

In KDE3 I can connect to my WPA2 network
and all other networks,
including open WiFi-networks in my university.

But in KDE 4 I can connect to my WPA2 access point
and cannot to open networks in the university.
(And, of course, ifup connection works each way.)

ifup is nice,
if you don’t move a lot (e.g. home access point)
or if you have a map of available
WiFi access points stored in your head.