[Bug 9141] ip: RTNETLINK answers: Invalid argument

bugzilla at busybox.net bugzilla at busybox.net
Sat Aug 6 17:37:15 UTC 2016


https://bugs.busybox.net/show_bug.cgi?id=9141

--- Comment #2 from Neil MacLeod <busybox at nmacleod.com> ---
The problem seems to be this part of the change:

https://github.com/mirror/busybox/commit/ce4bc1ed048233e89ee4cb95830bf6f01d523d1e#diff-17b20e94edc19bc0556a07b3f860041eR365

+               if (RT_SCOPE_UNIVERSE != 0)
+                       req.r.rtm_scope = RT_SCOPE_UNIVERSE;

On Linux, RT_SCOPE_UNIVERSE is 0 so req.r.rtm_scope is never assigned a usable
value unless it comes from the command line (ie. "scope 0"). If req.r.rtm_scope
is not assigned a value then a default value of 255 (RT_SCOPE_NOWHERE) is used.

Remove the "if" condition so that req.r.rtm_scope is set unconditionally and
the problems reported in this bug are resolved.

If the "scope 0" argument is added on the command line then there is also no
problem, however third party programs such as OpenVPN don't supply the scope
argument so they fail with Busybox 1.25.0.

Presumably the default scope should be "scope 0" but that's not working after
this change, and "scope #" is now mandatory which is a major break in terms of
compatibility.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the busybox-cvs mailing list