On Mon, 15 Aug 2011 16:39:54 +0000, Steve Kleene wrote:
> On Mon, 15 Aug 2011 16:14:56 +0000 (UTC), Camaleón wrote:
>
>> NM calls -by default- "dhclient", so... is NM running?
>
> Yes, it is running on each of the two machines.
"Arghh!!!" I mean... "ahh", that explains your pain :-P
>> If so, stop NM ("/etc/init.d/network-manager stop") or kill "dhclient"
>> process and then restart the network service (also run ifdown/ifup,
>> just to be sure). After that run "ifconfig" to check the current IP. If
>> that solves your problem, just disable NM and your happiness will
>> inmediately start :-)
>
> Doing just this:
> cd /etc/init.d; network-manager stop; networking restart
>
> gave me the desired static IP. Then I ran this:
>
> cd /etc/rc3.d; mv S03network-manager K97network-manager
>
> rebooted and again got the desired static IP.
Just for the record. Last time I had to disable NM (disable, not
removing) I finally used:
update-rc.d network-manager disable
Which does -more or less- what you did.
> So assuming I won't miss network-manager, all is well. I still don't
> understand why the other box, which is still running network-manager and
> a static IP, doesn't have this problem. They're both running updated
> Wheezy.
Mmm... now that you have found the culprit you can make additional tests
with NM. For instance, you can start NM service but instructing it to use
a static IP instead using DHCP (this can be done from the system tray
applet). This way no dhclient service should be called nor run in
background.
> Anyway, now I can get back to my real job. Thanks again.
Glad to know the mistery has been solved :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.08.15.19.11...@gmail.com
