On Thu, 14 Nov 2019 07:09:23 -0500 =?utf-8?b?Q2zDqW1lbnQgJ3d4Y2Fmw6knIEhlcnRsaW5n?= <wxc...@wxcafe.net> wrote: > Package: iproute2 > Version: 5.3.0-1 > Severity: normal > Tags: upstream > > `ip route get 1.0.0.0/1` used to return the route for `1.0.0.0/32`, > which was flawed behavior but at least somewhat worked in that it > returned something. > > `ip route get 0.0.0.0/0`, which should have worked, used to return > `need at least a destination address`, which was incorrect. > > Now, `ip route get `1.0.0.0/1` returns > `Error: ipv4: Invalid values in header for route get request.`, and > `ip route get 0.0.0.0/0` returns > `Error: ipv4: rtm_src_len and rtm_dst_len must be 32 for IPv4`. It > seems iproute2 doesn't 'support' querying subnets anymore, which is > broken behavior. > > Thanks
Hi, This never really worked - the kernel does not support getting routes for ranges. Since strict parsing was enabled, those commands are now refused. Simply avoid passing a prefix length. I'll see if upstream accepts a patch to force rtm_dst_len to what the kernel expects, since there's little point in passing something we know it's going to be rejected. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
