May 2017 - dev - lists.frrouting.org

Re: [dev] EIGRP
by Donald Sharp 07 May '17

07 May '17

Ismail - We actually have a PR for this open: https://github.com/FRRouting/frr/pull/409 Items that needed to be cleaned up were: 1) Some basic documentation ( I actually just pushed this in minutes ago ) 2) Permission/notification from original Authors. ( I also just sent an email to get some clarification on this ) So all in all, I hope this will happen sooner rather than later. donald On Sat, May 6, 2017 at 1:36 PM, ismail via dev <dev(a)lists.frrouting.org> wrote: > _______________________________________________ > dev mailing list > dev(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/dev > > > ---------- Forwarded message ---------- > From: ismail <ismail.elalami(a)yahoo.fr> > To: dev(a)lists.frrouting.org > Cc: > Bcc: > Date: Sat, 6 May 2017 19:36:26 +0200 > Subject: [dev] EIGRP > > Hi everyone, > > > is there any Plan to add EIGRP to FRRouting? > > > Regards, > > Ismail > >

1 0

EIGRP
by ismail 07 May '17

07 May '17

Hi everyone, is there any Plan to add EIGRP to FRRouting? Regards, Ismail

1 0

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

05 May '17

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. 4 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 1433168: (FORWARD_NULL) /pimd/pim_ifchannel.c: 1086 in pim_ifchannel_local_membership_del() /pimd/pim_ifchannel.c: 1086 in pim_ifchannel_local_membership_del() ________________________________________________________________________________________________________ *** CID 1433168: (FORWARD_NULL) /pimd/pim_ifchannel.c: 1086 in pim_ifchannel_local_membership_del() 1080 * has output here then the *,G was supplying the implied 1081 * if channel. So remove it. 1082 */ 1083 if (!chchannel && c_oil && c_oil->oil.mfcc_ttls[pim_ifp->mroute_vif_index]) 1084 pim_channel_del_oif (c_oil, ifp, PIM_OIF_FLAG_PROTO_STAR); 1085 >>> CID 1433168: (FORWARD_NULL) >>> Dereferencing null pointer "c_oil". 1086 if (c_oil->oil_size == 0) 1087 pim_upstream_del (child, __PRETTY_FUNCTION__); 1088 } 1089 } 1090 delete_on_noinfo(orig); 1091 } /pimd/pim_ifchannel.c: 1086 in pim_ifchannel_local_membership_del() 1080 * has output here then the *,G was supplying the implied 1081 * if channel. So remove it. 1082 */ 1083 if (!chchannel && c_oil && c_oil->oil.mfcc_ttls[pim_ifp->mroute_vif_index]) 1084 pim_channel_del_oif (c_oil, ifp, PIM_OIF_FLAG_PROTO_STAR); 1085 >>> CID 1433168: (FORWARD_NULL) >>> Dereferencing null pointer "c_oil". 1086 if (c_oil->oil_size == 0) 1087 pim_upstream_del (child, __PRETTY_FUNCTION__); 1088 } 1089 } 1090 delete_on_noinfo(orig); 1091 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0… To manage Coverity Scan email notifications for "frr(a)lists.nox.tf", click https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0…

1 0

Now frr-2.0 and frr-3.0-dev available in snap store
by Martin Winter 04 May '17

04 May '17

I’ve started to upload 3.0-dev images to the snap store. There are 4 channels on the snap store for different versions of the code: - stable - release candidate - beta - edge The default channel which is used (unless the user overrides it), is the stable channel. “stable” and “release candidate” contain the 2.0 version of FRR and “beta” and “edge” now contain the 3.0 code Snap’s are published for amd64, i386, armhf, arm64 and ppc64el CPU architectures. For release versions, I’ve named them 3.0-dev-20170428 (date of the git when it was pulled) I’m planning to update the 3.0 code on the store on a weekly base. I’m also thinking about pushing builds based on master to the edge channel (and keep 3.0 only on beta and soon release candidate channel). I’ve attached some stat output from the snap store to this email as well. - Martin

3 4

Please add me to the slack group for FRR
by Mary Manohar 04 May '17

04 May '17

3 4

Proposal to change CLI syntax of 'show ip rib <u_addr> to 'show ip pim rib <u_addr>
by Chirag Shah 03 May '17

03 May '17

Hello All, The CLI command 'show ip rib <unicast addr> is in pim_cmd.c which invokes zebra lookup for nexthops and return the first available path to user. Ideally the command is for PIMd (Zebra Client for nexthop info). I would like to propose to change to CLI to specific to PIMd 'show ip *pim *rib <uincat addr> rather generic than "ip rib" term. Please share your opinion. Kind Regards, Chirag Shah P.S. : Cli implementation from pim_cli.c DEFUN (show_ip_rib, show_ip_rib_cmd, "*show ip rib A.B.C.D*", SHOW_STR IP_STR RIB_STR "Unicast address\n") { struct in_addr addr; const char *addr_str; struct pim_nexthop nexthop; char nexthop_addr_str[PREFIX_STRLEN]; int result; memset (&nexthop, 0, sizeof (nexthop)); addr_str = argv[0]; result = inet_pton(AF_INET, addr_str, &addr); if (result <= 0) { vty_out(vty, "Bad unicast address %s: errno=%d: %s%s", addr_str, errno, safe_strerror(errno), VTY_NEWLINE); return CMD_WARNING; } if (*pim_nexthop_lookup*(&nexthop, addr, 0)) { vty_out(vty, "Failure querying RIB nexthop for unicast address %s%s", addr_str, VTY_NEWLINE); return CMD_WARNING; } vty_out(vty, "Address NextHop Interface Metric Preference%s", VTY_NEWLINE); pim_addr_dump("<nexthop?>", &nexthop.mrib_nexthop_addr, nexthop_addr_str, sizeof(nexthop_addr_str)); vty_out(vty, "%-15s %-15s %-9s %6d %10d%s", addr_str, nexthop_addr_str, nexthop.interface ? nexthop.interface->name : "<ifname?>", nexthop.mrib_route_metric, nexthop.mrib_metric_preference, VTY_NEWLINE); return CMD_SUCCESS; }

3 3

BGP v4 labeled unicast
by Donald Sharp 03 May '17

03 May '17

All - Thanks to the efforts of Vivek Venkatraman, Don Slice and Daniel Walton we now have BGP labeled unicast. - https://datatracker.ietf.org/doc/draft-rosen-idr-rfc3107bis/ And with a partial implementation of - https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-prefix-sid/ This code is available in the master branch. thanks! donald

1 0

Technical Meeting Agenda May 2 2017 11 am PDT
by Donald Sharp 02 May '17

02 May '17

https://bluejeans.com/9192742159 1) TSC Election info 2) Time decision 3) 3.0 issues 4) Issues 5) PR's 6) Reference Packaging 7) Slack channels thanks! donald

2 3

ISIS-MT support
by Donald Sharp 01 May '17

01 May '17

All -- We now have https://tools.ietf.org/html/rfc5120 support for FRR. This code is in the master branch, expect it to be part of an upcoming future release. I'd like to thank Christian Franke for taking the time and effort to get this code in! thanks! donald

1 0