diff options
| -rwxr-xr-x | doc/ucis.ano/bgp_graph/readme.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ucis.ano/bgp_graph/readme.txt b/doc/ucis.ano/bgp_graph/readme.txt index 75387da..b32c52f 100755 --- a/doc/ucis.ano/bgp_graph/readme.txt +++ b/doc/ucis.ano/bgp_graph/readme.txt @@ -3,7 +3,7 @@ These scripts can be used to graph the BGP peering connections in a network usin Some of the scripts will communicate with the BGP software, another script can be used to export the obtained information to a .dot file, which can then be converted to a graph file using graphviz. The scripts can run on different machines, and it is recommended to use routing information from multiple routes, to obtain an accurate view of the network.
Depending on the BGP software, one of the following scripts must be used to acquire the data:
-- bgp_path_list_birg.sh (or .php) for the bird routing daemon
+- bgp_path_list_bird.sh (or .php) for the bird routing daemon
- bgp_path_list_quagga.sh (or .php) for the quagga/zebra routing daemon
- bgp_path_list_xml.php to convert existing dn42/diac42 .xml data
@@ -43,4 +43,4 @@ client$ nc remotehost 9876 | ./path_list_to_dot.php < /tmp/paths.txt | dot -T pn You can also use inetd/xinetd on the server side for a more permanent solution.
-Be creative!
\ No newline at end of file +Be creative!
|