File | Date | Author | Commit |
---|---|---|---|
bgpd | 2013-06-12 | Aaron Hebert | [abd81a] clean up |
cli | 2013-06-12 | Aaron Hebert | [e9a415] clean up |
.gitignore | 2013-02-18 | Aaron Hebert | [905dc8] Initial commit |
LICENSE | 2013-04-10 | aaron | [1753b1] License |
README.md | 2013-06-04 | Aaron Hebert | [adf1df] various improvements. valgrind checked at 0/0 |
Flowlab BGP looking-glass allows the collection of the (IPv4/IPv6)Internet
routing table which may be viewed by service providers and/or ISP customers to validate
IP routing across autonomous systems.
Routing updates may also have attributes aliased to become (graph) readable. This function
exists to allow the exporting of RIB updates to splunk, or any such data collector.
Being that this project is still very new and under development (now 1-alpha), I
will try to keep the wiki as up to date as possible.
Looking glasses are generally used to validate BGP attributes when advertising
IP prefixes to the Internet. A beneficial side-effect is the tracking of BGP
updates/events local or remote(upstream). To analyze events, splunk is supported,
along with MySQL.
Custom graphs can be easily implemented if taken the time to do so. There's
certainly no need to rely on splunk if one developed another way of displaying
data. flowlab_bgp_lg is meant to be nothing more than a route collector, and
it's interface is solely CLI(command line interface). This project does not have
graph data "out of the box".
Command Line Interface (cli): Provides the shell interface in to configuring the daemons. This shell does not provide telnetd or ssh like features, but instead relies on the host OS to perform all functions pertaining to user access.
Border Gateway Protocol Daemon (bgpd): Serves as a fast and light weight BGP route collector.
Tested with live IPv4 routing table without major issues.
This project is currently in version 1. Most functionality is available,
but there are many improvements needed as things are refined/revised.
See issues for updates on
what is currently being worked on.
If you wish to contribute, please contact aaron.hebert@gmail.com stating which
area you feel you can contribute to.