summaryrefslogtreecommitdiffstats
path: root/bgpd (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #9676 from donaldsharp/import_registerDavid Lamparter2021-10-132-37/+40
|\
| * *: Remove the ZEBRA_IMPORT_ROUTE_XXX zapi messagesDonald Sharp2021-09-272-19/+4
| | | | | | | | | | | | | | | | | | These are no longer really needed. The client just needs to call nexthop resolution instead. So let's remove the zapi types. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
| * bgpd: Make bgp ready to remove distinction between 2 nh tracking typesDonald Sharp2021-09-271-12/+28
| | | | | | | | | | | | | | | | | | | | | | | | Allow bgp to figure out if it cares about address resolution instead of having zebra care about it. This will allow the removal of the zapi type for import checking and just use nexthop resolution. Effectively we just look up the route being returned and if it is in either table we just handle it instead of looking for clues from the zapi message type. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
| * *: Add resolve via default flagDonald Sharp2021-09-271-6/+8
| |
* | Merge pull request #9715 from idryzhov/cleanup-number-named-aclDonatas Abraitis2021-10-132-20/+8
|\ \ | | | | | | *: cleanup number-named access-lists in CLI
| * | *: cleanup number-named access-lists in CLIIgor Ryzhov2021-10-082-20/+8
| | | | | | | | | | | | | | | | | | | | | There's no more difference between number-named and word-named access-lists. This commit removes separate arguments for number-named ACLs from CLI. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | | Merge pull request #9780 from idryzhov/bgp-local-pointerDonatas Abraitis2021-10-111-1/+1
|\ \ \ | | | | | | | | bgpd: don't return pointer to a local variable
| * | | bgpd: don't return pointer to a local variableIgor Ryzhov2021-10-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | CID 1507651. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | | | Merge pull request #9774 from idryzhov/bgp-show-crashDonald Sharp2021-10-081-2/+1
|\ \ \ \ | | | | | | | | | | bgpd: fix crash when using "show bgp vrf all"
| * | | | bgpd: fix crash when using "show bgp vrf all"Igor Ryzhov2021-10-081-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Any command that uses `peer_lookup_in_view` crashes when "vrf all" is used, because bgp is NULL in this case. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | | | | Merge pull request #9693 from donaldsharp/bgp_address_removalDonatas Abraitis2021-10-085-16/+58
|\ \ \ \ \ | |_|/ / / |/| | | | bgpd: When removing v6 address being used as a nexthop ensure peer is…
| * | | | bgpd: When removing v6 address being used as a nexthop ensure peer is resetDonald Sharp2021-10-041-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With v6 interface based peering, we send the global as well as the LL address as nexthops to the peer. When either of these were removed on the interface we were not necessarily resetting the connection. Leaving bgp in a state where the peer had reachability for addresses that are no longer in use. Modify the code that when we receive an interface address deletion event. Check to see that we are using the v6 address as nexthops for that peer and if so, tell it to reset. I initially struggled with a hard reset of the peer or a clear but choose to follow other places in the code that we noticed address changes that resulted in hard resets. Ticket: #2799568 Signed-off-by: Donald Sharp <sharpd@nvidia.com>
| * | | | bgpd: bgp_announce_route should know if we should force the update or notDonald Sharp2021-10-044-16/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When calling bgp_announce_route allow it to properly set the flag to force an update to go out or not. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
* | | | | Merge pull request #9727 from ↵Igor Ryzhov2021-10-081-3/+0
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | ton31337/feature/catch_struct_thread_xxx_against_NULL_coccinelle bgpd: Don't set NULL for struct thread at bgp_dump_interval_func()
| * | | | | bgpd: Don't set NULL for struct thread at bgp_dump_interval_func()Donatas Abraitis2021-10-041-3/+0
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | NULL is already handled by thread_fetch(). Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
* | | | | Merge pull request #9773 from idryzhov/bgp-show-prefix-filter-vrfDonatas Abraitis2021-10-081-37/+16
|\ \ \ \ \ | | | | | | | | | | | | bgpd: add missing vrf/view parameter to one command
| * | | | | bgpd: add missing vrf/view parameter to one commandIgor Ryzhov2021-10-071-37/+16
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | "show bgp neighbors PEER received prefix-filter" misses the argument. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | | | | bgpd: Check return code for bgp_route_match_addDonald Sharp2021-10-061-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FRR uses bgp_route_match_add and checked the return code in every place but one. Fix so that the return code is looked at and warned against Signed-off-by: Donald Sharp <sharpd@nvidia.com>
* | | | | bgpd: Check return from generic_set_addDonald Sharp2021-10-061-5/+19
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Coverity found a couple of spots where FRR was ignoring the return code of generic_set_add. Just follow the code pattern for the rest of the usage in the code. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
* | | | Merge pull request #9743 from pguibert6WIND/largecommfrr-8.1-rc1base_8.1Jafar Al-Gharaibeh2021-10-051-1/+1
|\ \ \ \ | | | | | | | | | | bgpd: large community exact match fix
| * | | | bgpd: large community exact match fixPhilippe Guibert2021-10-051-1/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | The pointer to large community was not the appropriate one. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
* | | | Merge pull request #9689 from AnuradhaKaruppiah/bgp-evpn-lttngDonatas Abraitis2021-10-044-0/+113
|\ \ \ \ | |_|/ / |/| | | bgpd: initial batch of evpn lttng tracepoints
| * | | bgpd: initial batch of evpn lttng tracepointsAnuradha Karuppiah2021-10-014-0/+113
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Low overhead bgp-evpn TPs have been added which push data out in a binary format - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> root@switch:~# lttng list --userspace |grep "frr_bgp:evpn" frr_bgp:evpn_mh_nh_rmac_zsend (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint) frr_bgp:evpn_mh_nh_zsend (loglevel: TRACE_INFO (6)) (type: tracepoint) frr_bgp:evpn_mh_nhg_zsend (loglevel: TRACE_INFO (6)) (type: tracepoint) frr_bgp:evpn_mh_vtep_zsend (loglevel: TRACE_INFO (6)) (type: tracepoint) frr_bgp:evpn_bum_vtep_zsend (loglevel: TRACE_INFO (6)) (type: tracepoint) frr_bgp:evpn_mac_ip_zsend (loglevel: TRACE_INFO (6)) (type: tracepoint) root@switch:~# >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> In addition to the tracepoints a babeltrace python plugin for pretty printing (binary data is converted into grepable strings). Sample usage - frr_babeltrace.py trace_path Sample tracepoint output - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. frr_bgp: evpn_mac_ip_zsend frr_bgp:evpn_mac_ip_zsend {'action': 'add', 'vni': 1007, 'mac': '00:02:00:00:00:04', 'ip': 'fe80::202:ff:fe00:4', 'vtep': '27.0.0.15', 'esi': '03:44:38:39:ff:ff:01:00:00:02'} 2. frr_bgp: evpn_mh_vtep_zsend frr_bgp:evpn_mh_vtep_zsend {'action': 'add', 'esi': '03:44:38:39:ff:ff:01:00:00:02', 'vtep': '27.0.0.16'} 3. frr_bgp: evpn_mh_nhg_zsend frr_bgp:evpn_mh_nhg_zsend {'action': 'add', 'type': 'v4', 'nhg': 74999998, 'esi': '03:44:38:39:ff:ff:01:00:00:02', 'vrf': 85} 4. frr_bgp: evpn_mh_nh_zsend frr_bgp:evpn_mh_nh_zsend {'nhg': 74999998, 'vtep': '27.0.0.16', 'svi': 93} 5. frr_bgp: evpn_mh_nh_rmac_zsend frr_bgp:evpn_mh_nh_rmac_zsend {'action': 'add', 'vrf': 85, 'nh': '::ffff:1b00:12', 'rmac': '00:02:00:00:00:50'} >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Signed-off-by: Anuradha Karuppiah <anuradhak@nvidia.com>
* | | Merge pull request #9710 from idryzhov/bgp-distribute-list-updateDonatas Abraitis2021-10-021-1/+2
|\ \ \ | | | | | | | | bgpd: fix access-list update callback
| * | | bgpd: fix access-list update callbackIgor Ryzhov2021-10-011-1/+2
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | When a regular access-list is updated, we should update references to regular access-lists, not as-path access-lists. Fixes #9707. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* / / bgpd: fix build error seen when lttng is enabledAnuradha Karuppiah2021-09-301-0/+1
|/ / | | | | | | Signed-off-by: Anuradha Karuppiah <anuradhak@nvidia.com>
* | Merge pull request #9422 from pguibert6WIND/update_autort_l3vniSri Mohana Singamsetty2021-09-281-0/+50
|\ \ | |/ |/| bgpd: update auto route target for l3vni appropriately
| * bgpd: update auto route target for l3vni appropriatelyPhilippe Guibert2021-09-021-0/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The BGP configuration for BGP EVPN RT5 setup consists in mainly 2 bgp instances (eventually one is enough) and L3VNI config. When L3VNI is configured before BGP instances, and BGP route targets are auto derived as per rfc8365, then, the obtained route targets are wrong. For instance, the following can be obtained: => show bgp vrf cust1 vni BGP VRF: cust1 Local-Ip: 10.209.36.1 L3-VNI: 1000 Rmac: da:85:42:ba:2a:e9 VNI Filter: none L2-VNI List: Export-RTs: RT:12757:1000 Import-RTs: RT:12757:1000 RD: 65000:1000 whereas the derived route targets should be the below ones: => show bgp vrf cust1 vni BGP VRF: cust1 Local-Ip: 10.209.36.1 L3-VNI: 1000 Rmac: 72:f3:af:a0:98:80 VNI Filter: none L2-VNI List: Export-RTs: RT:12757:268436456 Import-RTs: RT:12757:268436456 RD: 65000:1000 There is an update handler that updates appropriately L2VNIs. But this is not the case for L3VNIs. Add the missing code. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
* | bgpd: Don't lookup paf structure get straight to the pointDonald Sharp2021-09-272-6/+22
| | | | | | | | | | | | | | | | | | | | | | | | The paf data structure is stored based upon an internal bgp enum. The code is looking over all AFI/SAFI's and doing a paf_af_find which then calls afindex to find the right paf structure. Let's just loop over the peer->peer_af_array[] and cut straight to the chase. Under some loads the paf_af_find was taking up 6% of the run time. This removes it entirely. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
* | Merge pull request #9638 from proelbtn/fix-multipath-srv6-sidQuentin Young2021-09-241-6/+3
|\ \
| * | bgpd: fix annouce for multipath SRv6 SID routesRyoga Saito2021-09-211-6/+3
| | | | | | | | | | | | | | | | | | | | | In current implementation, only last path in mpinfo is treated as seg6 nexthop, but all paths should be treated as seg6 nexthop. Signed-off-by: Ryoga Saito <ryoga.saito@linecorp.com>
* | | Merge pull request #9661 from ton31337/fix/bgp_frrtrace_for_lttngQuentin Young2021-09-243-22/+65
|\ \ \
| * | | bgpd: Make sure bgp_dest lock/unlock tracepoints works for LTTng as wellDonatas Abraitis2021-09-233-22/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tested with both UDST and LTTng, both are OK. ``` [13:57:31.346131253] (+?.?????????) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "10.0.2.0/24", count = 3 } [13:57:31.346154756] (+0.000023503) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.0.0/24", count = 3 } [13:57:31.346156699] (+0.000001943) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.10.0/24", count = 2 } [13:57:31.346157570] (+0.000000871) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.100.1/32", count = 2 } [13:57:31.346158521] (+0.000000951) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.100.2/32", count = 2 } [13:57:31.356149109] (+0.009990588) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "10.0.2.0/24", count = 3 } [13:57:31.356155889] (+0.000006780) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.0.0/24", count = 3 } [13:57:31.356156840] (+0.000000951) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.10.0/24", count = 2 } [13:57:31.356157751] (+0.000000911) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.100.1/32", count = 2 } [13:57:31.356158683] (+0.000000932) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 1 }, { prefix = "192.168.100.2/32", count = 2 } [13:57:34.508252238] (+3.152093555) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "172.16.16.1/32", count = 2 } [13:57:34.508289549] (+0.000037311) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "172.16.16.2/32", count = 2 } [13:57:34.508307544] (+0.000017995) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "172.16.16.3/32", count = 2 } [13:57:34.508433878] (+0.000126334) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "10.0.2.0/24", count = 2 } [13:57:34.508435891] (+0.000002013) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "10.0.2.0/24", count = 2 } [13:57:34.508458182] (+0.000022291) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "192.168.0.0/24", count = 2 } [13:57:34.508458852] (+0.000000670) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "192.168.0.0/24", count = 2 } [13:57:34.508472821] (+0.000013969) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "192.168.10.0/24", count = 1 } [13:57:34.508473482] (+0.000000661) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "192.168.10.0/24", count = 1 } [13:57:34.508487041] (+0.000013559) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "192.168.100.1/32", count = 1 } [13:57:34.508487792] (+0.000000751) home-spine1.donatas.net frr_bgp:bgp_dest_lock: { cpu_id = 2 }, { prefix = "192.168.100.1/32", count = 1 } ``` Converting bgp_dest_lock_node/bgp_dest_unlock_node to non-inlined function because LTTng can't work properly with inlined and the compiler does not like it. Not sure how it would be with the performance, but let's see. Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
* | | | Merge pull request #9660 from pguibert6WIND/bgp_error_swapDonatas Abraitis2021-09-231-1/+1
|\ \ \ \ | |/ / / |/| | | bgpd: swap bgp error value with file descriptor value
| * | | bgpd: swap bgp error value with file descriptor valuePhilippe Guibert2021-09-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | the values were swapped by mistake. fix it. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
* | | | Merge pull request #9653 from pguibert6WIND/carriage_returnSri Mohana Singamsetty2021-09-231-1/+2
|\ \ \ \ | | | | | | | | | | bgpd: add carriage return when dumping tags from all evpn rds
| * | | | bgpd: add carriage return when dumping tags from all evpn rdsPhilippe Guibert2021-09-221-1/+2
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | following command: show bgp l2vpn evpn rd all tags does not append rd contexts one after the other before: dut-vm# show bgp l2vpn evpn rd all tags Network Next Hop In tag/Out tag Route Distinguisher: 65000:999 *> [5]:[0]:[24]:[10.40.1.0] 10.209.36.1 Route Distinguisher: 65000:1000 *> [5]:[0]:[24]:[10.40.1.0] 10.209.36.1 Displayed 2 out of 2 total prefixes after: dut-vm# show bgp l2vpn evpn rd all tags Network Next Hop In tag/Out tag Route Distinguisher: 65000:999 *> [5]:[0]:[24]:[10.40.1.0] 10.209.36.1 Route Distinguisher: 65000:1000 *> [5]:[0]:[24]:[10.40.1.0] 10.209.36.1 Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
* | | | Merge pull request #9651 from proelbtn/refactor-9638Donald Sharp2021-09-221-3/+1
|\ \ \ \ | |/ / / |/| | | bgpd: fix mpls nexthop announce in bgp_zebra_announce
| * | | bgpd: fix mpls nexthop announce to zebraRyoga Saito2021-09-221-3/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | currently, has_valid_label is only used to check need to print debug, but if route has normal nexthops and mpls nexthops, label information will be printed even for normal nexthops. Signed-off-by: Ryoga Saito <ryoga.saito@linecorp.com>
* | | Merge pull request #9645 from mjstapp/fix_show_bgp_luDonatas Abraitis2021-09-221-3/+4
|\ \ \ | |/ / |/| | bgpd: make show bgp labeled-unicast work
| * | bgpd: make show bgp labeled-unicast workMark Stapp2021-09-211-3/+4
| | | | | | | | | | | | | | | | | | | | | Yet-another path where the safi needs to be changed to locate the unicast table where LU routes live. Signed-off-by: Mark Stapp <mstapp@nvidia.com>
* | | Merge pull request #9546 from proelbtn/add-support-for-perfix-sid-type-5Russ White2021-09-219-68/+398
|\ \ \ | |/ / |/| | Add support for Prefix-SID (Type 5)
| * | bgpd: show SID structure informationRyoga Saito2021-09-141-2/+10
| | | | | | | | | | | | | | | | | | | | | Current implementation shows Prefix SID value, so SID structure information also be shown. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
| * | bgpd: add sid struct info to bgp_path_info_extraRyoga Saito2021-09-144-18/+90
| | | | | | | | | | | | | | | | | | | | | add SID structure information to bgp_path_info_extra to use structure data in other places. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
| * | bgpd: insert SID structure Sub-Sub-TLVRyoga Saito2021-09-032-8/+21
| | | | | | | | | | | | | | | | | | | | | This patch enables frr to advertise SRv6 SID information with SID structure Sub-Sub-TLV. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
| * | bgpd: add transpose operationRyoga Saito2021-09-031-0/+25
| | | | | | | | | | | | | | | | | | | | | if advertisement with SID structure Sub-Sub-TLV, we need to transpose SID, so added transpose operation into bgp_update. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
| * | bgpd: introduce SID structure informationRyoga Saito2021-09-033-5/+65
| | | | | | | | | | | | | | | | | | | | | | | | draft-ietf-bess-srv6-services-07 defines new SID structure Sub-Sub-TLV. This patch adds SID structure information to bgp_attr_srv6_l3vpn. This patch also defines default SID stucture used by following patches. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
| * | bgpd: introduce new alloc algorithm for SRv6 SIDRyoga Saito2021-09-033-12/+29
| | | | | | | | | | | | | | | | | | | | | | | | Current implementation of SRv6 SID allocation algorithm sets most least 2 bytes. But, according to RFC8986, function bits is located in the next to locator. New allocation alogirithm respects this format. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
| * | bgpd: fix parser of srv6 infomationRyoga Saito2021-08-182-34/+157
| | | | | | | | | | | | | | | | | | | | | | | | | | | bgpd couldn't parse SRv6 SID Information Sub-TLV correctly. draft-ietf-bess-srv6-services-07 also defines SRv6 SID Structure Sub-Sub-TLV. This patch adds the parser for SRv6 SID Structure Sub-Sub-TLV. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
| * | bgpd: fix prefix sid sub-tlv header is missingRyoga Saito2021-08-182-3/+15
| | | | | | | | | | | | | | | | | | | | | | | | draft-ietf-bess-srv6-services-07 defines SRv6 Service Sub-TLV header, but, current bgpd implementation send path attribute without SRv6 Service Sub-TLV header. Signed-off-by: Ryoga Saito <contact@proelbtn.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-30 17:35:04 +0100