Add support for custom protocols from rt_protos.d
Bug #1771783 reported by
Nicolas Dichtel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
iproute2 (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Xenial |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https:/
A patch has been pushed upstream so that external applications can define their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https:/
affects: | linux (Ubuntu) → iproute2 (Ubuntu) |
tags: | added: xenial |
Changed in iproute2 (Ubuntu): | |
importance: | Undecided → Wishlist |
tags: | added: patch-accepted-upstream |
Changed in iproute2 (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in iproute2 (Ubuntu): | |
status: | New → Fix Released |
summary: |
- iproute2: frr route protocols are not converted to string on xenial + Add support for custom protocols from rt_protos.d |
To post a comment you must log in.
The attachment "proposed- patch-1. debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]