- dev - lists.frrouting.org

10k static config file.
by Christian Hopps 15 Dec '20

15 Dec '20

In the last NB meeting we discussed testing with a 10k staticd config file. Can someone point me to or send me that configuration? Also apparently someone had a docker setup that recreated the issue maybe? Thanks, Chris.

1 0

PR 7660 merged but some CI check failed
by Javier García 09 Dec '20

09 Dec '20

Hi, The 7660 pr is just documentation but shows 1/2 check failed (Topo Test Part 0). The detail points to a commit not involved in the PR 7660 . I think that is something related to the CI jobs itself that in some way mixed jobs or commits. This is the link to the detail CI https://ci1.netdef.org/browse/FRR-FRRPULLREQ-15805/ __________________________ Regards Javier

1 0

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 03 Dec '20

03 Dec '20

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 1 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 1499893: (OVERRUN) ________________________________________________________________________________________________________ *** CID 1499893: (OVERRUN) /isisd/isis_spf.c: 1349 in spf_adj_list_parse_lsp() 1343 if (lsp->tlvs) { 1344 if (pseudo_lsp || spftree->mtid == ISIS_MT_IPV4_UNICAST) { 1345 head = lsp->tlvs->oldstyle_reach.head; 1346 for (struct isis_oldstyle_reach *reach = 1347 (struct isis_oldstyle_reach *)head; 1348 reach; reach = reach->next) { >>> CID 1499893: (OVERRUN) >>> Overrunning array "reach->id" of 7 bytes by passing it to a function which accesses it at byte offset 7. 1349 spf_adj_list_parse_tlv( 1350 spftree, adj_list, reach->id, 1351 pseudo_nodeid, pseudo_metric, 1352 reach->metric, true, NULL); 1353 } 1354 } /isisd/isis_spf.c: 1366 in spf_adj_list_parse_lsp() 1360 spftree->mtid); 1361 if (te_neighs) { 1362 head = te_neighs->head; 1363 for (struct isis_extended_reach *reach = 1364 (struct isis_extended_reach *)head; 1365 reach; reach = reach->next) { >>> CID 1499893: (OVERRUN) >>> Overrunning array "reach->id" of 7 bytes by passing it to a function which accesses it at byte offset 7. 1366 spf_adj_list_parse_tlv( 1367 spftree, adj_list, reach->id, 1368 pseudo_nodeid, pseudo_metric, 1369 reach->metric, false, reach->subtlvs); 1370 } 1371 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 02 Dec '20

02 Dec '20

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 1 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 1499854: Error handling issues (CHECKED_RETURN) /zebra/dplane_fpm_nl.c: 1263 in fpm_process_queue() ________________________________________________________________________________________________________ *** CID 1499854: Error handling issues (CHECKED_RETURN) /zebra/dplane_fpm_nl.c: 1263 in fpm_process_queue() 1257 1258 /* Dequeue next item or quit processing. */ 1259 ctx = dplane_ctx_dequeue(&fnc->ctxqueue); 1260 if (ctx == NULL) 1261 break; 1262 >>> CID 1499854: Error handling issues (CHECKED_RETURN) >>> Calling "fpm_nl_enqueue" without checking return value (as is done elsewhere 4 out of 5 times). 1263 fpm_nl_enqueue(fnc, ctx); 1264 1265 /* Account the processed entries. */ 1266 atomic_fetch_add_explicit(&fnc->counters.dplane_contexts, 1, 1267 memory_order_relaxed); 1268 atomic_fetch_sub_explicit(&fnc->counters.ctxqueue_len, 1, ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

CLI configuration format for the new SR-TE daemon with PCEP
by Sebastien Merle 30 Nov '20

30 Nov '20

Hi, I am writing on behalf of the developers behind the pull request for the new experimental daemon pathd. It adds segment routing traffic engeneering policies and an optional dynamic module for PCEP support to FRR. During the review, the question of the CLI configuration format was discussed, and we wanted to submit the last proposal to be sure the community was agreeing with it. Here is a simple but artificially exhaustive example of pathd configuration with the pcep module enabled: ``` segment-routing traffic-eng segment-list SL1 index 10 mpls label 1111 nai node 1.1.1.1 index 20 mpls label 2222 nai node 2.2.2.2 ! policy color 4 endpoint 10.10.10.4 name r4 binding-sid 104 candidate-path preference 100 name exp41 explicit segment-list SL1 candidate-path preference 200 name dyn41 dynamic bandwidth 1234 affinity exclude-any 0x01 pcep metric bound abc 16 pcep required metric bnc 123 pcep objective-function mcp msn mll mrup ! ! pcep config-group COMMON source-address ip 10.10.10.10 timer keep-alive 50 ! config-group CONF1 config-group COMMON tcp-md5-auth SECRET timer keep-alive 30 ! pce-peer PCE1 config-group COMMON address ip 10.10.10.1 pce-initiated ! pce-peer PCE2 config-group CONF1 address ip 10.10.10.2 msd 32 sr-draft07 ! pcc peer PCE1 precedence 10 peer PCE2 precedence 20 ! ! ! ! ``` Some explanation about why the configuration format was chosen: * In the candidate path, the metric and objective function are prefixed with `pcep` because we didn't think this was generic enough for non-pcep candidate path. * `config-group` is used to create a hierarchy of pcc/pce configuration so the common configuration does not have to be duplicated in every `pce-peer`. * The `pce-peer` are not defined under `pcc` for two reasons: 1. This works around using vtysh without transaction, where we can't be sure when we have all the configuration to start the pcc. 2. The idea is to later support per-prefix selection of the PCE: ``` pcc peer PCE1 precedence 10 group GROUP1 priority 10 prefix 4.5.3.0/24 peer PCE2 precedence 10 peer PCE1 precedence 20 ! group GROUP2 priority 20 prefix 4.5.3.0/24 peer PCE3 precedence 10 peer PCE1 precedence 20 ! ! ``` The list of possible commands that can be specified under `config-group` and `pce-peer` is: * `sr-draft07` (Enable backward compatibility with segment routing draft07 PCEs) * `pce-initiated` (Enable PCE-intitated LSP support) * `tcp-md5-auth WORD` * `address <ip A.B.C.D | ipv6 X:X::X:X> [port (1024-65535)]` * `source-address [ip A.B.C.D | ipv6 X:X::X:X] [port (1024-65535)]` * `config-group WORD` * `timer [keep-alive (1-63)] [min-peer-keep-alive (1-255)] [max-peer-keep-alive (1-255)] ...` * `msd (1-32)` Link to the pull request: https://github.com/FRRouting/frr/pull/7351 Thank you very much for your feedback. Regards, Sebastien Merle.

3 2

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 19 Nov '20

19 Nov '20

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 3 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 1 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 3 of 3 defect(s) ** CID 1499606: Error handling issues (CHECKED_RETURN) /pimd/pim_nb_config.c: 2595 in routing_control_plane_protocols_control_plane_protocol_pim_address_family_rp_static_rp_rp_list_prefix_list_modify() ________________________________________________________________________________________________________ *** CID 1499606: Error handling issues (CHECKED_RETURN) /pimd/pim_nb_config.c: 2595 in routing_control_plane_protocols_control_plane_protocol_pim_address_family_rp_static_rp_rp_list_prefix_list_modify() 2589 break; 2590 case NB_EV_APPLY: 2591 vrf = nb_running_get_entry(args->dnode, NULL, true); 2592 pim = vrf->info; 2593 plist = yang_dnode_get_string(args->dnode, NULL); 2594 yang_dnode_get_ip(&rp_addr, args->dnode, "../rp-address"); >>> CID 1499606: Error handling issues (CHECKED_RETURN) >>> Calling "str2prefix" without checking return value (as is done elsewhere 58 out of 61 times). 2595 str2prefix("224.0.0.0/4", &group); 2596 return pim_rp_cmd_worker(pim, rp_addr.ip._v4_addr, group, 2597 plist, args->errmsg, args->errmsg_len); 2598 } 2599 2600 return NB_OK; ** CID 1499605: Error handling issues (CHECKED_RETURN) /pimd/pim_nb_config.c: 2500 in routing_control_plane_protocols_control_plane_protocol_pim_address_family_rp_static_rp_rp_list_destroy() ________________________________________________________________________________________________________ *** CID 1499605: Error handling issues (CHECKED_RETURN) /pimd/pim_nb_config.c: 2500 in routing_control_plane_protocols_control_plane_protocol_pim_address_family_rp_static_rp_rp_list_destroy() 2494 args->errmsg_len); 2495 } 2496 2497 else if (yang_dnode_get(args->dnode, "./prefix-list")) { 2498 plist = yang_dnode_get_string(args->dnode, 2499 "./prefix-list"); >>> CID 1499605: Error handling issues (CHECKED_RETURN) >>> Calling "str2prefix" without checking return value (as is done elsewhere 58 out of 61 times). 2500 str2prefix("224.0.0.0/4", &group); 2501 result = pim_no_rp_cmd_worker(pim, rp_addr.ip._v4_addr, 2502 group, plist, 2503 args->errmsg, 2504 args->errmsg_len); 2505 } ** CID 1499604: Error handling issues (CHECKED_RETURN) /pimd/pim_nb_config.c: 2622 in routing_control_plane_protocols_control_plane_protocol_pim_address_family_rp_static_rp_rp_list_prefix_list_destroy() ________________________________________________________________________________________________________ *** CID 1499604: Error handling issues (CHECKED_RETURN) /pimd/pim_nb_config.c: 2622 in routing_control_plane_protocols_control_plane_protocol_pim_address_family_rp_static_rp_rp_list_prefix_list_destroy() 2616 break; 2617 case NB_EV_APPLY: 2618 vrf = nb_running_get_entry(args->dnode, NULL, true); 2619 pim = vrf->info; 2620 yang_dnode_get_ip(&rp_addr, args->dnode, "../rp-address"); 2621 plist = yang_dnode_get_string(args->dnode, NULL); >>> CID 1499604: Error handling issues (CHECKED_RETURN) >>> Calling "str2prefix" without checking return value (as is done elsewhere 58 out of 61 times). 2622 str2prefix("224.0.0.0/4", &group); 2623 return pim_no_rp_cmd_worker(pim, rp_addr.ip._v4_addr, group, 2624 plist, args->errmsg, 2625 args->errmsg_len); 2626 break; 2627 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 16 Nov '20

