From: Petr Machata <petrm@nvidia.com>
To: Ido Schimmel <idosch@nvidia.com>
Cc: <netdev@vger.kernel.org>, <stephen@networkplumber.org>,
<dsahern@gmail.com>, <petrm@nvidia.com>, <razor@blackwall.org>
Subject: Re: [PATCH iproute2-next v2] bridge: Add backup nexthop ID support
Date: Thu, 3 Aug 2023 11:49:57 +0200 [thread overview]
Message-ID: <87tttgcv0v.fsf@nvidia.com> (raw)
In-Reply-To: <20230802164115.866222-1-idosch@nvidia.com>
Ido Schimmel <idosch@nvidia.com> writes:
> Extend the bridge and ip utilities to set and show the backup nexthop ID
> bridge port attribute. A value of 0 (default) disables the feature, in
> which case the attribute is not printed since it is not emitted by the
> kernel.
>
> Example:
>
> # bridge -d link show dev swp1 | grep -o "backup_nhid [0-9]*"
> # bridge -d -j -p link show dev swp1 | jq '.[]["backup_nhid"]'
> null
>
> # bridge link set dev swp1 backup_nhid 10
> # bridge -d link show dev swp1 | grep -o "backup_nhid [0-9]*"
> backup_nhid 10
> # bridge -d -j -p link show dev swp1 | jq '.[]["backup_nhid"]'
> 10
>
> # bridge link set dev swp1 backup_nhid 0
> # bridge -d link show dev swp1 | grep -o "backup_nhid [0-9]*"
> # bridge -d -j -p link show dev swp1 | jq '.[]["backup_nhid"]'
> null
>
> # ip -d link show dev swp1 | grep -o "backup_nhid [0-9]*"
> # ip -d -j -p lin show dev swp1 | jq '.[]["linkinfo"]["info_slave_data"]["backup_nhid"]'
> null
>
> # ip link set dev swp1 type bridge_slave backup_nhid 10
> # ip -d link show dev swp1 | grep -o "backup_nhid [0-9]*"
> backup_nhid 10
> # ip -d -j -p lin show dev swp1 | jq '.[]["linkinfo"]["info_slave_data"]["backup_nhid"]'
> 10
>
> # ip link set dev swp1 type bridge_slave backup_nhid 0
> # ip -d link show dev swp1 | grep -o "backup_nhid [0-9]*"
> # ip -d -j -p lin show dev swp1 | jq '.[]["linkinfo"]["info_slave_data"]["backup_nhid"]'
> null
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Reviewed-by: Petr Machata <petrm@nvidia.com>
next prev parent reply other threads:[~2023-08-03 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 16:41 [PATCH iproute2-next v2] bridge: Add backup nexthop ID support Ido Schimmel
2023-08-03 9:49 ` Petr Machata [this message]
2023-08-04 15:20 ` patchwork-bot+netdevbpf
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=87tttgcv0v.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.