On 03/03/17 06:43, David Miller wrote:
From: Cong Wang
Date: Thu, 2 Mar 2017 12:24:36 -0800
This restores the ability of setting bond device's mtu to 9000.
Fixes: 91572088e3fd ("net: use core MTU range checking in core net infra")
Reported-by: daz...@gmail.com
Reported-by: Br
G'day Jarod,
I have a pair of machines that are linked by a pair of quad port e1000
cards with all 4 ports bonded. The network is configured with an mtu of
9000.
Kernel 4.10 fails to bring these interfaces up as it fails when trying
to set the mtu on the bond interface higher than 1500. A bi
On 08/12/16 01:43, Thomas Haller wrote:
On Tue, 2016-12-06 at 17:12 -0600, Dan Williams wrote:
libnl1 rejects the IFLA_INFO_DATA attribute because it expects it
to
contain a sub-attribute. Since the payload size is zero it doesn't
match the policy and parsing fails.
There's no problem with li
On 06/12/16 01:53, Guillaume Nault wrote:
Probably not a mistake on your side. I've started looking at netcf'
source code, but haven't found anything that could explain your issue.
It'd really help if you could provide steps to reproduce the bug.
Further to my message this morning, I started
On 06/12/16 01:53, Guillaume Nault wrote:
Can you send a minimal configuration file that triggers the bug?
I've set up a virtual machine (Linux 4.7.0, netcf 0.2.8 backported from
Debian Sid), but couldn't reproduce the issue so far.
Ok I reproduced this in a VM. I used the stock Debian 7 inst
G'day All,
I've been chasing an issue on and off for a couple of months now, and
I've managed to finally find a way to reproduce and bisect it.
Machine is an old Debian (7.11) box with a recent compile of netcf. Any
kernel later than 4.6.7 prevents ncftool from running if the ppp
interface i
