quot; <netdev@vger.kernel.org>, "pve-devel" <pve-de...@pve.proxmox.com>
Envoyé: Jeudi 30 Juillet 2015 07:31:44
Objet: Re: [pve-devel] bridge vlan range, kernel 4.1 : "message truncated"
warning when too much vlans defined
Thanks Ronen,
I have tested
- char buf[1
From: roopa
Date: Thu, 10 Sep 2015 15:26:30 -0700
> On 9/9/15, 11:40 PM, Alexandre DERUMIER wrote:
>> Hi,
>>
>> This still not fixed in iproute 4.2.
>>
>> Is they any plan to increase the rtnl_dump_filter buffer size soon ?
>
> Instead of increasing the default size,
On 9/9/15, 11:40 PM, Alexandre DERUMIER wrote:
Hi,
This still not fixed in iproute 4.2.
Is they any plan to increase the rtnl_dump_filter buffer size soon ?
Instead of increasing the default size, it would be nicer if this was
configurable for iproute2 (I haven't looked yet).
--
To
On 9/10/15, 3:58 PM, David Miller wrote:
From: roopa
Date: Thu, 10 Sep 2015 15:26:30 -0700
On 9/9/15, 11:40 PM, Alexandre DERUMIER wrote:
Hi,
This still not fixed in iproute 4.2.
Is they any plan to increase the rtnl_dump_filter buffer size soon ?
Instead of
Hi,
I'm currently testing vlan range on bridge filtering with kernel 4.1.
If I defined too much vlans, or too big vlan range,
I have a warning message truncated, even if I'm using -c
# bridge -c vlan
Message truncated
port vlan ids
eth2 1 PVID Egress Untagged
bond0 1 PVID Egress
29, 2015 11:25 AM
To: netdev
Cc: pve-devel
Subject: bridge vlan range, kernel 4.1 : message truncated warning when too
much vlans defined
Hi,
I'm currently testing vlan range on bridge filtering with kernel 4.1.
If I defined too much vlans, or too big vlan range,
I have a warning message
: Wednesday, July 29, 2015 11:25 AM
To: netdev
Cc: pve-devel
Subject: bridge vlan range, kernel 4.1 : message truncated warning when too
much vlans defined
Hi,
I'm currently testing vlan range on bridge filtering with kernel 4.1.
If I defined too much vlans, or too big vlan range,
I