16 Nov '20

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 1 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 3 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 1499551: Null pointer dereferences (REVERSE_INULL) /bgpd/bgp_flowspec_vty.c: 304 in route_vty_out_flowspec() ________________________________________________________________________________________________________ *** CID 1499551: Null pointer dereferences (REVERSE_INULL) /bgpd/bgp_flowspec_vty.c: 304 in route_vty_out_flowspec() 298 else if (json_paths && display == NLRI_STRING_FORMAT_JSON) 299 json_object_array_add(json_paths, json_nlri_path); 300 if (!path) 301 return; 302 303 ipv6_ecomm = bgp_attr_get_ipv6_ecommunity(path->attr); >>> CID 1499551: Null pointer dereferences (REVERSE_INULL) >>> Null-checking "path->attr" suggests that it may be null, but it has already been dereferenced on all paths leading to the check. 304 if (path->attr && (path->attr->ecommunity || ipv6_ecomm)) { 305 /* Print attribute */ 306 attr = path->attr; 307 if (attr->ecommunity) 308 s1 = ecommunity_ecom2str(attr->ecommunity, 309 ECOMMUNITY_FORMAT_ROUTE_MAP, 0); ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

Announcing the 7.5 release of FRR
by Donald Sharp 16 Nov '20

16 Nov '20

All - I'd like to announce the 7.5 release of FRR! Debian Packaging - https://deb.frrouting.org/ Snap Packaging - https://snapcraft.io/frr RPM Packaging - https://rpm.frrouting.org/ Github Release - FreeBSd Packaging - Are built and available in FreeBSD packages/port BFD Profile support Minimum ttl support BGP rpki VRF support GR fixes Add wide option to display of routes Add `maximum-prefix <num> force` Add `bestpath-routes` to neighbor command Add `bgp shutdown message MSG...` command Add v6 Flowspec support Add `neighbor <neigh> shutdown rtt` command Allow update-delay to be applied globaly EVPN Beginning of MultiHoming Support ISIS Segment Routing Support VRF Support Guard against adj timer display overflow Add support for Anycast-SIDs OSPF Segment Routing support for ECMP Various LSA fixes Prevent crash if transferring config amongst instances PBR Adding json support to commands DSCP/ECN based PBR Matching PIM Add more json support to commands Fix missing mesh-group commands MSDP SA forwarding Clear (s,g,rpt) ifchannel on (*, G) prune received Fix igmp querier election and IP address mapping Crash fix when RP is removed STATIC Northbound Support YANG Filter and route-map Support OSPF model definition BGP model definition VTYSH Fix build-time errors for some --enable flags Speed up output of configuration across daemons ZEBRA nexthop group support for FPM northbound support for rib model Backup nexthop support netlink batching support Allow upper level protocols to request ARP Add json output for zebra ES, ES-EVI and access vlan dumps Upgrade to using libyang1.0.184 RPM Moved RPKI to subpackage Added SNMP subpackage Centos 6 and Debian Jessie have been deprecated As always there are too many bugfixes to list individually. This release compromises just over 1k of commits by the community, with contributors from 70 people. thanks! Donald

1 1

Northbound weekly meeting
by Lou Berger 13 Nov '20

13 Nov '20

1 0

Northbound weekly meeting
by Lou Berger 12 Nov '20

12 Nov '20

1 0