- dev - lists.frrouting.org

Discussion call about interface naming <> namespace VRF next Monday 14:00 UTC
by David Lamparter 14 Nov '18

14 Nov '18

Hi all, Philippe and I are setting up a call to talk about interface naming considerations in the face of namespaced VRFs, i.e. when names aren't unique anymore. This is related to PR #3246 for the distribute list use case. We'll hop on the usual Bluejeans: https://bluejeans.com/9192742159/ Monday 19th at 14:00 UTC (6:00 PST / 9:00 EST / 15:00 CET / 19:30 IST) Per usual, everyone is welcome to attend, if anyone with knowledge of the BSD network stacks is around that would be especially cool. Cheers, -David

1 0

A quick question about RFC 5512?
by Jia Chen 14 Nov '18

14 Nov '18

I have a question to FRR BGP exports, what is the status regarding RFC 5512? Thanks, Jay From: dev <dev-bounces(a)lists.frrouting.org> on behalf of Donald Sharp <sharpd(a)cumulusnetworks.com> Date: Wednesday, October 24, 2018 at 6:09 AM To: "tamar_c(a)rad.com" <tamar_c(a)rad.com> Cc: "arik_p(a)rad.com" <arik_p(a)rad.com>, FRRouting-Dev <dev(a)lists.frrouting.org>, frog <frog(a)lists.frrouting.org> Subject: Re: [dev] [FROG] Multicast Protocol The `show ip multicast` command is showing that pim does not think vpp0 or vpp1 have an ip address or an associated VIFI in the linux kernel. I would recommend trying this again: conf t interface vpp0 no ip pim sm ip pim sm ! interface vpp1 no ip igmp join 224.1.1.1 3.3.3.4 no ip pim sm ip pim sm ip igmp join 224.1.1.1 3.3.3.4 ! Then let's re-issue a `show ip multicast` and see if those interfaces are now configured under pim. If not we can discuss debugging. I would also recommend joining the FRRouting slack for a real-time debugging ability. donald On Wed, Oct 24, 2018 at 8:17 AM Tamar Cohen <tamar_c(a)rad.com<mailto:tamar_c@rad.com>> wrote: Hi Donald and thank you!!!! Show ip multicast: [cid:image001.png@01D46BAC.425969D0] Show ip pim rp-info [cid:image002.png@01D46BAC.AD5F5500] Show running-config: [cid:image003.png@01D46BAC.AD5F5500] What I miss? Thank you!!!! From: Donald Sharp [mailto:sharpd@cumulusnetworks.com<mailto:sharpd@cumulusnetworks.com>] Sent: Wednesday, October 24, 2018 14:41 To: Tamar Cohen <tamar_c(a)rad.com<mailto:tamar_c@rad.com>> Cc: FRRouting-Dev <dev(a)lists.frrouting.org<mailto:dev@lists.frrouting.org>>; frog <frog(a)lists.frrouting.org<mailto:frog@lists.frrouting.org>>; Arik Peretz <arik_p(a)rad.com<mailto:arik_p@rad.com>> Subject: Re: [FROG] Multicast Protocol 1) PIM-SM works, we are going to need a bit more data, can we get the output of `show ip multicast` and `show ip pim rp-info` as a start? 2) `terminal monitor` is currently only meant for when you telnet into a particular daemon. There is no good way to have asynchronous logging data between all the daemons be sent to the vtysh process for what you are trying to do. I would suggest using a `log file XXX` and in another window tail'ing that file. I have also been known to turn on debugging, watching the log file via a `tail -f XXXX &` and then invoking vtysh to see output as I do work. 3) this is the same question as #1, so yes. donald On Wed, Oct 24, 2018 at 7:34 AM Tamar Cohen <tamar_c(a)rad.com<mailto:tamar_c@rad.com>> wrote: Hi all, My name is Tamar and I have the release 5.0.1 of the FRRouting, it is an excellent IP routing protocol suite! I try to use frr in multicast traffic. 1) Is frr support multicast traffic? (I ask because I tried without success) I write this commands: ip multicast ip pim rp IP ADDR inteface INTERFACE ip pim sm\\ in all interfaces Also I add an ospf: router ospf 1 network 0.0.0.0 0.0.0.0 area 0 my setup include tow PC and one additional router (VM of cisco) Error! Filename not specified. This setup does not foreword a multicast traffic unfortunately … 2) I try to debug the traffic in the frr with the “debug” commands but it does not print to the screen anything. In the manual Error! Filename not specified. When I wrote the command I got Error! Filename not specified. Why? 3) Is the frr support pim protocol? It is written in the manual but not work in my setup I would be very grateful if you could help me with this. Thank you! Tamar Error! Filename not specified. Tamar Cohen NFV SW Engineer T: +972-73-270-7625 F: +972-08-6436791 | tamar_c(a)rad.com<mailto:tamar_c@rad.com> www.rad.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__emea01.safelinks.prote…> | Follow RAD on LinkedIn<https://urldefense.proofpoint.com/v2/url?u=https-3A__emea01.safelinks.prote…> | Facebook<https://urldefense.proofpoint.com/v2/url?u=https-3A__emea01.safelinks.prote…> | Twitter<https://urldefense.proofpoint.com/v2/url?u=https-3A__emea01.safelinks.prote…> | YouTube<https://urldefense.proofpoint.com/v2/url?u=https-3A__emea01.safelinks.prote…> _______________________________________________ frog mailing list frog(a)lists.frrouting.org<mailto:frog@lists.frrouting.org> https://lists.frrouting.org/listinfo/frog<https://urldefense.proofpoint.com/v2/url?u=https-3A__emea01.safelinks.prote…>

