From: David Ahern <dsahern@gmail.com>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, nikolay@cumulusnetworks.com,
stephen@networkplumber.org
Subject: Re: [PATCH iproute2 net-next v2 1/2] bridge: fdb get support
Date: Mon, 30 Sep 2019 10:41:44 -0600 [thread overview]
Message-ID: <0ae9fd91-ab7c-c614-06e8-e8264bcfe96d@gmail.com> (raw)
In-Reply-To: <1569702130-46433-2-git-send-email-roopa@cumulusnetworks.com>
On 9/28/19 2:22 PM, Roopa Prabhu wrote:
> @@ -518,6 +520,113 @@ static int fdb_modify(int cmd, int flags, int argc, char **argv)
> return 0;
> }
>
> +static int fdb_get(int argc, char **argv)
> +{
> + struct {
> + struct nlmsghdr n;
> + struct ndmsg ndm;
> + char buf[1024];
> + } req = {
> + .n.nlmsg_len = NLMSG_LENGTH(sizeof(struct ndmsg)),
> + .n.nlmsg_flags = NLM_F_REQUEST,
> + .n.nlmsg_type = RTM_GETNEIGH,
> + .ndm.ndm_family = AF_BRIDGE,
> + };
> + struct nlmsghdr *answer;
> + char *addr = NULL;
> + char *d = NULL, *br = NULL;
> + char abuf[ETH_ALEN];
> + unsigned long vni = ~0;
> + int br_ifindex = 0;
> + char *endptr;
> + short vlan = -1;
iproute2 follows the net standards of reverse xmas tree for declarations.
next prev parent reply other threads:[~2019-09-30 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 20:22 [PATCH iproute2 net-next v2 0/2] support for bridge fdb and neigh get Roopa Prabhu
2019-09-28 20:22 ` [PATCH iproute2 net-next v2 1/2] bridge: fdb get support Roopa Prabhu
2019-09-30 16:41 ` David Ahern [this message]
2019-09-28 20:22 ` [PATCH iproute2 net-next v2 2/2] ipneigh: neigh " Roopa Prabhu
2019-09-30 16:42 ` David Ahern
2019-10-01 4:44 ` Roopa Prabhu
2019-09-30 14:57 ` [PATCH iproute2 net-next v2 0/2] support for bridge fdb and neigh get Ivan Vecera
2019-09-30 16:25 ` Roopa Prabhu
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=0ae9fd91-ab7c-c614-06e8-e8264bcfe96d@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.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).