Re: new BGP hijack & visibility tool “BGPalerter”

Wed Aug 14 17:13:47 UTC 2019

Hi,

You can build it yourself, see
https://github.com/nttgin/BGPalerter#more-information-for-developers

I think that the binaries are here for thoses that don’t want to install
all the build-chain.

-- 
Alarig

On 14/08/2019 19:06, Ryan Hamel wrote:
> Job,
>
> I appreciate the effort and the intent behind this project, but why
> should the community contribute to an open source project on GitHub
> that is mainly powered by a closed source binary?
>
> Ryan
>
> On Wed, Aug 14, 2019, 10:55 AM Job Snijders <job at ntt.net
> <mailto:job at ntt.net>> wrote:
>
>     Dear NANOG,
>
>     Recently NTT investigated how to best monitor the visibility of
>     our own and our subsidiaries’ IP resources in the BGP Default-Free
>     Zone. We were specifically looking how to get near real-time
>     alerts funneled into an actionable pipeline for our NOC &
>     Operations department when BGP hijacks happen.
>
>     Previously we relied on a commercial “BGP Monitoring as a Service”
>     offering, but with the advent of RIPE NCC’s “RIS Live” streaming
>     API [1] we saw greater potential for a self-hosted approach
>     designed specifically for custom integrations with various
>     business processes. We decided to write our own tool “BGPalerter”
>     and share the source code with the Internet community.
>
>     BGPalerter allows operators to specify in great detail how to
>     distribute meaningful information from the firehose from various
>     BGP data sources (we call them “connectors”), through data
>     processors (called “monitors”), finally outputted through
>     “reports” into whatever mechanism is appropriate (Slack, IRC,
>     email, or a call to your ticketing system’s API). 
>
>     The source code is available on Github, under a liberal open
>     source license to foster community collaboration:
>
>         https://github.com/nttgin/BGPalerter 
>
>     If you wish to contribute to the project, please use Github’s
>     “issues” or “pull request” features. Any help is welcome! We’d
>     love suggestions for new features, updates to the documentation,
>     help with setting up a CI regression testing pipeline, or
>     packaging for common platforms.
>
>     Kind regards,
>
>     Job & Massimo
>     NTT Ltd
>
>     [1]: https://ris-live.ripe.net/
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190814/046ee136/attachment.html>