May 2018 - dev - lists.frrouting.org

Re: [dev] Dataplane API
by Donald Sharp 10 Sep '18

10 Sep '18

I actually agree with both Vincent and Lou :) The current paradigm is a kernel based infrastructure and will be so for the foreseeable future. So if you are doing development *now* I would highly recommend working towards this paradigm. So Vincent is correct. Having said that, we are looking towards more formally defining the DataPlane API so that it becomes possible to allow a fully implemented dataplane api that if someone wanted to implement non-kernel based interfaces they could. So Lou is correct too! There is a lot of work here though, mainly of a infrastructure updates. I've currently (slowly) started trying to define this api( See https://github.com/FRRouting/frr/pull/2292 ). The current api line for the dataplane is fuzzy at best and lots of assumptions are made about behavior and how data structures are created. This line must be wedged apart as a first step. If you are unsure where to start here, please ask and we'll have suggestions. We also have additional goals for zebra such as true pthreads and nexthop-group route entry indirection to name a few. Please note we are not doing this work specifically to allow a full dataplane outside of a kernel, it should fall out if I do the work correctly for what I am interested in. I am doing this work because I think this work will allow me to do some work with route-aggregation as well as more efficiently pass data to the kernel for route installs. I'm sure other people have their own reasons, just as long as we keep those in mind and work together. thanks! donald On Tue, May 29, 2018 at 3:04 PM, Jay Chen <jchen1(a)paloaltonetworks.com> wrote: > A quick question about FRR interfaces. The Zebra get interface information/status from Kernel. > > In our platform, it is almost impossible to put interface into kernel (due to history reasons people object to do so). Is there anyone else facing the same situation and any suggestions for a work around? Or anything similarly to FPM existing for interface to bypass kernel (from interface manager to Zebra instead)? > > Thanks, > Jay > >

5 12

no soft bgp clear is triggered on modification to prefixlist / routemap
by François 02 Aug '18

02 Aug '18

Hello, This issue has been discussed here : https://github.com/FRRouting/frr/issues/126 To sum up, when a route-map is modified (tried 2 things: adding a new entry and modifying prefix-list involved), no soft bgp clear is performed, so it looks like other peers never get new results (the "show advertised route" output is correct). Looks like "no route-map ... " and "route-map ..." again does the trick. My question is: do someone has an idea on how to fix that? I can give a shot, but I would appreciate some inputs ;) Ps: I use version 2 of FRR (because Vincent Jardin told that version 3 was not production ready at FRNog 29 ;)) Thanks! -- François

3 6

Fwd: FW: FRRouting - RIP VRF Support.
by Amit Tiwari 26 Jul '18

26 Jul '18

Hi Kunihiro, I have compiled FRRouting master branch and deployed it on my router, bgp and ospf are working fine with vrf. Whereas, in case of RIP, vrf doesn't seems to be working, there is no vrf support even at CLI level. May we know, when are you guys releasing frrouting with full vrf support in RIP. Regards, Amit Kumar Tiwari 9953769181

3 2

Invite to Slack channel?
by JP Senior 12 Jun '18

12 Jun '18

Hello, there! I wonder if I or our domain @apstra.com can get an invite or whitelist to the FRRouting slack channel? We've got a lot of cool stuff to talk about with regards to EVPN and EVPN inter-operability. -- JP Senior | Apstra, Inc c: +1.403.970.4965 e: jp(a)apstra.com www.apstra.com | Vendor-Agnostic Data Center Network Automation

7 9

Slack invite
by Paco Aragon 30 May '18

30 May '18

Hi, I'm starting using the topotests for adding a test, and I would like to get a Slack invite for paco(a)voltanet.io , if possible (I saw invitation requests in the list, so I'm doing the same, please excuse the inconvenience) Thank you in advance :-) Paco

2 1

slack channel invite
by Yuriy Andamasov 29 May '18

29 May '18

Hello! Can we have invites to slack channel for yuriy(a)sentrium.io daniil(a)sentrium.io Thanks!

2 1

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 29 May '18

