NetworkManager

[NoOp]

On 10/07/2008 02:03 PM, Leonard Chatagnier wrote:
> --- On Tue, 10/7/08, Derek Broughton <news at pointerstop.ca> wrote:
> From: Derek Broughton <news at pointerstop.ca>
> Subject: Re: NetworkManager
> To: ubuntu-users at lists.ubuntu.com
> Date: Tuesday, October 7, 2008, 9:58 AM
> 
> lchata at ubuntu-hardy-64bit:/etc/init.d$ cat /etc/resolv.conf
> ### BEGIN INFO
> #
> # Modified_by:  NetworkManager
> # Process:      /usr/bin/NetworkManager
> # Process_id:   5207
> #
> ### END INFO
> 
> search gateway.2wire.net
> 
> 
> nameserver 192.168.1.254
> 
> 
> lchata at ubuntu-hardy-64bit:/etc/init.d$
> 

/etc/resolv.conf _absolutely_ gets written to by the network manager
when using "Roaming" as you can see from the above. That is how
"Roaming" mode works. As Leonard has shown, it's easy to demontrate this:

1. Open NM and remove any existing DNS entries except for the router
gateway (leave the NM dialog open for all of the following).

Set NM for "Roaming mode" and
sudo /etc/init.d/networking restart
cat /etc/resolv.conf

You will see that Network Manager wrote into the /etc/resolv.conf file
as shown in Leonard's output.

2. Now go back to NM and set it for DHCP. You will see that the

### BEGIN INFO
#
# Modified_by:  NetworkManager
# Process:      /usr/bin/NetworkManager

*is now gone* and instead only the nameserver entries obtained from the
gateway remain:

nameserver xxx.xxx.xxx.xxx

3. Now go back to NM and set it for a static IP address. Same as 2 above.

4. Now go back and repeat #1 above (set NM for Roaming mode). You will
again see the "Modified_by:  NetworkManager" entries. Nice touch - NM
tells you that it has modified resolv.conf and what it's process ID is.

It's too bad that other processes (dhclient, openvpn etc) don't write in
the "Modified by" as NetworkManger does.

Anyway...

http://www.google.com/search?hl=en&q=Ubuntu+%2Bnetwork+manager+%2Bresolv.conf

BTW: Leonard, why are you set for roaming mode? I'd set for static IP's
in your particular setup, or just standard DHCP. Also instead of setting
your DNS to "search gateway.2wire.net" just enter the IP address of
gateway.2wire.net (192.168.1.254) in the DNS box (above the Search
Domains) and your dns resolution will be faster... it doesn't need to
resolve gateway.2wire.net first. Or for even faster, put in your DNS's
directly instead of 192.168.1.254:

nameserver 68.94.156.1
nameserver 68.94.157.1