From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 976] rte_rib (and rte_rib6) do not handle /0 correctly
Date: Wed, 23 Mar 2022 22:46:02 +0000 [thread overview]
Message-ID: <bug-976-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=976
Bug ID: 976
Summary: rte_rib (and rte_rib6) do not handle /0 correctly
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The function rte_rib_insert() allows inserting 0/0 as a default route, but it
is not correctly handled by the current tree code. For example lookups will
never match the default route and tree traversal never finds this default
route.
Same bug probably exists in rte_rib6
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-03-23 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 22:46 bugzilla [this message]
2022-03-23 23:38 ` Stephen Hemminger
2022-03-24 18:21 ` Medvedkin, Vladimir
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=bug-976-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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).