On Mon, Aug 15, 2011 at 12:14 PM, Camaleón <noela...@gmail.com> wrote:
> (...)
>
> NM calls -by default- "dhclient", so... is NM running?
>
> 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 :-)
Rip NetworkManager *out*, if at all feasible. Like having a too-long
password that you cannot remember, it has its rare uses, but is far,
far more likely to break things in a stable network environment.
--
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/CAOCN9rwgci=ArA80ppfAFF7vSLtQjHv2B2sogKsF=h3egve...@mail.gmail.com
