pkgsrc/net/exabgp/distinfo

$NetBSD: distinfo,v 1.15 2018/03/10 16:32:18 he Exp $

SHA1 (exabgp/3.4.23.tar.gz) = 25523fbc1a1ad3c44ced38f50697f5bca0808a52
RMD160 (exabgp/3.4.23.tar.gz) = 4683067e93884fa1b41edcd13a8b335b09fc8778
SHA512 (exabgp/3.4.23.tar.gz) = 50b8df2d33cb37efe204b709650200d4ec6de5cf1805ee5d0642723b50d6ec86d560795687631ab43069a5c5e85ee5eda89a98e76b58a21e3efa5e3632a84b92
Size (exabgp/3.4.23.tar.gz) = 544183 bytes
Upgrade to ExaBGP version 3.4.23. Upstream changes: Version 3.4.23 * Fix: issue parsing some flowspec routes (backport from master) 2018-03-10 17:32:18 +01:00			$NetBSD: distinfo,v 1.15 2018/03/10 16:32:18 he Exp $
Unlike BIRD or Quagga, ExaBGP was not designed to transform a general purpose server into a router, but to allow engineers to control their BGP (rfc4271) network easily. Think of it as Software Defined Networking for people with "commodity" routers. ExaBGP transform BGP (rfc4271) messages into friendly plain text or JSON which can be easily manipulate by scripts. It allows the creation of tools such as: * advanced looking glass graphically display the routing of prefix * high availability tool which automatically isolate broken services * DDOS mitigation * an anycasted server 2013-12-15 23:22:44 +01:00
Upgrade to ExaBGP version 3.4.23. Upstream changes: Version 3.4.23 * Fix: issue parsing some flowspec routes (backport from master) 2018-03-10 17:32:18 +01:00			`SHA1 (exabgp/3.4.23.tar.gz) = 25523fbc1a1ad3c44ced38f50697f5bca0808a52`
			`RMD160 (exabgp/3.4.23.tar.gz) = 4683067e93884fa1b41edcd13a8b335b09fc8778`
			`SHA512 (exabgp/3.4.23.tar.gz) = 50b8df2d33cb37efe204b709650200d4ec6de5cf1805ee5d0642723b50d6ec86d560795687631ab43069a5c5e85ee5eda89a98e76b58a21e3efa5e3632a84b92`
			`Size (exabgp/3.4.23.tar.gz) = 544183 bytes`