FIXED - Re: F20 - broken ethernet setup in NetworkManager?

[Robert Moskowitz]

On 01/26/2015 07:53 AM, Robert Moskowitz wrote:
>
> On 01/26/2015 12:10 AM, Ed Greshko wrote:
>> On 01/26/15 12:42, Robert Moskowitz wrote:
>>> On 01/25/2015 11:09 PM, Robert Moskowitz wrote:
>>>> On 01/25/2015 09:36 PM, Ed Greshko wrote:
>>>>> On 01/26/15 09:24, Robert Moskowitz wrote:
>>>>>> What else should I try?
>>>>> I don't use the command line interface to NM.
>>>>>
>>>>> But, if the only problem you're having is with PEERDNS not being 
>>>>> set correctly for you needs then why not just edit the appropriate 
>>>>> ifcfg accordingly?
>>>> Thinking that.  Was suspecting that something would just change it 
>>>> back.
>>> Well I tried changing it, and nothing different happened. Rebooted, 
>>> and it is back to PEERDNS=no
>>>
>>> So NM foo is controlling the content of this file.  Just like it is 
>>> not setting up /etc/resolv.conf as it should.
>>>
>> I have never encountered PEERDNS being changed once set.
>>
>> Care to post the contents of your ifcfg?
>>
>> With PEERDNS=no I always get the info in /etc/resolv.conf reflecting 
>> what is defined as DNSX= in the config.  And with PEERDNS=yes I 
>> always get the information being supplied by my DHCP server.
>
> TYPE=Ethernet
> BOOTPROTO=dhcp
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> NAME=Wired
> UUID=975503fd-b62a-4784-bd17-6d3e4b07e9e9
> ONBOOT=yes
> HWADDR=E8:9A:8F:8D:7B:56
> PEERDNS=no
> PEERROUTES=yes
> IPV6_PEERDNS=yes
> IPV6_PEERROUTES=yes
>
> Next I am going to delete this ifcfg and create a new one via the NM gui.

That did the trick.  Unplugged the ethernet.  Deleted the current NM 
ethernet config.  Created a new one with all defaults and saved it. 
Plugged ethernet back in and it is working.

Mine is not to reason why.  Mine is just to do or die.

Or some sentiment like that.

thanks