<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="DejaVu Sans">Well that's embarrassing. </font>Here is
just the libnl change.<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/16/2012 06:47 PM, Justin Mayfield
wrote:<br>
</div>
<blockquote cite="mid:502D94A0.90609@cradlepoint.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font face="DejaVu Sans">Hi Everyone,<br>
<br>
I ran into a bug today related to how Linux handles a route's
nexthop flags when there is just one nexthop. Namely Linux
expects the flags to be OR'd into the rtm_flags field when there
is only one nexthop and so rtnl_route_build_msg needs to check
the number of nexthops and store the nexthops flags into this
field prior to calling nlmsg_append(...&rtmsg).<br>
<br>
Conversely the rtnl_route_parse function needs to pull these
lower 0xff bits when a single nexthop is detected.<br>
<br>
Attached is my patch. I don't like the slight duplication of
doing the rtnl_route_get_nnexthops check twice but it seemed to
be the least turmoil of any solution I thought of.<br>
<br>
Cheers!<br>
Justin Mayfield<br>
</font> !SIG:502d94f9190323796110542!
</blockquote>
<br>
</body>
</html>