Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How best to replace NetworkManager with wicd?
99 views
Skip to first unread message
kei...@strucktower.com
Feb 12, 2012, 3:10:01 PM2/12/12
to
Sometime back I moved one of my laptops from using Gnome to using a wm (i3
at present). I have been slowly trying to learn the various functions that
the Gnome DE does in the background (hides from the user) so that I can
replace the Gnome-related-software to software which is desktop
independent.
I'm a bit confused as to how to replace NetworkManager with wicd (using
both wired and wireless connections). After installing wicd, I thought
perhaps I could simply turn off NetworkManager, configure wicd, then when
I am satisfied everything works with wicd properly I will uninstall
NetworkManager. I am hoping that this approach won't leave me stranded
with an incomplete or non-working interface configurations.
I thought I could simply invoke
$sudo /etc/init.d/NetworkManager stop
to unload the Networkmanager daemon while playing around with configuring
wicd, but that doesn't work. I get:
$NetworkManager is already running (pid 3879)
So then I try to kill the process, but it automatically restarts in about
20-30 seconds.
So then I think maybe I should stop the networking daemon. But then, when
I restart it how do I tell the system to use wicd instead of
NetworkManager?
So I guess there's a bunch of stuff I still don't understand (duh!).
Is there a tutorial someone can point me to that would help educate me on
how best to approach this task? Or do I need to go cold-turkey and
uninstall NetworkManager before configuring wicd?
So far I am looking at:
http://wicd.sourceforge.net/download.php and
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html
Thanks,
Keith Ostertag
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/b682d188b6f11a39dc32...@webmail.strucktower.com
at present). I have been slowly trying to learn the various functions that
the Gnome DE does in the background (hides from the user) so that I can
replace the Gnome-related-software to software which is desktop
independent.
I'm a bit confused as to how to replace NetworkManager with wicd (using
both wired and wireless connections). After installing wicd, I thought
perhaps I could simply turn off NetworkManager, configure wicd, then when
I am satisfied everything works with wicd properly I will uninstall
NetworkManager. I am hoping that this approach won't leave me stranded
with an incomplete or non-working interface configurations.
I thought I could simply invoke
$sudo /etc/init.d/NetworkManager stop
to unload the Networkmanager daemon while playing around with configuring
wicd, but that doesn't work. I get:
$NetworkManager is already running (pid 3879)
So then I try to kill the process, but it automatically restarts in about
20-30 seconds.
So then I think maybe I should stop the networking daemon. But then, when
I restart it how do I tell the system to use wicd instead of
NetworkManager?
So I guess there's a bunch of stuff I still don't understand (duh!).
Is there a tutorial someone can point me to that would help educate me on
how best to approach this task? Or do I need to go cold-turkey and
uninstall NetworkManager before configuring wicd?
So far I am looking at:
http://wicd.sourceforge.net/download.php and
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html
Thanks,
Keith Ostertag
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/b682d188b6f11a39dc32...@webmail.strucktower.com
Lisi
Feb 12, 2012, 3:20:02 PM2/12/12
to
On Sunday 12 February 2012 19:44:33 kei...@strucktower.com wrote:
> Or do I need to go cold-turkey and
> uninstall NetworkManager before configuring wicd?
I did. And have never looked back. I deinstall network manager at the first
> Or do I need to go cold-turkey and
> uninstall NetworkManager before configuring wicd?
opportunity. You could always install it again. But telling it not to do
anything is the triumph of hope over experience!
Lisi
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Claudius Hubig
Feb 12, 2012, 3:30:02 PM2/12/12
to
kei...@strucktower.com wrote:
>Sometime back I moved one of my laptops from using Gnome to using a wm (i3
>at present). I have been slowly trying to learn the various functions that
>the Gnome DE does in the background (hides from the user) so that I can
>replace the Gnome-related-software to software which is desktop
>independent.
Network Manager per se is not connected to Gnome and runs just fine
>Sometime back I moved one of my laptops from using Gnome to using a wm (i3
>at present). I have been slowly trying to learn the various functions that
>the Gnome DE does in the background (hides from the user) so that I can
>replace the Gnome-related-software to software which is desktop
>independent.
with XFCE, KDE and even from the command line (you will have to
create connections manually, though).
>I thought I could simply invoke
>
>$sudo /etc/init.d/NetworkManager stop
# /etc/init.d/network-manager stop
? – The file /etc/init.d/NetworkManager isn’t even existing on my system.
Best regards,
Claudius
--
I'd horsewhip you if I had a horse.
-- Groucho Marx
Please use GPG: ECB0C2C7 4A4C4046 446ADF86 C08112E5 D72CDBA4
http://chubig.net/ http://nightfall.org
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Feb 12, 2012, 3:40:02 PM2/12/12
to
On Sun 12 Feb 2012 at 11:44:33 -0800, kei...@strucktower.com wrote:
> Is there a tutorial someone can point me to that would help educate me on
> how best to approach this task? Or do I need to go cold-turkey and
> uninstall NetworkManager before configuring wicd?
Normally I try to address the actual question asked, but when I see
> Is there a tutorial someone can point me to that would help educate me on
> how best to approach this task? Or do I need to go cold-turkey and
> uninstall NetworkManager before configuring wicd?
something like this I want to ask - is the machine always connected
to one network or is it roaming between networks? If its just one
network then about eight lines in /etc/network/interfaces will set
you up for life.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
Feb 12, 2012, 3:50:02 PM2/12/12
to
distributions but prefer NM.
One thing you should know is that the /etc/network/interfaces files are
VERY different. I have two different interfaces files and use a bash
script to choose which one to use.
< script to select wireless interface >
#!/bin/sh
# netup
wicd() {
# do Verizon setup
modprobe -r rtl8187
modprobe ath9k
cp /etc/network/interfaces-MiFi /etc/network/interfaces
sleep 5
service networking restart
sleep 5
service network-manager stop
wicd-curses
}
nm() {
modprobe -r ath9k
modprobe rtl8187
cp /etc/network/interfaces-wlan1 /etc/network/interfaces
sleep 5
service networking restart
sleep 5
service network-manager restart
sleep 5
ckif
ifup wlan1
echo "NM is setup."
}
task=$1
case "$task" in
wicd) wicd
;;
nm) nm
;;
* ) echo
echo "*** arg ( wice | nm ) required ***"
;;
esac
exit
--------------------------------------------------------
< the NM interface file >
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# Netgear wg111v2 rtl8187 module
#
# The primary network interface
allow-hotplug wlan1
iface wlan1 inet dhcp
modprobe rtl8187
wpa-ssid Verizon MiFi2200 C4B5 Secure
wpa-psk your-password-goes-here
--------------------------------------------------------
< the wicd interfaces file >
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# up route add -net 127.0.0.0 netmask 255.0.0.0 dev lo
# down route del -net 127.0.0.0 netmask 255.0.0.0 dev lo
# ------ For Verizon MiFi Network
# Using wicd on X
#
# Need to correct this for NON X use
# The primary network interface
##manual eth0
##iface eth0 inet static
## address 192.168.1.11
## network 192.168.1.0
## netmask 255.255.255.0
## broadcast 192.168.1.255
# gateway 192.168.1.11
## dns-nameservers 66.174.95.44 8.8.8.8 8.8.4.4
# dns-nameservers 209.183.33.23 209.183.35.23 192.168.1.11
## dns-search dns-domain dns-sortlist
--------------------------------------------------------
The EMPTY interfaces is how I, finally, got wicd to work.
I hope this helps you in getting one or both working.
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Davies
Feb 13, 2012, 5:30:02 AM2/13/12
to
kei...@strucktower.com wrote:
> I'm a bit confused as to how to replace NetworkManager with wicd (using
> both wired and wireless connections).
My understanding is that NM will not touch any interface that is defined
> I'm a bit confused as to how to replace NetworkManager with wicd (using
> both wired and wireless connections).
in /etc/network/interfaces. So, theoretically at least, if you simply
go ahead and declare the interfaces "it will all just work".
I've not used wicd so I can't give you specific information on configuring
the /etc/network/interfaces file.
Chris
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Feb 13, 2012, 9:20:02 AM2/13/12
to
On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies <chris-...@roaima.co.uk> wrote:
>
> My understanding is that NM will not touch any interface that is defined
> in /etc/network/interfaces. So, theoretically at least, if you simply
> go ahead and declare the interfaces "it will all just work".
Check "/etc/NetworkManager/NetworkManager.conf"
>
> My understanding is that NM will not touch any interface that is defined
> in /etc/network/interfaces. So, theoretically at least, if you simply
> go ahead and declare the interfaces "it will all just work".
If "managed=false" in the "ifupdown" section, NM will not manage
interfaces defined in "/etc/network/interfaces".
I'm not sure of the current behavior because I don't use NM but,
AFAIK, when NM's installed "managed" is set to "false" and NM comments
out interfaces that are configured in "/etc/network/interfaces" other
than "lo".
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
Feb 13, 2012, 11:40:02 AM2/13/12
to
On 02/13/2012 09:18 AM, Tom H wrote:
> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk> wrote:
>>
>> My understanding is that NM will not touch any interface that is defined
>> in /etc/network/interfaces. So, theoretically at least, if you simply
>> go ahead and declare the interfaces "it will all just work".
>
> Check "/etc/NetworkManager/NetworkManager.conf"
>
> If "managed=false" in the "ifupdown" section, NM will not manage
> interfaces defined in "/etc/network/interfaces".
>
Sorry that is incorrect.
> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk> wrote:
>>
>> My understanding is that NM will not touch any interface that is defined
>> in /etc/network/interfaces. So, theoretically at least, if you simply
>> go ahead and declare the interfaces "it will all just work".
>
> Check "/etc/NetworkManager/NetworkManager.conf"
>
> If "managed=false" in the "ifupdown" section, NM will not manage
> interfaces defined in "/etc/network/interfaces".
>
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
/etc/NetworkManager/NetworkManager.conf (END)
And this is being sent via NM .
> I'm not sure of the current behavior because I don't use NM but,
> AFAIK, when NM's installed "managed" is set to "false" and NM comments
> out interfaces that are configured in "/etc/network/interfaces" other
> than "lo".
>
>
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Feb 13, 2012, 12:30:03 PM2/13/12
to
On Mon, Feb 13, 2012 at 11:38 AM, Wayne Topa <linu...@gmail.com> wrote:
> On 02/13/2012 09:18 AM, Tom H wrote:
>> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk>
>> wrote:
>>>
>>> My understanding is that NM will not touch any interface that is defined
>>> in /etc/network/interfaces. So, theoretically at least, if you simply
>>> go ahead and declare the interfaces "it will all just work".
>>
>> Check "/etc/NetworkManager/NetworkManager.conf"
>>
>> If "managed=false" in the "ifupdown" section, NM will not manage
>> interfaces defined in "/etc/network/interfaces".
>
> Sorry that is incorrect.
What's incorrect?
> On 02/13/2012 09:18 AM, Tom H wrote:
>> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk>
>> wrote:
>>>
>>> My understanding is that NM will not touch any interface that is defined
>>> in /etc/network/interfaces. So, theoretically at least, if you simply
>>> go ahead and declare the interfaces "it will all just work".
>>
>> Check "/etc/NetworkManager/NetworkManager.conf"
>>
>> If "managed=false" in the "ifupdown" section, NM will not manage
>> interfaces defined in "/etc/network/interfaces".
>
> Sorry that is incorrect.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
Feb 13, 2012, 1:50:02 PM2/13/12
to
On 02/13/2012 12:20 PM, Tom H wrote:
> On Mon, Feb 13, 2012 at 11:38 AM, Wayne Topa<linu...@gmail.com> wrote:
>> On 02/13/2012 09:18 AM, Tom H wrote:
>>> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk>
>>> wrote:
>>>>
>>>> My understanding is that NM will not touch any interface that is defined
>>>> in /etc/network/interfaces. So, theoretically at least, if you simply
>>>> go ahead and declare the interfaces "it will all just work".
>>>
>>> Check "/etc/NetworkManager/NetworkManager.conf"
>>>
This statement
> On Mon, Feb 13, 2012 at 11:38 AM, Wayne Topa<linu...@gmail.com> wrote:
>> On 02/13/2012 09:18 AM, Tom H wrote:
>>> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk>
>>> wrote:
>>>>
>>>> My understanding is that NM will not touch any interface that is defined
>>>> in /etc/network/interfaces. So, theoretically at least, if you simply
>>>> go ahead and declare the interfaces "it will all just work".
>>>
>>> Check "/etc/NetworkManager/NetworkManager.conf"
>>>
>>> If "managed=false" in the "ifupdown" section, NM will not manage
>>> interfaces defined in "/etc/network/interfaces".
>> Sorry that is incorrect.
>
> What's incorrect?
My NetworkMansger.conf file does have "managed=false" and my
>>> interfaces defined in "/etc/network/interfaces".
>> Sorry that is incorrect.
>
> What's incorrect?
interfaces file
has only one interface listed and I am using it to send this message.
ifup/down works just as it should.
I sent that information in my last post. Wasn't it clear?
WT
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Feb 13, 2012, 2:50:02 PM2/13/12
to
On Mon, Feb 13, 2012 at 1:47 PM, Wayne Topa <linu...@gmail.com> wrote:
> On 02/13/2012 12:20 PM, Tom H wrote:
>> On Mon, Feb 13, 2012 at 11:38 AM, Wayne Topa<linu...@gmail.com> wrote:
>>> On 02/13/2012 09:18 AM, Tom H wrote:
>>>> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk>
>>>> wrote:
>>>>>
>>>>> My understanding is that NM will not touch any interface that is
>>>>> defined
>>>>> in /etc/network/interfaces. So, theoretically at least, if you simply
>>>>> go ahead and declare the interfaces "it will all just work".
>>>>
>>>> Check "/etc/NetworkManager/NetworkManager.conf"
>>>>
>
> This statement
>>>>
>>>> If "managed=false" in the "ifupdown" section, NM will not manage
>>>> interfaces defined in "/etc/network/interfaces".
>
>>> Sorry that is incorrect.
>>
>> What's incorrect?
>
> My NetworkMansger.conf file does have "managed=false" and my interfaces
> file
> has only one interface listed and I am using it to send this message.
> ifup/down works just as it should.
>
> I sent that information in my last post. Wasn't it clear?
No, it wasn't clear (to me).
> On 02/13/2012 12:20 PM, Tom H wrote:
>> On Mon, Feb 13, 2012 at 11:38 AM, Wayne Topa<linu...@gmail.com> wrote:
>>> On 02/13/2012 09:18 AM, Tom H wrote:
>>>> On Mon, Feb 13, 2012 at 4:54 AM, Chris Davies<chris-...@roaima.co.uk>
>>>> wrote:
>>>>>
>>>>> My understanding is that NM will not touch any interface that is
>>>>> defined
>>>>> in /etc/network/interfaces. So, theoretically at least, if you simply
>>>>> go ahead and declare the interfaces "it will all just work".
>>>>
>>>> Check "/etc/NetworkManager/NetworkManager.conf"
>>>>
>
> This statement
>>>>
>>>> If "managed=false" in the "ifupdown" section, NM will not manage
>>>> interfaces defined in "/etc/network/interfaces".
>
>>> Sorry that is incorrect.
>>
>> What's incorrect?
>
> My NetworkMansger.conf file does have "managed=false" and my interfaces
> file
> has only one interface listed and I am using it to send this message.
> ifup/down works just as it should.
>
> I sent that information in my last post. Wasn't it clear?
I was 100% of what I wrote when I wrote it and am now 99% sure. Since
I was writing from memory, I'll have check the docs and find
references to NM and ifup being managed/unmanaged.
Maybe your NIC's being brought up by "/etc/init.d/networking" (since
it's defined in "/etc/network/interfaces") and not by
"/etc/init.d/network-manager". (Can "/etc/init.d/networking" and
"/etc/init.d/network-manager" be enabled simultaneously by insserv?)
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Feb 13, 2012, 3:00:02 PM2/13/12
to
be interesting to know).
In the script that you posted earlier in this thread, you activate NM
but then bring up your NIC with "ifup", which is in accord with what
I've posted. So it's not NM that's bringing up your NIC if you have
"managed=false" in "/etc/NetworkManager/NetworkManager.conf".
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Feb 13, 2012, 3:10:01 PM2/13/12
to
>From http://live.gnome.org/NetworkManager/SystemSettings
<begin>
The ifupdown plugin also uses the
/etc/NetworkManager/nm-system-settings.conf file (0.7 and 0.8.0) or
NetworkManager.conf (0.8.1 and later) for some configuration. All
ifupdown-specific options go in a "[ifupdown]" section. If the
"managed" key is set to "false", then any device listed in
/etc/network/interfaces will be completely ignored by NetworkManager.
Remember that NetworkManager controls the default route, so because
the device is hidden, NetworkManager will assign the default route to
some other device.
</end>
>From http://wiki.debian.org/NetworkManager
<begin>
If you want NetworkManager to handle interfaces that are enabled in
/etc/network/interfaces:
Set managed=true in /etc/NetworkManager/NetworkManager.conf.
</end>
>From "/usr/share/doc/network-manager/README.Debian"
<begin>
Managed vs. Unmanaged mode and /etc/network/interfaces
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Devices listed in /etc/network/interfaces _will_ be managed by NetworkManager
unless the ifupdown system-config-setting is enabled and is setup to run
in "Unmanaged mode".
The config to select unmanaged/managed mode is in
/etc/NetworkManager/NetworkManager.conf:
[ifupdown]
managed=true/false
Unmanaged mode will make NetworkManager not touch any wired/wireless device
matching an interface name configured in /etc/network/interfaces.
Managed mode will make NetworkManager manage all devices and will make
NetworkManager honour all dhcp and static configurations for wired and
wireless devices.
After modifying /etc/NetworkManager/NetworkManager.conf _or_
/etc/network/interfaces you may want to tell NetworkManager about the changes
by running "service network-manager restart".
</end>
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
Feb 13, 2012, 7:00:03 PM2/13/12
to
iwconfig. ifdown wlan1 takes it down and ifup brings it back up,
and, NM is not running as shown by ps aux. What the heck?
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Tom H
Feb 13, 2012, 11:10:01 PM2/13/12
to
On Mon, Feb 13, 2012 at 6:58 PM, Wayne Topa <linu...@gmail.com> wrote:
> On 02/13/2012 03:06 PM, Tom H wrote:
>>
>> From http://live.gnome.org/NetworkManager/SystemSettings
>>
>> <begin>
>> The ifupdown plugin also uses the
>> /etc/NetworkManager/nm-system-settings.conf file (0.7 and 0.8.0) or
>> NetworkManager.conf (0.8.1 and later) for some configuration. All
>> ifupdown-specific options go in a "[ifupdown]" section. If the
>> "managed" key is set to "false", then any device listed in
>> /etc/network/interfaces will be completely ignored by NetworkManager.
>> Remember that NetworkManager controls the default route, so because
>> the device is hidden, NetworkManager will assign the default route to
>> some other device.
>> </end>
>
> On 02/13/2012 03:06 PM, Tom H wrote:
>>
>> From http://live.gnome.org/NetworkManager/SystemSettings
>>
>> <begin>
>> The ifupdown plugin also uses the
>> /etc/NetworkManager/nm-system-settings.conf file (0.7 and 0.8.0) or
>> NetworkManager.conf (0.8.1 and later) for some configuration. All
>> ifupdown-specific options go in a "[ifupdown]" section. If the
>> "managed" key is set to "false", then any device listed in
>> /etc/network/interfaces will be completely ignored by NetworkManager.
>> Remember that NetworkManager controls the default route, so because
>> the device is hidden, NetworkManager will assign the default route to
>> some other device.
>> </end>
>
> Then I am stumped. If I kill NM the interface is still up says iwconfig.
> ifdown wlan1 takes it down and ifup brings it back up,
> and, NM is not running as shown by ps aux. What the heck?
It's because NM isn't in control of your NIC, which is being brought
> ifdown wlan1 takes it down and ifup brings it back up,
> and, NM is not running as shown by ps aux. What the heck?
up in your script by "ifup wlan1" using "iface wlan1 inet dhcp; mod
probe rtl8187; wpa-ssid Verizon MiFi2200 C4B5 Secure; wpa-psk
your-password-goes-here" in "/etc/network/interfaces".
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Martin Steigerwald
Feb 14, 2012, 5:10:02 PM2/14/12
to
Hi Claudius, hi everyone,
Am Sonntag, 12. Februar 2012 schrieb Claudius Hubig:
> kei...@strucktower.com wrote:
> >Sometime back I moved one of my laptops from using Gnome to using a wm
> >(i3 at present). I have been slowly trying to learn the various
> >functions that the Gnome DE does in the background (hides from the
> >user) so that I can replace the Gnome-related-software to software
> >which is desktop independent.
>
> Network Manager per se is not connected to Gnome and runs just fine
> with XFCE, KDE and even from the command line (you will have to
> create connections manually, though).
No, at least not for KDE. Just use plasma-widget-networkmanagement which
in the meanwhile became quite nice. The version in wheezy/sid is nicer
than in squeeze. But the same is true for network manager it self.
Network Manager 0.9 was the first version that I really found usable.
Before I tried wicd sometimes, but either the KDE/GTK guis of it did not
respond to clicks or wicd did some wierd misconfiguration - AFAIR it
changed hostname to what was told by DHCP which is an absolute no-go to me
since it breaks DBUS and more. After that last occurence I ditched wicd
faster than you can spell apt-get purge - so to say. (I had this with
earlier versions of network-manager as well, I purged it quite a lot.;)
Network Manager 0.9+ is fine for me. It connects to every WLAN I thrown at
it, including the WPA PSK RADIUS - insert some more bull^W^W^W acronyms to
make you happy - whatnot WLAN at work. I simply put in the data I was told
to use for authentification and it worked out of the box. And at a customer
it was just the same, told data and it worked. That wasn´t that
consistently the case for me with earlier versions of network manager.
Heck, Network Manager 0.9+ even retries DHCP several times which helps
while my ASUS WL-500g Premium router boots Debian from the USB-Stick after
it loaded the Linux kernel from internal flash - for some reasons that
sometimes takes longer.
So this new version of Network Manager was really a pleasant surprise to
me as I disliked previous versions quite much. First time I do not need to
know how it works. Like in K3b for CD/DVD burning and copying ;).
Only thing I did have some issue was OpenVPN, but I only tried it once and
maybe I misconfigured it.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/201202142303...@lichtvoll.de
Am Sonntag, 12. Februar 2012 schrieb Claudius Hubig:
> kei...@strucktower.com wrote:
> >Sometime back I moved one of my laptops from using Gnome to using a wm
> >(i3 at present). I have been slowly trying to learn the various
> >functions that the Gnome DE does in the background (hides from the
> >user) so that I can replace the Gnome-related-software to software
> >which is desktop independent.
>
> Network Manager per se is not connected to Gnome and runs just fine
> with XFCE, KDE and even from the command line (you will have to
> create connections manually, though).
in the meanwhile became quite nice. The version in wheezy/sid is nicer
than in squeeze. But the same is true for network manager it self.
Network Manager 0.9 was the first version that I really found usable.
Before I tried wicd sometimes, but either the KDE/GTK guis of it did not
respond to clicks or wicd did some wierd misconfiguration - AFAIR it
changed hostname to what was told by DHCP which is an absolute no-go to me
since it breaks DBUS and more. After that last occurence I ditched wicd
faster than you can spell apt-get purge - so to say. (I had this with
earlier versions of network-manager as well, I purged it quite a lot.;)
Network Manager 0.9+ is fine for me. It connects to every WLAN I thrown at
it, including the WPA PSK RADIUS - insert some more bull^W^W^W acronyms to
make you happy - whatnot WLAN at work. I simply put in the data I was told
to use for authentification and it worked out of the box. And at a customer
it was just the same, told data and it worked. That wasn´t that
consistently the case for me with earlier versions of network manager.
Heck, Network Manager 0.9+ even retries DHCP several times which helps
while my ASUS WL-500g Premium router boots Debian from the USB-Stick after
it loaded the Linux kernel from internal flash - for some reasons that
sometimes takes longer.
So this new version of Network Manager was really a pleasant surprise to
me as I disliked previous versions quite much. First time I do not need to
know how it works. Like in K3b for CD/DVD burning and copying ;).
Only thing I did have some issue was OpenVPN, but I only tried it once and
maybe I misconfigured it.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Martin Steigerwald
Feb 14, 2012, 5:10:02 PM2/14/12
to
Am Montag, 13. Februar 2012 schrieb Chris Davies:
> kei...@strucktower.com wrote:
> > I'm a bit confused as to how to replace NetworkManager with wicd
> > (using both wired and wireless connections).
>
> My understanding is that NM will not touch any interface that is
> defined in /etc/network/interfaces. So, theoretically at least, if you
> simply go ahead and declare the interfaces "it will all just work".
There is one disadvantage with that:
> kei...@strucktower.com wrote:
> > I'm a bit confused as to how to replace NetworkManager with wicd
> > (using both wired and wireless connections).
>
> My understanding is that NM will not touch any interface that is
> defined in /etc/network/interfaces. So, theoretically at least, if you
> simply go ahead and declare the interfaces "it will all just work".
Online detection in apps can be flaky. Network Manager reports offline when
all of its managed interfaces are offline. No matter whether another
interface it does not manage is online.
This even caused the famous I can´t surf with Iceweasel issue since
Firefox/Iceweasel switched to offline mode when Network Manager reports
being offline. Or the weather applet of KDE did not work and stuff like that.
So I am happy that Network Manager 0.9+ can it all for me now, although I
do not agree to the report "offline" even when you do not actually now it
for sure approach.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/201202142308...@lichtvoll.de
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages