All the BGPMon users can be divided into three main groups. Each group will use BGPMon in a defferent level. We organize the user guide into three sections which each section is for a specifc group. So If you are a potential user of BGPMon, the first thing is to find which user group you are in. After that, you can find the most appropriate user guide to read.
Following are the three user groups of BGPmon:
Yes, we support MD5.
BGPmon does not implement the full BGP state machine. Hence there is no way for it to advertise routes to it's peers. It only monitors incoming BGP messages.
If someone peers with instances of bgpmon that Colorado State University maintains, then the routing data that, will be collected from his routers will be publicly available. In case though, someone wants to maintain a private bgpmon cluster or node he can setup Access Control Lists that impose restrictions on who can view the data.
Full tables are generally more useful. For example, a researcher exploring a prefix hijack may want to see if the hijacked route became the preferred route in your network. so we would prefer you send a full table. Most (but not all) of peers send full tables. but some data is better than none at all so if full tables are a policy problem, even the routes originiting from your network can be very valuable.