Re: NetworkManager causin problems with DNS settings.

2012-10-22 Thread Reindl Harald
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" a

Re: NetworkManager causin problems with DNS settings.

2012-10-22 Thread Mateusz Marzantowicz
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=, where is one of the following

Re: NetworkManager causin problems with DNS settings.

2012-10-21 Thread Jim
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=, where is one of the following: yes — This interface will modify your system

Re: NetworkManager causin problems with DNS settings.

2012-10-20 Thread Ed Greshko
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=, where is one of the following: yes — This interface will modify your system's /etc/resolv.conf file entries to use

Re: NetworkManager causin problems with DNS settings.

2012-10-20 Thread Jim
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.. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: h

Re: NetworkManager causin problems with DNS settings.

2012-10-20 Thread Sam Varshavchik
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" BOOTPROT

Re: NetworkManager causin problems with DNS settings.

2012-10-20 Thread Joe Zeff
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 nev

NetworkManager causin problems with DNS settings.

2012-10-20 Thread Jim
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=