With non-targeted LDP receiving a PW label mapping before configuring
the PW was causing the SET message to be sent before the ADD one, so
Zebra PW manager wouldn't find the PW on first message reception.
Signed-off-by: ßingen <bingen@voltanet.io>
When we have a v4 or v6 prefix list, only
apply it via a match when the address families
are the same.
Fixes: #1339
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
This version of FRR contains these fixes since the last release:
1. Some improved packaging fixes
2. Fix for miss-handling of BGP attributes in an error situation.
3. Fix for reading in of a nexthop as part of set ip nexthop ... command.
4. Fix for a memory leak in ISIS.
5. Check for per-peer outbound configuration, in addition to the peer-group config.
6. Enable '-S' usage for BGP.
(Re-Release of 3.0.1 which missed some version number and changelog updates)
Signed-off-by: Martin Winter <mwinter@opensourcerouting.org>
Fixes: #1420
Signed-off-by: Juergen Kammer <j.kammer@eurodata.de>
If the ipv6 ospf6 cost on an interface is changed, no recalculation of routes happens, though the interface structure is updated with the new value. The new cost will be used later, when LSA hooks are called for any other reason.
Diagnosis:
The DEFUN for the config command sets oi->cost and calls ospf6_interface_recalculate_cost(oi) whenever there is a change in the supplied value. ospf6_interface_recalculate_cost then gets the new cost for the interface by calling ospf6_interface_get_cost(oi), which returns oi->cost if a cost is manually set (i.e. we get the value we just set). ospf6_interface_recalculate_cost only calls the LSA hooks if there is a change - which obviously never happens if we compare the new value with itself.
A crafted BGP UPDATE with a malformed path attribute length field causes
bgpd to dump up to 65535 bytes of application memory and send it as the
data field in a BGP NOTIFY message, which is truncated to 4075 bytes
after accounting for protocol headers. After reading a malformed length
field, a NOTIFY is generated that is supposed to contain the problematic
data, but the malformed length field is inadvertently used to compute
how much data we send.
CVE-2017-15865
Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
When displaying the config, bgpd only checked for the existance of a peer-group prefix-list before
deciding to not display the outbound prefix-list. This commit updates the outbound prefix-list
logic to match the inbound.
- /etc/frr/daemon is a config file and won't be replaced, do quick sed fix
- Updated changelog
Signed-off-by: Martin Winter <mwinter@opensourcerouting.org>
* Fixes issue where daemon default config tried to use /etc/init.d/frr script which doesn't exist on systemd systems
Signed-off-by: Martin Winter <mwinter@opensourcerouting.org>
- FPM is a module since 3.0. Always build it and allow user choice to enable or disable it
Signed-off-by: Martin Winter <mwinter@opensourcerouting.org>
- Flex is too old on these releases and misses some prototypes in the generated code. Removing the
werror allows to build the package anyway
Signed-off-by: Martin Winter <mwinter@opensourcerouting.org>
Because the lintian warning no longer matched exactly due to removal
of unused protobuf libraries from the build, the warning wasn't
masked. Update it to match the current warning string.
Signed-off-by: Silas McCroskey <smccroskey@cumulusnetworks.com>
Testing done: built and installed for all ubuntu targets
Socket-based services such as syslog need not be specified as
dependencies in service files, and doing so may slow down boot by
reducing parallelism. All known supported systemd-based platforms
have syslog as a socket-based service.
Clears the following lintian warnings:
W: frr: systemd-service-file-refers-to-obsolete-target lib/systemd/system/frr.service syslog.target
Signed-off-by: Silas McCroskey <smccroskey@cumulusnetworks.com>
Testing done: built and installed for all ubuntu targets
These library targets should not be built if protobuf support is
disabled, as that is their only functionality.
Clears the following lintian warnings:
W: frr: non-dev-pkg-with-shlib-symlink usr/lib/libfrr_pb.so.0.0.0 usr/lib/libfrr_pb.so
W: frr: non-dev-pkg-with-shlib-symlink usr/lib/libfrrfpm_pb.so.0.0.0 usr/lib/libfrrfpm_pb.so
W: frr-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libfrr_pb.so.0.0.0
W: frr-dbg: debug-file-with-no-debug-symbols usr/lib/debug/usr/lib/libfrrfpm_pb.so.0.0.0
Signed-off-by: Silas McCroskey <smccroskey@cumulusnetworks.com>
Testing done: built and installed on all ubuntu
Fix was applied elsewhere but didn't make it into this file.
Clears the following lintian warning:
W: frr-dbg: description too long
Signed-off-by: Silas McCroskey <smccroskey@cumulusnetworks.com>
Testing done: built and installed on all ubuntu
Debconf was in use by this packaging a long time ago, and references to it
were never fully cleaned up when the one question it asked was deleted.
Clears the following lintian warning:
W: frr: no-debconf-templates
Signed-off-by: Silas McCroskey <smccroskey@cumulusnetworks.com>
Testing done: built in sbuild with lintian enabled
verified frr-reload.py still in frr-pythontools
Clean up issues missed when moving the script into a separate package.
Clears the following lintian warning:
E: frr: python-script-but-no-python-dep usr/lib/frr/frr-reload.py
Signed-off-by: Silas McCroskey <smccroskey@cumulusnetworks.com>
