Installing libnl 3.2.27-1 on LM/Ubuntu-Xenial disables net interfaces

[Jef Oliver]

On Sat, Sep 24, 2016 at 4:16 AM, Thomas Haller <thaller at redhat.com> wrote:
> On Fri, 2016-09-23 at 18:06 -0700, Jef Oliver wrote:
>> There was an ABI break, I believe around 3.2.22->3.2.23. If you go
>> from
>> 3.2.21 to the newest, this could be the problem. Don't hold me to
>> this
>> though.
>
> Hi Jef,
>
> which ABI break are you referring too?
>
> "ABI break" sounds intentional. AFAIK, there wasn't an intentional ABI
> change.
> Certainly it's possible that one or another version has (serioius)
> bugs. Of course, for an affected user the difference between ABI change
> and bug is moot...
>
>
> best,
> Thomas

I was incorrect in my thinking here. My apologies. I was referring the
SONAME bug that happened pre-3.2.20. This is not something that should
be affecting the described situation.

Jef

>
>>
>> On Fri, Sep 23, 2016 at 3:23 PM, Mel Brands <bighype at gmail.com>
>> wrote:
>> >
>> > Hi all,
>> >
>> > Ever since I upgraded to new Linux 4.4..0-x series of kernels, I've
>> > had unexplained network troubles. About 1 in 5 reboots would result
>> > in
>> > network interfaces being down and I was getting "The system network
>> > services are not compatible with this version." from
>> > NetworkManager. I
>> > used to "resolve" that error by rebooting... since none of the
>> > network
>> > troubleshooting methods worked for me.
>> >
>> > After I upgraded to 4.4.0-38-generic kernel, not even a reboot
>> > would
>> > bring network interfaces up. I finally did some searching and it
>> > turns
>> > out that libnl is the culprit.
>> >
>> > You can see other reports here for example:
>> > https://askubuntu.com/questions/727988/the-system-network-services-
>> > are-not-compatible-with-this-version-ubuntu-14-0
>> >
>> > The solution offered above is to downgrade libnl to 3.2.21-1. I can
>> > confirm that this works and my network interfaces work after
>> > reboots.
>> > Judging by the dates of the posts above, it seems that this issue
>> > has
>> > persisted for years.
>> >
>> > Since I don't like running old network packages, I'm hoping that
>> > someone here can tell me what's wrong and how I can fix this. I'm
>> > willing to help with tracking down the issue.
>> >
>> > Thank you!
>> > Mel
>> >
>> > _______________________________________________
>> > libnl mailing list
>> > libnl at lists.infradead.org
>> > http://lists.infradead.org/mailman/listinfo/libnl
>>
>> _______________________________________________
>> libnl mailing list
>> libnl at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/libnl