On Mon, 22 Jun 2015 11:44:50 -0600
jd1008 <jd1008(a)gmail.com> wrote:
On 06/21/2015 10:50 PM, Ed Greshko wrote:
> On 06/22/15 12:31, Bruno Wolff III wrote:
>> I am still investigating this, but I have an f22 laptop that is
>> only getting an IP6 address set up on the loopback interface. I
>> noticed this because I run a local resolver on 127.0.0.1 and
>> connections to it stopped working over night (after a reboot). The
>> was a NetworkManager update before the reboot where things stopped
>> working, so that seems to be the mostly change that triggered the
>> problem. I'll be able to reboot another f22 machine tomorrow and
>> also should have time to try downgrading NetworkManager to confirm
>> whether or not that update is really causing the problem. (And
>> file a bug and give negative karma if appropriate.)
> FWIW, also have a laptop running F22 and fully updated. Currently
> at NetworkManager-1.0.2-1.fc22.x86_64 which I believe is the latest
> and I'm not having any difficulties with my lo interface.
>
Do you also "run a local resolver on 127.0.0.1", as Bruno does?
I'm not sure if that was addressed to me, but yes, I use
dnssec-tiggerd / unbound here. However, they don't start right on boot
due to the missing 127.0.0.1/8. So, I think this is very likely a
NetworkManager bug.
kevin