From: Stephen Hemminger <stephen@networkplumber.org>
To: "Magesh M P" <magesh@digitizethings.com>
Cc: David Ahern <dsahern@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: gateway field missing in netlink message
Date: Wed, 4 May 2022 20:49:08 -0700 [thread overview]
Message-ID: <20220504204908.025d798c@hermes.local> (raw)
In-Reply-To: <DM5PR20MB2055CCC42062AF5DB5827BAEAEC29@DM5PR20MB2055.namprd20.prod.outlook.com>
On Thu, 5 May 2022 03:43:45 +0000
"Magesh M P" <magesh@digitizethings.com> wrote:
> Hi Dave,
>
> Thanks for responding.
>
> The librtnl/netns.c contains the parser code as below which parses the MULTIPATH attribute. Could you please take a look at the code and see if anything is wrong ?
That won't support IPv6.
next prev parent reply other threads:[~2022-05-05 3:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 6:46 gateway field missing in netlink message Magesh M P
2022-05-04 22:31 ` David Ahern
2022-05-05 3:43 ` Magesh M P
2022-05-05 3:49 ` Stephen Hemminger [this message]
[not found] ` <DM5PR20MB20556090A88575E4F55F1EDAAEC29@DM5PR20MB2055.namprd20.prod.outlook.com>
[not found] ` <DM5PR20MB2055F01D55F6F7307B50182EAEC29@DM5PR20MB2055.namprd20.prod.outlook.com>
[not found] ` <20220505092851.79d3375a@hermes.local>
[not found] ` <DM5PR20MB2055542FB35F8CA770178F9AAEC69@DM5PR20MB2055.namprd20.prod.outlook.com>
2022-05-09 6:59 ` Magesh M P
2022-05-09 15:32 ` David Ahern
[not found] ` <20220509080511.1893a939@hermes.local>
[not found] ` <DM5PR20MB2055EBCA16DFB527A7E9A32FAEC89@DM5PR20MB2055.namprd20.prod.outlook.com>
2022-05-11 5:35 ` Magesh M P
2022-05-11 15:56 ` Stephen Hemminger
2022-05-11 16:25 ` David Ahern
2022-05-05 3:50 ` Stephen Hemminger
2022-05-05 4:14 ` Magesh M P
2022-05-05 4:13 ` David Ahern
2022-05-12 6:33 Magesh M P
2022-05-19 6:11 Magesh M P
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220504204908.025d798c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@kernel.org \
--cc=magesh@digitizethings.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).