29 May '18

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. 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 1 of 1 defect(s) ** CID 1469463: Incorrect expression (CONSTANT_EXPRESSION_RESULT) /bgpd/bgp_pbr.c: 243 in bgp_pbr_validate_policy_route() ________________________________________________________________________________________________________ *** CID 1469463: Incorrect expression (CONSTANT_EXPRESSION_RESULT) /bgpd/bgp_pbr.c: 243 in bgp_pbr_validate_policy_route() 237 * for now, only match/set supported is 238 * - combination src/dst => redirect nexthop [ + rate] 239 * - combination src/dst => redirect VRF [ + rate] 240 * - combination src/dst => drop 241 * - combination srcport + @IP 242 */ >>> CID 1469463: Incorrect expression (CONSTANT_EXPRESSION_RESULT) >>> The expression "api->match_icmp_type_num || api->match_icmp_type_num" does not accomplish anything because it evaluates to either of its identical operands, "api->match_icmp_type_num". 243 if (api->match_icmp_type_num || api->match_icmp_type_num 244 || api->match_packet_length_num || api->match_dscp_num 245 || api->match_tcpflags_num) { 246 if (BGP_DEBUG(pbr, PBR)) { 247 bgp_pbr_print_policy_route(api); 248 zlog_debug("BGP: some SET actions not supported by Zebra. ignoring."); ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0…

1 0

Northbound API - Presentation this Friday
by Renato Westphal 23 May '18

23 May '18

Hi all, This Friday (18/May - 8am PST) I'll be making a presentation about my proposal to introduce a YANG-based northbound API in FRR. The main goal of this work is to provide a better interface to configure and monitor FRR programmatically. Everyone is welcomed to attend, no invitations needed. Link of the conference call: https://bluejeans.com/9192742159/ Best Regards, Renato.

2 4

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 18 May '18

18 May '18

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 1469172: Error handling issues (CHECKED_RETURN) /bgpd/bgp_route.c: 2551 in bgp_maximum_prefix_restart_timer() ________________________________________________________________________________________________________ *** CID 1469172: Error handling issues (CHECKED_RETURN) /bgpd/bgp_route.c: 2551 in bgp_maximum_prefix_restart_timer() 2545 2546 if (bgp_debug_neighbor_events(peer)) 2547 zlog_debug( 2548 "%s Maximum-prefix restart timer expired, restore peering", 2549 peer->host); 2550 >>> CID 1469172: Error handling issues (CHECKED_RETURN) >>> Calling "peer_clear" without checking return value (as is done elsewhere 5 out of 6 times). 2551 peer_clear(peer, NULL); 2552 2553 return 0; 2554 } 2555 2556 int bgp_maximum_prefix_overflow(struct peer *peer, afi_t afi, safi_t safi, ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0…

1 0

05/15/18 Technical Meeting Notes
by Quentin Young 15 May '18

15 May '18

05/15/18 FRR Technical Meeting Notes ==================================== 5.0 Status ----------- mwinter - testing looks good, just open issues & pr's that need to go into 5.0; will retest again when we have a release candidate Issues ------ #2201 - Doesn't seem like many people use this anymore; assigned mwinter #2204 - Partially fixed; needs unrelated changes to fully fix it; assigned dslice #2205 - User question; donaldsharp to update documentation #2228 - Assigned qlyoung #2206 - Fixed by #2226 (open) #2230 - Assigned donaldsharp #2232 - qlyoung & pguibert6WIND to discuss in slack #2233 - Question answered & closed, following up with Olson for further thoughts #2235 - Assigned pguibert6WIND for furhter investigation #2155 - cfra: haven't had time to work on it yet #2163 - donaldsharp will scrub #2147 - Various fixes, 4.0 should be fixed, pending fix for 5.0 to be reviewed by donaldsharp Pull Requests ------------- #1853 - rzalamena: manpage & documentation added, still open for review #2025 - Closed due to security and architectural concerns. Possibly revisit in the future w/ an architecture to segment the code away from FRR core. #2041 - Waiting on repsonse from vincentbernat #2034 - Waiting on response from vincentbernat #2144 - Merged #2122 - Some issues with state synchronization between staticd and zebra #2142 - donaldsharp to review #2186 - qlyoung to go look at how other projects handle packaging for multiple platforms & report back with better solution; closed #2198 - Fixes #2196, solution could be improved in the future; lberger to file issue to track better solution; donaldsharp to merge this one #2200 - rwestphal, mwinter to review #2210 - donaldsharp will rework patch and resubmit #2220 - lberger to try it again and report back, -ldl should not be necessary #2224 - cherry-pick, waiting on merge #2226 - qlyoung, donaldsharp to review #2231 - donaldsharp to review

1 0