1 0

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

13 Nov '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 1475469: Null pointer dereferences (NULL_RETURNS) ________________________________________________________________________________________________________ *** CID 1475469: Null pointer dereferences (NULL_RETURNS) /bgpd/bgp_nht.c: 870 in bgp_nht_register_enhe_capability_interfaces() 864 } 865 866 if (p.family != AF_INET6) 867 return; 868 rn = bgp_node_lookup(bgp->nexthop_cache_table[AFI_IP6], &p); 869 >>> CID 1475469: Null pointer dereferences (NULL_RETURNS) >>> Dereferencing a pointer that might be null "rn" when calling "bgp_nexthop_get_node_info". 870 bnc = bgp_nexthop_get_node_info(rn); 871 if (!bnc) 872 return; 873 874 if (peer != bnc->nht_info) 875 return; ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0…

1 0

Intel Vtune - Open Source non-commercial license for VTune (Parallel Studio XE)
by Jeff Tantsura 06 Nov '18

06 Nov '18

https://software.intel.com/en-us/qualify-for-free-software/opensourcecontri… <https://software.intel.com/en-us/qualify-for-free-software/opensourcecontri…>

1 0

Fwd: [NetDev-People] CFS for Netdev 0x13 open!
by Donald Sharp 06 Nov '18

06 Nov '18

All - Netdev has opened up submissions for the upcoming conference in prague. It would be a great idea to consider presenting something for the community to have as well as consider attending to meet and discuss with your fellow co-developers upcoming projects!. donald ---------- Forwarded message --------- From: Jamal Hadi Salim via people <people(a)lists.netdevconf.org> Date: Mon, Nov 5, 2018 at 3:42 PM Subject: [NetDev-People] CFS for Netdev 0x13 open! To: people <people(a)netdevconf.org> Cc: linux-wireless <linux-wireless(a)vger.kernel.org>, netdev(a)vger.kernel.org <netdev(a)vger.kernel.org>, <netfilter-devel(a)vger.kernel.org>, <lwn(a)lwn.net> We are pleased to announce the opening of call for submissions(CFS) for Netdev 0x13. For overview of topics, submissions and requirements please visit: https://netdevconf.org/0x13/submit-proposal.html Sessions are selected via a blind review process carried out by the Program Committee and Shepherd. Please refer to: https://www.netdevconf.org/0x13/pc_review.html Important dates: Closing of CFS: Tue, January 15, 2019. Acceptance or rejection notification by: Fri, January 18, 2019 Conference dates: Wed, March 20 to Fri, March 22. cheers, jamal _______________________________________________ people mailing list people(a)netdevconf.org https://lists.netdevconf.org/cgi-bin/mailman/listinfo/people

1 0

Northbound API and the new libyang dependency
by Renato Westphal 06 Nov '18

06 Nov '18

Hi all, I'd like to announce that the Northbound API PR [1] was merged a couple of days ago. This is only the beginning of a long journey to modernize FRR with a model-driven architecture based on the YANG modeling language. The goal of this initiative is to provide better interfaces to configure and monitor FRR programatically, since the good old CLI is unfit for that purpose. Examples of new management interfaces include the NETCONF and RESTCONF protocols (supported though the ConfD and Sysrepo plugins). There's also a new gRPC-based northbound plugin under development and the CLI will of course continue to be available, now with new features like support for configuration transactions and rollbacks (please check the demos [2]). It's important to say, however, that only daemons converted to the new northbound model will be able to take advantage of the new northbound capabilities. As of now, only the ripd daemon was converted (ripd was chosen for being one of the simplest daemons we have). This means we can configure/monitor ripd using NETCONF for example, but the same doesn't apply to the other daemons yet. The remaining daemons should be converted within the next few months, and everyone from the community is welcome to collaborate :) For more information about the new Northbound API, please check the documentation [3]. As a consequence of this work, FRR will have a new mandatory dependency: libyang [4]. Everyone please check the updated FRR build instructions to see how to obtain and install this library for your platform. Thanks everyone who collaborated to make this possible! Best Regards, Renato. [1] https://github.com/FRRouting/frr/pull/2705 [2] https://github.com/opensourcerouting/frr/wiki/Demos [3] https://github.com/opensourcerouting/frr/wiki/Architecture [4] https://github.com/CESNET/libyang

1 0

Open source routing @ ietf meetup -- Tuesday Lunch
by Lou Berger 05 Nov '18

05 Nov '18

