zclinet: Enable to request MPLS label range to FRRouting #1587
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi I'd really like to see this PR become part of the master branch. When's this likely to happen? thanks |
With FRRouting, MPLS label allocation is maintained on Zebra daemon, so GoBGP need to request the label range allocation to Zebra daemon in order to allocate a label to VRFs with MPLS VPN. Example of Configuration: ```toml [zebra.config] enabled = true url = "unix:/var/run/frr/zserv.api" redistribute-route-type-list = ["connect"] version = 4 mpls-label-range-size = 100 ``` Note: "version >= 4" is required to use this feature. Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
iwaseyusuke
force-pushed
the
zclient-Enable_to_request_MPLS_label_range
branch
from
5a39915
to
418dcb0
Compare
|
Updated to resolve conflicts. |
irino
added a commit
to irino/gobgp
that referenced
this pull request
Mar 2, 2019
- This commit aims to solve reported problem on issues osrg#1611, osrg#1648 and osrg#1912 - Partial changes of this commit duplicate with changes on PR osrg#1587 (not merged) and PR osrg#1766 (not merged and already closed) - This commit is tested with only FRRouting version 6.0.2 (which uses Zebra API 6) - This commit fixes lack of LABEL_MANAGER_CONNECT_ASYNC for ZAPI6. (This bug is introduced on commit 2bdb76f "Supporting Zebra API version 6 which is used in FRRouting version 6")
fujita
pushed a commit
that referenced
this pull request
Mar 14, 2019
- This commit aims to solve reported problem on issues #1611, #1648 and #1912 - Partial changes of this commit duplicate with changes on PR #1587 (not merged) and PR #1766 (not merged and already closed) - This commit is tested with only FRRouting version 6.0.2 (which uses Zebra API 6) - This commit fixes lack of LABEL_MANAGER_CONNECT_ASYNC for ZAPI6. (This bug is introduced on commit 2bdb76f "Supporting Zebra API version 6 which is used in FRRouting version 6")
|
@irino great, let's close. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With FRRouting, MPLS label allocation is maintained on Zebra daemon, so GoBGP need to request the label range allocation to Zebra daemon in order to allocate a label to VRFs with MPLS VPN.
Example of Configuration:
Note: "version >= 4" is required to use this feature.