1
0
mirror of https://github.com/osrg/gobgp.git synced 2024-05-11 05:55:10 +00:00

10 Commits

Author SHA1 Message Date
Britton Payne
34e4845765 Adjust size of packing slice before allocating
- Changes table.(*packerV4).pack.func1 (split) to adjust the max
  parameter before using it to allocate slice size.  Previously the full
  max size was allocated then max was (possibly) truncated before
  further use.
2024-03-02 07:48:16 +00:00
Jeremiah Millay
79d301f75b Fix UpdatePathAggregator4ByteAs() ignores 32bit value
Signed-off-by: Jeremiah Millay <jmillay@fastly.com>
2023-06-12 17:19:09 -04:00
FUJITA Tomonori
97aefbb24a decouple logging
gobgp is tightly coupled with logrus and uses the global logrus logger
instance. The uses of gobgp library can't use other logging libraries.

Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
2021-12-08 10:39:16 +00:00
FUJITA Tomonori
c593d7c8b3 switch to Go API v2 for protobuf
seems that sticking to Go API v1 for protobuf is headache for projects
using GoBGP.

This breaks the compatibility so bumps up the major version to 3.

Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
2021-12-08 07:22:50 +00:00
Imcom Jin
d277950d0f refactor: nlri/nexthop requires MP will get MP explicitly already.
so we can safely remove the MP_REACH_NLRI from ipv4_uc with ipv4 nexthop
2021-06-07 09:25:54 +09:00
Imcom Jin
2d73cf8eba bugfix: should check if next-hop attr exists or not before append 2021-03-03 09:28:08 +09:00
Imcom Jin
82d2877c70 fixing an issue when gobgp sits between a MP-capable peer and a non-MP-capable peer
whereby MP-capable peer uses MP_REACH_NLRI to send updates to gobgp
gobgp accepts it but without setting NEXT_HOP pathattr
then gobgp propagates the paths to the non-MP-capable peer with update.NLRI set but without NEXT_HOP
the non-MP-capable peer will treat the update as withdraw message cause routes cannot propagate properly
2021-03-03 09:28:08 +09:00
FUJITA Tomonori
ce62ea68d8 table: handle staticcheck's warnings
Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
2019-10-26 22:19:30 +09:00
FUJITA Tomonori
1d14b8ecfb silence staticcheck warnings
Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
2019-01-09 14:36:48 +09:00
FUJITA Tomonori
c4775c4251 follow Standard Go Project Layout
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>
2018-07-07 20:44:25 +09:00