FRR
FRRouting
| Tests: | 6609 passed |
|---|---|
| Duration: | 127 minutes |
| Changes: | Who: Mark Stapp <mjs@voltanet.io> Why: Merge pull request #4165 from dslicenc/rnh-invalid-nexthops zebra: stop sending invalid nexthops to clients Who: Don Slice <dslice@cumulusnetworks.com> Why: zebra: stop sending invalid nexthops to clients Found that zebra_rnh_apply_nht_rmap would set the NEXTHOP_FLAG_ACTIVE if not blocked by the route-map, even if the flag was not active prior to the check. This fix changes the flag used to denote the nexthop is filtered so that proper active state can be retained. Additionally, found two cases where we would send invalid nexthops via send_client, which would also cause this crash. All three fixed in this commit. Signed-off-by: Don Slice <dslice@cumulusnetworks.com> |
Manual run by Martin Winter
Rebuilt by Martin Winter
Manual run by Martin Winter
Rebuilt by Martin Winter
Manual run by Martin Winter
FRR Release 6.0.x Build
FRRouting
| Tests: | 437 passed |
|---|---|
| Duration: | 133 minutes |
| Changes: | Who: Martin Winter Why: FRRouting Release 6.0.2 This is a maintenance release for a security (Denial of Service) issue found with the expermimental BGP VNC Attribute (255). Other experiments using the same attribute may bring down BGP peers if they are malformed for the VNC parsing. (As required by RFC). The update disables the parsing of the VNC attribute by default to avoid this. Beside this change, this release is similar to 6.0.1 Major Changes since 6.0 (already in 6.0.1) - New Debian Package structure without backports - Fix Memory Leak on FreeBSD - Fix BGP unnumbered peer setup - Various fixes for label manager - Various other fixes Signed-off-by: Martin Winter <mwinter@opensourcerouting.org> Who: Lou Berger Why: bgpd: don"t use BGP_ATTR_VNC(255) unless ENABLE_BGP_VNC_ATTR is defined Signed-off-by: Lou Berger <lberger@labn.net> Who: Donald Sharp Why: Merge pull request #3524 from manuhalo/fix_autoreconf /: add -f to autoreconf in bootstrap Who: Donald Sharp Why: Merge pull request #3577 from LabNConsulting/working/6.0/no-bgp-attr-255 6.0: bgpd: don"t use BGP_ATTR_VNC(255) unless ENABLE_BGP_VNC_ATTR is defined |
Rebuilt by Martin Winter
FRR Release 7.0 Build
FRRouting
| Tests: | Testless build |
|---|---|
| Duration: | 68 minutes |
| Changes: | Who: Martin Winter Why: FRRouting Release 7.0 Major Changes since 6.0.x: - Added libyang dependency: New work for northbound interface based on libyang - Fabricd: New Daemon based on https://datatracker.ietf.org/doc/draft-white-openfabric/ - various bug fixes and other enhancements Signed-off-by: Martin Winter <mwinter@opensourcerouting.org> |
Custom build by Martin Winter with revision frr-7.0
Rebuilt by Martin Winter
Rebuilt by Martin Winter
FRR-6.0-Snapcraft
FRRouting
| Tests: | 1322 passed |
|---|---|
| Duration: | 962 minutes |
| Changes: | Who: Donald Sharp Why: Merge pull request #3577 from LabNConsulting/working/6.0/no-bgp-attr-255 6.0: bgpd: don"t use BGP_ATTR_VNC(255) unless ENABLE_BGP_VNC_ATTR is defined Who: Lou Berger Why: bgpd: don"t use BGP_ATTR_VNC(255) unless ENABLE_BGP_VNC_ATTR is defined Signed-off-by: Lou Berger <lberger@labn.net> Who: Martin Winter Why: FRRouting Release 6.0.2 This is a maintenance release for a security (Denial of Service) issue found with the expermimental BGP VNC Attribute (255). Other experiments using the same attribute may bring down BGP peers if they are malformed for the VNC parsing. (As required by RFC). The update disables the parsing of the VNC attribute by default to avoid this. Beside this change, this release is similar to 6.0.1 Major Changes since 6.0 (already in 6.0.1) - New Debian Package structure without backports - Fix Memory Leak on FreeBSD - Fix BGP unnumbered peer setup - Various fixes for label manager - Various other fixes Signed-off-by: Martin Winter <mwinter@opensourcerouting.org> |
Rebuilt by Martin Winter
FRR-7.0-Snapcraft
FRRouting
| Tests: | 8 of 1507 failed |
|---|---|
| Duration: | 967 minutes |
| Changes: | Who: Renato Westphal Why: bgpd: add missing checks for vpnv6 nexthop lengths A few code paths weren"t handling the vpnv6 nexthop lenghts as expected, which was leading to problems like imported vpnv6 routes not being marked as valid when they should. Fix this. Signed-off-by: Renato Westphal <renato@opensourcerouting.org> Who: Donald Sharp Why: Merge pull request #3896 from opensourcerouting/7.0-fix-6vpe [7.0] 6VPE fixes Who: Renato Westphal Why: Revert "bgpd: in case nexthop is ipv6, set nh attribute flag in mpls vpn case" BGP IPv6 routes should never contain the NEXT_HOP attribute (MP_REACH_NLRI should be used instead). This reverts commit 75cd35c6977137a14ac37347a465d4e8a91eb4c4. Signed-off-by: Renato Westphal <renato@opensourcerouting.org> |
Manual run by Martin Winter
FRR-Pull-Requests
FRRouting
| Tests: | 5271 passed |
|---|---|
| Duration: | 68 minutes |
| Changes: | Who: Mark Stapp <mjs@voltanet.io> Why: Merge pull request #4165 from dslicenc/rnh-invalid-nexthops zebra: stop sending invalid nexthops to clients |
Custom build by Github Hook with revision master
OpenFabric
FRRouting
| Tests: | 6046 passed |
|---|---|
| Duration: | 169 minutes |
| Changes: | Who: David Lamparter Why: isisd: silence SA warnings As suggested by Renato Westphal. Signed-off-by: David Lamparter <equinox@diac24.net> |
Changes by David Lamparter
Snapcraft
FRRouting
| Tests: | 1323 passed |
|---|---|
| Duration: | 920 minutes |
| Changes: | Who: David Lamparter Why: pimd: fix clang warning pimd/pim_sock.c:178:13: error: implicit conversion from "int" to "char" changes value from 148 to -108 [-Werror,-Wconstant-conversion] ra[0] = 148; Signed-off-by: David Lamparter <equinox@opensourcerouting.org> Who: Jafar Al-Gharaibeh <Jafaral@users.noreply.github.com> Why: Merge pull request #461 from donaldsharp/poll_2.0 Poll 2.0 Who: Donald Sharp Why: lib: Rename HAVE_POLL to prevent conflicting #defines Rename HAVE_POLL to HAVE_POLL_CALL, when compiling with snmp and poll enabled this was causing issues. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com> Who: Sam Tannous <stannous@cumulusnetworks.com> Why: Remove uncalled function causing compiler error Ticket: CM-16086 Reviewed By: sharpd Testing Done: Built debs and tested on hardnode With snmp enabled, this function was causing compiler errors since it was not being called. Removed it. Signed-off-by: Sam Tannous <stannous@cumulusnetworks.com> |
Rebuilt by Martin Winter
TopoTest PullReq
FRRouting
| Tests: | 9 of 1240 failed |
|---|---|
| Duration: | 47 minutes |
| Changes: | Who: Rafael Zalamena <rzalamena@users.noreply.github.com> Why: Merge pull request #145 from donaldsharp/staticd_warning Add a tiny breadcrumb to hopefully help end user Who: Mark Stapp <mjs@voltanet.io> Why: zebra: dataplane provider enhancements Limit the number of updates processed from the incoming queue; add more stats. Fill out apis for dataplane providers; convert route update processing to provider model; move dataplane status enum Signed-off-by: Mark Stapp <mjs@voltanet.io> Who: F. Aragon <paco@voltanet.io> Why: bgpd: null check (Coverity 1475469) Null check of "rn" returned by bgp_node_lookup() because it could be deferenced afterwards into bgp_nexthop_get_node_info() Signed-off-by: F. Aragon <paco@voltanet.io> Who: F. Aragon <paco@voltanet.io> Why: isisd lib ospfd pbrd python: fix empty init ISO C forbids empty initializer braces. Empty initializers have been replaced with {0} Signed-off-by: F. Aragon <paco@voltanet.io> Who: Russ White <russ@riw.us> Why: Merge pull request #3339 from opensourcerouting/bugfix/isis-flooding-issues isis: Fix flooding issues ... |
Custom build by Github Hook with revision master