January 2022 - dev - lists.frrouting.org

FRR Telco Call (Bi-Weekly)
by Alistair Woodman 25 Jan '22

25 Jan '22

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 14.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16011104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CN=dev@lists.frrouting.org;RSVP=TRUE:mailto:dev@lists.frrouting.or g ATTENDEE;CN=olivier.dugeon@orange.com;RSVP=TRUE:mailto:olivier.dugeon@orang e.com CLASS:PUBLIC CREATED:20220126T053025Z DESCRIPTION:Discuss FRR #Telco channel projects and PRs\n DTEND;TZID="Pacific Standard Time":20220127T080000 DTSTAMP:20220126T053025Z DTSTART;TZID="Pacific Standard Time":20220127T070000 LAST-MODIFIED:20220126T053029Z LOCATION:https://bluejeans.com/377688464 ORGANIZER;CN="Alistair Woodman":mailto:awoodman@netdef.org PRIORITY:5 RRULE:FREQ=WEEKLY;COUNT=13;INTERVAL=2;BYDAY=TH;WKST=SU SEQUENCE:0 SUMMARY;LANGUAGE=en-us:FRR Telco Call (Bi-Weekly) TRANSP:OPAQUE UID:040000008200E00074C5B7101A82E00800000000301BA6363212D801000000000000000 010000000BC2E60F5A724FD4DB508800FAB1B8D76 X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve rsion 14.02.5004.000">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n\n\nDiscuss FRR #Telco channel projects and PRs\n\n</BODY>\n</HTML> X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-DISALLOW-COUNTER:FALSE X-MS-OLK-AUTOSTARTCHECK:FALSE X-MS-OLK-CONFTYPE:0 BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 24 Jan '22

24 Jan '22

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 1511183: Incorrect expression (COPY_PASTE_ERROR) /ospfd/ospf_vty.c: 6824 in show_ip_ospf_database_summary() ________________________________________________________________________________________________________ *** CID 1511183: Incorrect expression (COPY_PASTE_ERROR) /ospfd/ospf_vty.c: 6824 in show_ip_ospf_database_summary() 6818 } 6819 6820 count += show_lsa_summary( 6821 vty, lsa, self, json_lsa); 6822 } 6823 >>> CID 1511183: Incorrect expression (COPY_PASTE_ERROR) >>> "json" looks like a copy-paste error. 6824 if (!json) 6825 vty_out(vty, "\n"); 6826 else 6827 json_object_int_add( 6828 json_area, 6829 ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

Next step for the Telco Meeting
by olivier.dugeon＠orange.com 12 Jan '22

12 Jan '22

Dear all, Following the last Telco Meeting and the discussion about the future of the Telco Meeting during the last regular meeting, I open a new thread on the mailing list to discuss how to organize Telco Meeting for 2022. Context: ======== - First, starting mid-2021, we reduce the number of Telco Meeting from bi-weekly to monthly meeting. - Second, number of attendees decrease regularly as well as number of subjects. - As a consequence, it seams reasonable to stop Telco Meeting by end of 2021. - However, during the lastTelco meeting, it appears that we need to continue coordination at least for Segment RoutingFlex algorithm at least between Hiroki who develop Flex Algo for IS-IS, Pushpasis who do thesame for OSPF and myself who develop Constraints SPF algorithm for Flex Algo based on delayand TE metric. Proposal: ========= - Continue a regular cycle of meeting dedicated to coordinate the development of new features - Give time for presentation of new features, new architectures, new daemons ... for FRR - Discuss FRR roadmap and organize which features will be part of the next FRR release - And to reflect the new orientation, rename Telco Meeting e.g. New Features Meeting Thus, it was decided during the last regular meeting, to open discussion on the mailing list (the object of this thread) and organize a dedicated meeting to discuss the future of the Telco Meeting for 2022 and beyond. I'll send an invit for such meeting by taking the slot of the next Telco Meeting i.e. the 12th of January 17h00 CEST. Best Regards Olivier _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 1

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 11 Jan '22

11 Jan '22

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 2 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 2 of 2 defect(s) ** CID 1510738: Null pointer dereferences (FORWARD_NULL) ________________________________________________________________________________________________________ *** CID 1510738: Null pointer dereferences (FORWARD_NULL) /bgpd/bgp_vty.c: 4243 in bgp_shutdown_msg_magic() 4237 if (msgstr && strlen(msgstr) > BGP_ADMIN_SHUTDOWN_MSG_LEN) { 4238 vty_out(vty, "%% Shutdown message size exceeded %d\n", 4239 BGP_ADMIN_SHUTDOWN_MSG_LEN); 4240 return CMD_WARNING_CONFIG_FAILED; 4241 } 4242 >>> CID 1510738: Null pointer dereferences (FORWARD_NULL) >>> Passing null pointer "msgstr" to "bgp_shutdown_enable", which dereferences it. 4243 bgp_shutdown_enable(bgp, msgstr); 4244 XFREE(MTYPE_TMP, msgstr); 4245 4246 return CMD_SUCCESS; 4247 } 4248 ** CID 1510737: Null pointer dereferences (REVERSE_INULL) /bgpd/bgpd.c: 4344 in bgp_shutdown_enable() ________________________________________________________________________________________________________ *** CID 1510737: Null pointer dereferences (REVERSE_INULL) /bgpd/bgpd.c: 4344 in bgp_shutdown_enable() 4338 /* continue, if peer is already in administrative shutdown. */ 4339 if (CHECK_FLAG(peer->flags, PEER_FLAG_SHUTDOWN)) 4340 continue; 4341 4342 /* send a RFC 4486 notification message if necessary */ 4343 if (BGP_IS_VALID_STATE_FOR_NOTIF(peer->status)) { >>> CID 1510737: Null pointer dereferences (REVERSE_INULL) >>> Null-checking "msg" suggests that it may be null, but it has already been dereferenced on all paths leading to the check. 4344 if (msg) 4345 bgp_notify_send_with_data( 4346 peer, BGP_NOTIFY_CEASE, 4347 BGP_NOTIFY_CEASE_ADMIN_SHUTDOWN, data, 4348 datalen + 1); 4349 else ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

Eesppsspdlpppllapllkk
by Karuppiah, Jeyachandran 09 Jan '22

09 Jan '22

Jve Get Outlook for Android<https://aka.ms/AAb9ysg>

1 0