> Downgrading the kernel resolves the problem, but I don't see any bonding
> commits between linux-lts-5.10.25 and linux-lts 5.10.26.
My mistake - 9392b8219b62b0536df25c9de82b33f8a00881ef *was* included in
5.10.26. Thus the "Invalid argument" message.
https://git.kernel.org/pub/scm/linux/k
Arch linux-lts-5.10.25-1 to linux-lts 5.10.26-1
This is on a wireless bonding setup with fallback to wired ethernet.
Everything with the interfaces looks fine, except, for instance, ping returns
the error message "ping: sendmsg: Invalid argument". Of course, networking
becomes unusable.
Remo
I have a question - maybe someone can point me in the right direction?
When there exist two or more "local" interfaces on the "host" system, where
sysctl "net.ipv4.conf..forwarding=1" has been set, and where each
interface has an IP address on a different subnet, then, when a frame arrives
at a
On 08/13/2017 11:42 AM, Andreas Born wrote:
> On a side note I would recommend some of my own reading to you about
> patch submission in general [1] and on netdev specifically [2].
Mmm - [2] and [3], I suspect. Thanks Andreas. I'll be studying those. Yeah,
I'm still learning what is needed and
Hey Kalle
Still, a problem:
On 08/12/2017 01:35 AM, Kalle Valo wrote:
> Kalle Valo writes:
>
>> Andreas Born writes:
>>
>>> Earlier today I submitted the patch (bonding: require speed/duplex
>>> only for 802.3ad, alb and tlb) [2] that only partially reverts what is
>>> a regression following m
Should there be an
ip link set primary
command in the iproute2 package, to set the Primary Slave on a "bond" type link?
It seems that the alternative now is to use the sysfs, with
echo -n > /sys/devices/virtual/net//bonding/primary
which, in systemd Service Unit Files, requires "/usr/bin/
