Re: [PATCH iproute2-master] bridge: fdb: Fix FDB dump with strict checking disabled

On Fri, 25 Jan 2019 17:09:17 + Ido Schimmel wrote: > While iproute2 correctly uses ifinfomsg struct as the ancillary header > when requesting an FDB dump on old kernels, it sets the message type to > RTM_GETLINK. This results in wrong reply being returned. > > Fix this by using RTM_GETNEIGH

Re: [PATCH iproute2-master] bridge: fdb: Fix FDB dump with strict checking disabled

- Ido Schimmel wrote: > While iproute2 correctly uses ifinfomsg struct as the ancillary header > when requesting an FDB dump on old kernels, it sets the message type to > RTM_GETLINK. This results in wrong reply being returned. > > Fix this by using RTM_GETNEIGH instead. > > Before: > $ br

Re: [PATCH iproute2-master] bridge: fdb: Fix FDB dump with strict checking disabled

On 1/25/19 10:09 AM, Ido Schimmel wrote: > While iproute2 correctly uses ifinfomsg struct as the ancillary header > when requesting an FDB dump on old kernels, it sets the message type to > RTM_GETLINK. This results in wrong reply being returned. > > Fix this by using RTM_GETNEIGH instead. > > Be

[PATCH iproute2-master] bridge: fdb: Fix FDB dump with strict checking disabled

While iproute2 correctly uses ifinfomsg struct as the ancillary header when requesting an FDB dump on old kernels, it sets the message type to RTM_GETLINK. This results in wrong reply being returned. Fix this by using RTM_GETNEIGH instead. Before: $ bridge fdb show brport dummy0 Not RTM_NEWNEIGH: