network-manager

Zach uid000 at gmail.com
Tue Nov 15 21:04:01 UTC 2005


Yes that sounds similar to my problem as well.  Couldn't resolve any
hosts on the lan.

Unfortunately, i've already uninstalled network-manager and bind, so I
can't try your suggestion, but maybe I'll try it again later.

However, I don't like that network-manager takes over my
/etc/resolv.conf.  I get dns assigned by dhcp, and anything besides
that is an unecessary layer of complexity.  I'm not sure why
network-manager requires a local dns server, but I hope that get that
resolved before it goes into Ubuntu.

The other thing I didn't like is that it wanted to use the gnome
keyring manager to track my wep key, which prompted for a passphrase
once per login (or per boot, can't remember).  Prior to installing
network-manager my wep key was configured globally in
/etc/network/interfaces, and I don't know why it couldn't/wouldn't
work with that.

On 11/15/05, Stephen Ryan <taketwoaspirin at gmail.com> wrote:
> On 11/15/05, Zach <uid000 at gmail.com> wrote:
> > I'm in agreement.  I'm removing it because of it's bind9 requirement.
> > every since I installed it dns has been flakey, and since I am
> > unfamliar with how bind works, I am not able to configure or
> > troubleshoot it.  network-manager would be great if it were simpler.
>
>  I think dns is flaky because there are two copies of bind running; I killed
> the second one  and dns suddenly became much more reliable (well, until I
> dropped the laptop on the floor and the whole thing stopped working
> permanently, it was more reliable, anyway!)
>
>
> One copy is started at boot, by the bind package, as a regular name server,
> and the other is started by nm, as a caching / forwarding name server.  I
> discovered this because I run an internal nameserver in my house, and the
> hostname for my server wasn't being recognized, which meant that it was
> bypassing the local nameserver supplied by DHCP.
>
>  Run
>
>  $ ps axf
>
>  and look for two copies of named, with different parameters.  One should
> look something like "named .... -c
> /usr/lib/NetworkManager/named.conf", the other should not
> have a "-c ...." parameter.  (I'm doing this from memory, and this is surely
> wrong; after I get my laptop repaired I can provide more details.)
>
>  I adjusted the symlinks in /etc/rc?.d/ to never start named so that I
> wouldn't have the problem again.
>
>


--
If you reply to a message I posted to a mailing list,
and you want me to see your reply, be sure to put my
address in the 'To:', or I might not see the message.




More information about the ubuntu-users mailing list