Re: Problem with NetworkManager - WAS: Re: Help needed to repair a damaged dual boot Debian System
Bernard, 5.03.2012:
> Tom H wrote:
> >On Sun, Mar 4, 2012 at 8:43 AM, Bernard <bdebreil@teaser.fr> wrote:
> >>Selim T. Erdogan wrote:
> >>>Andrei POPESCU, 3.03.2012:
> >>>>On Sb, 03 mar 12, 20:59:30, Bernard wrote:
> >>>>>Thanks in advance for your help with the 'NetworkManager' or any
> >>>>>other convenient tool that would operate on Squeeze so as to easily
> >>>>>turn an Internet connexion ON and OFF
> >>>>Make sure you have NO definition for eth0 in /etc/network/interfaces and
> >>>>that you have:
> >>>>
> >>>>[ifupdown]
> >>>>managed=false
> >>>>
> >>>>in /etc/NetworkManager/NetworkManager.conf
> >>>>
> >>>>If it still doesn't work after a restart[1] please attach both files.
> >>>>
> >>>>[1] not sure why, but in some cases new configurations did not work
> >>>>properly until a full restart
> >>>Or you can keep /etc/network/interfaces as you have it now and edit
> >>>/etc/NetworkManager/NetworkManager.conf to have
> >>>
> >>>[main]
> >>>plugins=ifupdown,keyfile
> >>>
> >>>[ifupdown]
> >>>managed=true
> >>>
> >>>(And you have to restart Network Manager.)
> >>I just tested both ways, to no avail.
> >>
> >>At first, I must say that my system did not have any
> >>
> >>NetworkManager.conf file in /etc/NetworkManager/
> >>
> >>The only NetworkManager.conf file that could be found on this system was in
> >>
> >>/etc/dbus-1/system.d/
> >>
> >>I can see the same thing on this other machine still on Lenny, where I am
> >>writing this from: no /etc/NetworkManager/NetworkManager.conf file either.
> >>
> >>the man page for NetworkManager does not mention any such conf file. I did
> >>not dare modifying /etc/dbus-1/system.d/NetworkManager.conf
> >>
> >>But I tested creating an /etc/NetworkManager/NetworkManager.conf, with only
> >>****************************
> >>
> >>[main]
> >>plugins=ifupdown,keyfile
> >>
> >>[ifupdown]
> >>managed=false
> >>******************************
> >>
> >>As a first trial, I had just written:
> >>
> >>***********************
> >>[ifupdown]
> >>managed=false
> >>*************************
> >>
> >>in it. But maybe I should have modified permissions and owner ? Owner was
> >>root and perms: -rw-r--r--
> >>
> >>Besides, my /etc/network/interfaces file did not contain any definition for
> >>eth0. Still, I tested removing any mention of eth0, to no avail.
> >>
> >>Below is my 'etc/network/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
> >>
> >># The primary network interface
> >>allow-hotplug eth0
> >>iface eth0 inet dhcp
> >>
> >>*********************************************
> >
> >The file in "/etc/dbus-1/system.d/" is useful (to systems) if you have
> >systemd installed.
> >
> >Do you have network access?
> >
> >With your current setup, "managed=false" and eth0 defined in
> >"/etc/network/interfaces" you can control eth0 with ifup and if down.
> >
> >With "managed=true", you'd have to use NM to bring up or take down eth0.
> >
> >
> I just don't understand what happens. Whatever I try with
> 'NetworkManager'... FAILS ! Besides, as previously stated, I have
> tried to install 'wicd'... It did install all right, and worked as
> far as disconnecting was concerned, but no way to reconnect except
> on a re-boot. Now that I wish to get rid of 'wicd', just in case it
> would interfer with 'NetworkManager', I can't get rid of it !
>
> #apt-get remove wicd
>
> did remove it, so it said... if I try to remove it again, it says
> that it is no longer there... however, I can still see 'wicd network
> manager' on my gnome desktop, and, if I launch it, it still
> disconnects my Internet link, and is still unable to reconnect it !
There may be other wicd-related packages still installed. Try
dpkg --get-selections wicd*
> Now, if I try
>
> #ifup and #ifdown eth0, it seems to work... I repeat: it "SEEMS TO
> WORK" but it does not REALLY work !! Here is what I see:
>
> #ifup eth0
>
> ..........
> .......
> receive packet failed on eth0: Network is down
> ..................................
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
> DHCPOFFER from 192.168.1.1
> DHCPREQUEST on eth0...............
> DHCPACK form 192.168.1.1
> SIOCADDRT: File exists
> bound to 192.168.1.15 -- renewal in 40322 seconds.
> #
>
> at this point, if I start again the command:
>
> #ifup eth0
>
> I get this:
>
> ifup: interface eth0 already configured (which I agree was expected
> as normal !)
>
> ifdown disconfigure eth0 ; ifup reconfigures it... Except that,
> whether it is configured or disconfigured, the network (the Internet
> network) is up and running, as if it did not care whether ifup had
> it configured or not ! (I must state that I have no wireless
> connexion on this machine, just one wired ethernet connexion, no
> more).
>
> Ooh... Well... let me see... I just finished testing something... As
> previously stated, 'wicd' only works in the purpose of disconnecting
> ; it never reconnects ; it does that job even though I have
> supposedly removed it... I just tested disconnecting with wicd...
> and now that it is really disconnected, I can REALLY reconnect with
> '#ifup eth0' and REALLY disconnect using '#ifdown eth0', back and
> forth as many times as I wish... provided that I have first
> disconnected - using 'wicd' - the connexion that occured
> automatically upon boot !
>
> I hope that these symptoms might help someone to understand what is
> wrong with my settings..
Sounds like when you turn off wicd, then ifup and ifdown work the way
you want them to.
Reply to: