v1.14.1
-
Fix: import limit is not set if PeeringDB records are not found.
For clients not configured with a specific max-prefix value, when a PeeringDB record was not found the value from the general limit was not used to build the import limit configuration. The tool was expected to fallback to the
general_limit_ipv4
value instead.See also GitHub issue #105 105