summaryrefslogtreecommitdiffhomepage
path: root/internal/pkg/zebra
AgeCommit message (Collapse)Author
2020-04-26Refactoring Zebra and supporting frr7.3Hitoshi Irino
- Change const values to camel case from snake case to make zero golint's warnigns - Introduce convert functions (toEach, toCommon) between the newest version to older versions - Merge code about decode nexthop to reduce lines of code - Add frr7.3 statemet in allowable software for config - Rename and Update generated file by stringer
2020-01-18bug fix in zebra integration for frr7.2Hitoshi Irino
2020-01-13Supporting FRR7.2Hitoshi Irino
2019-08-21Support connecting zebra of cumulus linuxHitoshi Irino
2019-07-21Avoid panic by receiving vpnv6 prefixes with zebra reported in issue #2113Hitoshi Irino
- Additionally bug fix which avoid panic caused by displaying vpnv6 prefixes using gobgp vrf rib - Supporting FRRouting 7.1.x
2019-05-08zebra: fix unit test failure on non linuxFUJITA Tomonori
syscall.AF_INET/AF_INET6 are os/architecture specific. On some non Linux x86 architectures, failures like the following happen: --- FAIL: Test_NexthopRegisterBody (0.00s) Error Trace: zapi_test.go:893 Error: Not equal: 0x1e (expected) != 0xa (actual) Error Trace: zapi_test.go:894 Error: Not equal: net.IP{0x20, 0x1, 0xd, 0xb8, 0x0, 0x1, 0x0, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1} (expected) != net.IP(nil) (actual) Diff: --- Expected +++ Actual @@ -1,2 +1,2 @@ -(net.IP) (len=16 cap=16) 2001:db8:1:1::1 +(net.IP) <nil> looks like that frr uses os/os/architecture specific values in the zapi message. Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
2019-05-08zebra: supporting FRRouting version 7Hitoshi Irino
- the "version" parameter (which means ZAPI) 6 in zebra config changes supporting FRRouting version 7 instead of FRRouting version 6. - the "software-name" parameter which supports backward compatibility is added in zebra config. (GoBGP support FRRouting version 6 when "version = 6" and "software-name = frr6" is configured.)
2019-05-01zebra: using LABEL_MANAGER_CONNECT_ASYNC instead of LABEL_MANAGER_CONNECTHitoshi Irino
2019-03-14Fix bug using variable of zclient in AddVrf of server.go.Hitoshi Irino
2019-03-14Supporting BGP/MPLS L3VPNs with Frrouting Zebra API 6Hitoshi Irino
- 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 2bdb76f2dcf24b891f2b6327a57c31b26463b2dd "Supporting Zebra API version 6 which is used in FRRouting version 6")
2019-02-03Fix spells for keywords (vrfid, labelnum) in sprintf lineHitoshi Irino
2019-02-02Fix bug: processing MPLS label in nexthop update messageHitoshi Irino
2019-01-09silence staticcheck warningsFUJITA Tomonori
Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
2018-12-30zebra: Introducing MIN_ZAPIVER and MAX_ZAPIVER. And avoiding double close ↵Hitoshi Irino
channel when sequential retry to connect zebra. - Introducing MIN_ZAPIVER and MAX_ZAPIVER for avoiding editing files except for zapi.go when new ZAPI version will be supported in future. - Fix a bug avoiding panic by double close for a channel. - Changing algorithm for sequential retry to connect zebra.
2018-12-16fix typo in zapi.go: LABLE -> LABELHitoshi Irino
2018-10-21Supporting Zebra API version 6 which is used in FRRouting version 6Hitoshi Irino
2018-08-18ZAPI5 (FRRouting version 5) supportHitoshi Irino
2018-07-07follow Standard Go Project LayoutFUJITA Tomonori
https://github.com/golang-standards/project-layout Now you can see clearly what are private and public library code. Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-15 05:25:37 +0000