Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zapi version 5 #1766

Closed
wants to merge 125 commits into from
Closed

Zapi version 5 #1766

wants to merge 125 commits into from

Conversation

amanshaikh75
Copy link

This branch implements Zebra API version 5. Using this branch I have been able to add required routes to kernel for end-to-end forwarding in an BGP/MPLS L3-VPN scenario.

Aman Shaikh and others added 30 commits January 9, 2018 11:56
Reverted "Updated to deal with API change in github.com/satori/go.uuid"

See merge request !1
Merge changes made locally with github version
Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
On FRRouting, MPLS label allocation is maintained on Zebra daemon, so we
need to request the label range allocation to Zebra daemon in order to
allocate a label to VRFs with MPLS VPN.

Note: "version >= 4" is required to use this feature.

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
```

Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
On FRRouting, MPLS label allocation is maintained on Zebra daemon, so we
need to request the label range allocation to Zebra daemon in order to
allocate a label to VRFs with MPLS VPN.

Note: "version >= 4" is required to use this feature.

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
```

Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
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>
@fujita
Copy link
Member

fujita commented Jun 27, 2018

As I said before, I'm not interested in adding another one the supported list unless dropping one in the list.

@fujita fujita closed this Jun 27, 2018
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")
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants