Fedora 17
NetworkManager is changing Nameserver in resolv.conf to 192.168.1.1 my Router gateway and my setting in /etc/sysconfig/network- scripts/cfg-p128p1 (eth0) are as such.
UUID="e676da02-6018-4567-8c0f-ab849ac673cb" NM_CONTROLLED="yes" HWADDR="78:E3:B5:95:98:2C" BOOTPROTO="dhcp" DEVICE="p128p1" ONBOOT="yes" PEERDNS=yes DNS1=8.8.8.8 DNS2=8.8.0.0
How do I get NM to accept the above settings ?
On 10/20/2012 01:46 PM, Jim wrote:
How do I get NM to accept the above settings ?
Set /etc/resolv.conf with your DNS data, disable NM completely and let network handle things. I did that several years ago because NM insisted on blanking out my DNS settings every time I rebooted and I've never looked back.
Jim writes:
Fedora 17
NetworkManager is changing Nameserver in resolv.conf to 192.168.1.1 my Router gateway and my setting in /etc/sysconfig/network- scripts/cfg-p128p1 (eth0) are as such.
UUID="e676da02-6018-4567-8c0f-ab849ac673cb" NM_CONTROLLED="yes" HWADDR="78:E3:B5:95:98:2C" BOOTPROTO="dhcp" DEVICE="p128p1" ONBOOT="yes" PEERDNS=yes DNS1=8.8.8.8 DNS2=8.8.0.0
How do I get NM to accept the above settings ?
Get rid of the PEERDNS setting.
On 10/21/2012 05:29 AM, Jim wrote:
On 10/20/2012 04:55 PM, Sam Varshavchik wrote:
Get rid of the PEERDNS setting.
Getting rid of the PEERDNS setting did not help..
PEERDNS=<answer>, where <answer> is one of the following:
yes — This interface will modify your system's /etc/resolv.conf file entries to use the DNS servers provided by the remote system when a connection is established.
no — The /etc/resolv.conf file will not be changed.
It is possible that the default is "yes" in the absence of the parameter.
Make it PEERDNS=no. While I've been lazy as of late and use the GUI. I have set Method for IPV4 to "Automatic (DHCP) addresses only" which results in the resolv.conf not being touch and the following in the configuration file...
UUID="a8ca1d90-45fd-462c-8162-29093223af83" NM_CONTROLLED="yes" BOOTPROTO="dhcp" DEVICE="p2p1" ONBOOT="yes" HWADDR=08:00:27:F1:1A:38 TYPE=Ethernet DNS1=192.168.0.55 DOMAIN=greshko.com DEFROUTE=yes PEERDNS=no PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System p2p1"
On 10/20/2012 09:31 PM, Ed Greshko wrote:
On 10/21/2012 05:29 AM, Jim wrote:
On 10/20/2012 04:55 PM, Sam Varshavchik wrote:
Get rid of the PEERDNS setting.
Getting rid of the PEERDNS setting did not help..
PEERDNS=<answer>, where <answer> is one of the following:
yes — This interface will modify your system's /etc/resolv.conf file entries to use the DNS servers provided by the remote system when a connection is established.
no — The /etc/resolv.conf file will not be changed.
It is possible that the default is "yes" in the absence of the parameter.
Make it PEERDNS=no. While I've been lazy as of late and use the GUI. I have set Method for IPV4 to "Automatic (DHCP) addresses only" which results in the resolv.conf not being touch and the following in the configuration file...
UUID="a8ca1d90-45fd-462c-8162-29093223af83" NM_CONTROLLED="yes" BOOTPROTO="dhcp" DEVICE="p2p1" ONBOOT="yes" HWADDR=08:00:27:F1:1A:38 TYPE=Ethernet DNS1=192.168.0.55 DOMAIN=greshko.com DEFROUTE=yes PEERDNS=no PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System p2p1"
Setting PEERDNS=no did not help, I guess I will have to uninstall NetworkManager, I unistalled NetworkManager and it also uninstalled anaconda.
I can start "network" and get the network up. But it won't start after bootup, Why ?
Am 21.10.2012 20:58, schrieb Jim:
Setting PEERDNS=no did not help, I guess I will have to uninstall NetworkManager, I unistalled NetworkManager and it also uninstalled anaconda.
who needs anaconda on a running setup.... but you could disable it without uninstall
I can start "network" and get the network up. But it won't start after bootup, Why?
because you have to enable it like any other service
[root@srv-rhsoft:~]$ systemctl disable network.service network.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig network off [root@srv-rhsoft:~]$ systemctl enable network.service network.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig network on
On 21.10.2012 20:58, Jim wrote:
On 10/20/2012 09:31 PM, Ed Greshko wrote:
On 10/21/2012 05:29 AM, Jim wrote:
On 10/20/2012 04:55 PM, Sam Varshavchik wrote:
Get rid of the PEERDNS setting.
Getting rid of the PEERDNS setting did not help..
PEERDNS=<answer>, where <answer> is one of the following:
yes — This interface will modify your system's /etc/resolv.conf file entries to use the DNS servers provided by the remote system when a connection is established.
no — The /etc/resolv.conf file will not be changed.
It is possible that the default is "yes" in the absence of the parameter.
Make it PEERDNS=no. While I've been lazy as of late and use the GUI. I have set Method for IPV4 to "Automatic (DHCP) addresses only" which results in the resolv.conf not being touch and the following in the configuration file...
UUID="a8ca1d90-45fd-462c-8162-29093223af83" NM_CONTROLLED="yes" BOOTPROTO="dhcp" DEVICE="p2p1" ONBOOT="yes" HWADDR=08:00:27:F1:1A:38 TYPE=Ethernet DNS1=192.168.0.55 DOMAIN=greshko.com DEFROUTE=yes PEERDNS=no PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System p2p1"
Setting PEERDNS=no did not help, I guess I will have to uninstall NetworkManager, I unistalled NetworkManager and it also uninstalled anaconda.
I can start "network" and get the network up. But it won't start after bootup, Why ?
Because it's not enabled in systemd by default. Try command: systemctl enable network.service .
Mateusz Marzantowicz
-
Ed Greshko -
Joe Zeff -
Mateusz Marzantowicz -
Mickey -
Reindl Harald -
Sam Varshavchik