Hi, We're continuing with the informal Open source routing @ ietf meetup. Anyone interested in joining a "bring your own lunch" gathering of folks using/building open source routing code, please drop in to "Borophimarn 3 on the 3rd floor" on *Tuesday* during lunch (noon). There is no agenda or slides. Please feel free to bring a topic that you'd like to discuss or just come and listen. Cheers, Lou https://datatracker.ietf.org/meeting/103/floor-plan#3rd-floor

1 0

slack request
by Felt, Patrick 02 Nov '18

02 Nov '18

I’d like to request an account in the slack. Thanks,

2 1

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

01 Nov '18

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 4 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 4 of 4 defect(s) ** CID 1475322: Null pointer dereferences (FORWARD_NULL) ________________________________________________________________________________________________________ *** CID 1475322: Null pointer dereferences (FORWARD_NULL) /ripd/rip_cli_clippy.c: 1531 in ip_rip_authentication_mode() 1525 } 1526 #if 0 /* anything that can fail? */ 1527 if (_failcnt) 1528 return CMD_WARNING; 1529 #endif 1530 #endif >>> CID 1475322: Null pointer dereferences (FORWARD_NULL) >>> Passing null pointer "mode" to "ip_rip_authentication_mode_magic", which dereferences it. 1531 return ip_rip_authentication_mode_magic(self, vty, argc, argv, mode, auth_length); 1532 } 1533 1534 /* no_ip_rip_authentication_mode => "no ip rip authentication mode [<md5 [auth-length <rfc|old-ripd>]|text>]" */ 1535 DEFUN_CMD_FUNC_DECL(no_ip_rip_authentication_mode) 1536 #define funcdecl_no_ip_rip_authentication_mode static int no_ip_rip_authentication_mode_magic(\ ** CID 1475321: Null pointer dereferences (FORWARD_NULL) ________________________________________________________________________________________________________ *** CID 1475321: Null pointer dereferences (FORWARD_NULL) /lib/northbound_cli_clippy.c: 672 in yang_module_translator_unload_family() 666 } 667 #if 0 /* anything that can fail? */ 668 if (_failcnt) 669 return CMD_WARNING; 670 #endif 671 #endif >>> CID 1475321: Null pointer dereferences (FORWARD_NULL) >>> Passing null pointer "translator_family" to "yang_module_translator_unload_family_magic", which dereferences it. 672 return yang_module_translator_unload_family_magic(self, vty, argc, argv, translator_family); 673 } 674 675 /* show_config_transaction => "show configuration transaction [ (1-4294967296)$transaction_id [<json$json|xml$xml> [translate WORD$translator_family]] [< with-defaults$with_defaults |changes$changes >] ]" */ 676 DEFUN_CMD_FUNC_DECL(show_config_transaction) 677 #define funcdecl_show_config_transaction static int show_config_transaction_magic(\ ** CID 1475320: Null pointer dereferences (FORWARD_NULL) ________________________________________________________________________________________________________ *** CID 1475320: Null pointer dereferences (FORWARD_NULL) /ripd/rip_cli_clippy.c: 1612 in ip_rip_authentication_string() 1606 } 1607 #if 0 /* anything that can fail? */ 1608 if (_failcnt) 1609 return CMD_WARNING; 1610 #endif 1611 #endif >>> CID 1475320: Null pointer dereferences (FORWARD_NULL) >>> Passing null pointer "password" to "ip_rip_authentication_string_magic", which dereferences it. 1612 return ip_rip_authentication_string_magic(self, vty, argc, argv, password); 1613 } 1614 1615 /* no_ip_rip_authentication_string => "no ip rip authentication string [LINE]" */ 1616 DEFUN_CMD_FUNC_DECL(no_ip_rip_authentication_string) 1617 #define funcdecl_no_ip_rip_authentication_string static int no_ip_rip_authentication_string_magic(\ ** CID 1475319: Security best practices violations (SECURE_TEMP) /lib/northbound_cli.c: 419 in nb_write_config() ________________________________________________________________________________________________________ *** CID 1475319: Security best practices violations (SECURE_TEMP) /lib/northbound_cli.c: 419 in nb_write_config() 413 { 414 int fd; 415 struct vty *file_vty; 416 int ret = 0; 417 418 snprintf(path, pathlen, "/tmp/frr.tmp.XXXXXXXX"); >>> CID 1475319: Security best practices violations (SECURE_TEMP) >>> Calling "mkstemp" without securely setting umask first. 419 fd = mkstemp(path); 420 if (fd < 0) { 421 flog_warn(EC_LIB_SYSTEM_CALL, "%s: mkstemp() failed: %s", 422 __func__, safe_strerror(errno)); 423 return -1; 424 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0…

1 0

Reminder/Warning: weekly call might be earlier/later in some timezones due to DST
by David Lamparter 30 Oct '18

30 Oct '18

Hi all, just a heads-up/reminder/warning: since some countries move out/in to daylight savings time, and the date and direction differs between countries. So, the weekly meeting might be at a different local time for some of us. (e.g.: it's an hour earlier this week for everyone in the EU.) For today: it's in 20 minutes! Cheers, -David

1 0