mirror of
https://github.com/bgp/bgpq4
synced 2025-02-28 08:53:11 +00:00
Remove generated .html file from repository.
This commit is contained in:
Roelf Wichertjes
1
.gitignore
vendored
1
.gitignore
vendored
@@ -3,6 +3,7 @@ Makefile
|
||||
config.h
|
||||
*.o
|
||||
bgpq4
|
||||
bgpq4.html
|
||||
Makefile.in
|
||||
.deps
|
||||
/ar-lib
|
||||
|
||||
12
Makefile.am
12
Makefile.am
@@ -12,10 +12,10 @@ bgpq4.html: readme.header README.md
|
||||
cat readme.header README.md | @MARKDOWN@ > bgpq4.html
|
||||
|
||||
clean-local:
|
||||
@rm config.status configure config.log
|
||||
@rm Makefile
|
||||
@rm -r autom4te.cache/
|
||||
@rm aclocal.m4
|
||||
@rm compile install-sh missing Makefile.in depcomp stamp-h1
|
||||
@rm config.h config.h.in
|
||||
-rm config.status configure config.log
|
||||
-rm Makefile
|
||||
-rm -r autom4te.cache/
|
||||
-rm aclocal.m4
|
||||
-rm compile install-sh missing Makefile.in depcomp stamp-h1
|
||||
-rm config.h config.h.in
|
||||
|
||||
|
||||
296
bgpq4.html
296
bgpq4.html
@@ -1,296 +0,0 @@
|
||||
<p><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.or
|
||||
g/TR/html4/loose.dtd"> <br />
|
||||
<html><head><style type='text/css'>
|
||||
h1 { color: #3c78b5; border-bottom: 3px solid #3c78b5; font-size: 180%; }
|
||||
h2 { color: #3c78b5; border-bottom: 2px solid #3c78b5; font-size: 140%; }
|
||||
h3 { color: #3c78b5; border-bottom: 1px dotted #3c78b5; font-size: 129%; }
|
||||
em { color: #0000FF; }
|
||||
code { font-size:12px; background-color:#f8f8ff; border:1px; }
|
||||
pre { border: 1px dotted #3c78b5; background-color: #f8f8ff; margin: 1em 1em;}
|
||||
body { width: 80%; margin: 0 3em; }
|
||||
ul { list-style: none; }
|
||||
</style></head><body> </p>
|
||||
|
||||
<h2>NAME</h2>
|
||||
|
||||
<p><code>bgpq4</code> - bgp filtering automation for Cisco and Juniper routers</p>
|
||||
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><code>
|
||||
bgpq4 [-h host] [-S sources] [-EP] [-f asn | -G asn] [-2346AbDdJjpX] [-r len] [-R len] [-m max] [-W len] OBJECTS [...]
|
||||
</code></p>
|
||||
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p>The bgpq4 utility used to generate Cisco and Juniper prefix-lists,
|
||||
extended access-lists, policy-statement terms and as-path lists based on
|
||||
RADB data.</p>
|
||||
|
||||
<p>The options are as follows:</p>
|
||||
|
||||
<h4>-3</h4>
|
||||
|
||||
<p>Assume that your device is asn32-capable.</p>
|
||||
|
||||
<h4>-4</h4>
|
||||
|
||||
<p>Generate IPv4 prefix/access-lists (default).</p>
|
||||
|
||||
<h4>-6</h4>
|
||||
|
||||
<p>Generate IPv6 prefix/access-lists (IPv4 by default).</p>
|
||||
|
||||
<h4>-A</h4>
|
||||
|
||||
<p>Try to aggregate generated filters as much as possible (not all output formats
|
||||
supported).</p>
|
||||
|
||||
<h4>-b</h4>
|
||||
|
||||
<p>Generate output in BIRD format (default: Cisco).</p>
|
||||
|
||||
<h4>-d</h4>
|
||||
|
||||
<p>Enable some debugging output.</p>
|
||||
|
||||
<h4>-E</h4>
|
||||
|
||||
<p>Generate extended access-list (Cisco) or policy-statement term using
|
||||
route-filters (Juniper).</p>
|
||||
|
||||
<h4>-f <code>AS number</code></h4>
|
||||
|
||||
<p>Generate input as-path access-list for adjacent as <code>AS number</code>.</p>
|
||||
|
||||
<h4>-G <code>number</code></h4>
|
||||
|
||||
<p>Generate output as-path access-list.</p>
|
||||
|
||||
<h4>-h <code>host</code></h4>
|
||||
|
||||
<p>Host running IRRD database (default: <code>rr.ntt.net</code>).</p>
|
||||
|
||||
<h4>-J</h4>
|
||||
|
||||
<p>Generate config for Juniper (default: Cisco).</p>
|
||||
|
||||
<h4>-j</h4>
|
||||
|
||||
<p>Generate output in JSON format (default: Cisco).</p>
|
||||
|
||||
<h4>-m <code>length</code></h4>
|
||||
|
||||
<p>Maximum length of accepted prefixes (default: <code>32</code> for IPv4, <code>128</code> for IPv6).</p>
|
||||
|
||||
<h4>-M <code>match</code></h4>
|
||||
|
||||
<p>Extra match conditions for Juniper route-filters. See the examples section.</p>
|
||||
|
||||
<h4>-l <code>name</code></h4>
|
||||
|
||||
<p><code>Name</code> of generated configuration stanza.</p>
|
||||
|
||||
<h4>-p</h4>
|
||||
|
||||
<p>Enable use of private ASNs and ASNs used for documentation purpose only
|
||||
(default: disabled).</p>
|
||||
|
||||
<h4>-P</h4>
|
||||
|
||||
<p>Generate prefix-list (default behaviour, flag added for backward compatibility
|
||||
only).</p>
|
||||
|
||||
<h4>-r <code>length</code></h4>
|
||||
|
||||
<p>Allow more-specific routes with masklen starting with specified length.</p>
|
||||
|
||||
<h4>-R <code>length</code></h4>
|
||||
|
||||
<p>Allow more-specific routes up to specified masklen too. (Please, note: objects
|
||||
with prefix-length greater than specified length will be always allowed.)</p>
|
||||
|
||||
<h4>-S <code>sources</code></h4>
|
||||
|
||||
<p>Use specified sources only (default: RADB,RIPE,APNIC).</p>
|
||||
|
||||
<h4>-T</h4>
|
||||
|
||||
<p>Disable pipelining. (not recommended)</p>
|
||||
|
||||
<h4>-W <code>length</code></h4>
|
||||
|
||||
<p>Generate as-path strings of a given length maximum (0 for infinity).</p>
|
||||
|
||||
<h4>-X</h4>
|
||||
|
||||
<p>Generate config for Cisco IOS XR devices (plain IOS by default).</p>
|
||||
|
||||
<h4><code>OBJECTS</code></h4>
|
||||
|
||||
<p><code>OBJECTS</code> means networks (in prefix format), autonomous systems, as-sets and
|
||||
route-sets. If multiple objects are specified they will be merged.</p>
|
||||
|
||||
<h2>EXAMPLES</h2>
|
||||
|
||||
<p>Generating named Juniper prefix-filter for <code>AS20597</code>:</p>
|
||||
|
||||
<pre><code> user@host:~>bgpq4 -Jl eltel AS20597
|
||||
policy-options {
|
||||
replace:
|
||||
prefix-list eltel {
|
||||
81.9.0.0/20;
|
||||
81.9.32.0/20;
|
||||
81.9.96.0/20;
|
||||
81.222.128.0/20;
|
||||
81.222.192.0/18;
|
||||
85.249.8.0/21;
|
||||
85.249.224.0/19;
|
||||
89.112.0.0/19;
|
||||
89.112.4.0/22;
|
||||
89.112.32.0/19;
|
||||
89.112.64.0/19;
|
||||
217.170.64.0/20;
|
||||
217.170.80.0/20;
|
||||
}
|
||||
}
|
||||
</code></pre>
|
||||
|
||||
<p>For Cisco we can use aggregation (-A) flag to make this prefix-filter
|
||||
more compact:</p>
|
||||
|
||||
<pre><code> user@host:~>bgpq4 -Al eltel AS20597
|
||||
no ip prefix-list eltel
|
||||
ip prefix-list eltel permit 81.9.0.0/20
|
||||
ip prefix-list eltel permit 81.9.32.0/20
|
||||
ip prefix-list eltel permit 81.9.96.0/20
|
||||
ip prefix-list eltel permit 81.222.128.0/20
|
||||
ip prefix-list eltel permit 81.222.192.0/18
|
||||
ip prefix-list eltel permit 85.249.8.0/21
|
||||
ip prefix-list eltel permit 85.249.224.0/19
|
||||
ip prefix-list eltel permit 89.112.0.0/18 ge 19 le 19
|
||||
ip prefix-list eltel permit 89.112.4.0/22
|
||||
ip prefix-list eltel permit 89.112.64.0/19
|
||||
ip prefix-list eltel permit 217.170.64.0/19 ge 20 le 20
|
||||
</code></pre>
|
||||
|
||||
<p>and, as you see, prefixes <code>89.112.0.0/19</code> and <code>89.112.32.0/19</code> now aggregated
|
||||
into single entry </p>
|
||||
|
||||
<pre><code>ip prefix-list eltel permit 89.112.0.0/18 ge 19 le 19.
|
||||
</code></pre>
|
||||
|
||||
<p>Well, for Juniper we can generate even more interesting policy-statement,
|
||||
using <code>-M <extra match conditions></code>, <code>-r <len></code>, <code>-R <len></code> and hierarchical
|
||||
names:</p>
|
||||
|
||||
<pre><code> user@host:~>bgpq4 -AJEl eltel/specifics -r 29 -R 32 -M "community blackhole" AS20597
|
||||
policy-options {
|
||||
policy-statement eltel {
|
||||
term specifics {
|
||||
replace:
|
||||
from {
|
||||
community blackhole;
|
||||
route-filter 81.9.0.0/20 prefix-length-range /29-/32;
|
||||
route-filter 81.9.32.0/20 prefix-length-range /29-/32;
|
||||
route-filter 81.9.96.0/20 prefix-length-range /29-/32;
|
||||
route-filter 81.222.128.0/20 prefix-length-range /29-/32;
|
||||
route-filter 81.222.192.0/18 prefix-length-range /29-/32;
|
||||
route-filter 85.249.8.0/21 prefix-length-range /29-/32;
|
||||
route-filter 85.249.224.0/19 prefix-length-range /29-/32;
|
||||
route-filter 89.112.0.0/17 prefix-length-range /29-/32;
|
||||
route-filter 217.170.64.0/19 prefix-length-range /29-/32;
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
</code></pre>
|
||||
|
||||
<p>generated policy-option term now allows more-specific routes in range
|
||||
/29 - /32 for eltel networks if they marked with community 'blackhole'
|
||||
(defined elsewhere in configuration).</p>
|
||||
|
||||
<p>Of course, <code>bgpq4</code> supports IPv6 (-6):</p>
|
||||
|
||||
<pre><code> user@host:~>bgpq4 -6l as-retn-6 AS-RETN6
|
||||
no ipv6 prefix-list as-retn-6
|
||||
ipv6 prefix-list as-retn-6 permit 2001:7fb:fe00::/48
|
||||
ipv6 prefix-list as-retn-6 permit 2001:7fb:fe01::/48
|
||||
[....]
|
||||
</code></pre>
|
||||
|
||||
<p>and ASN32</p>
|
||||
|
||||
<pre><code> user@host:~>bgpq4 -J3f 112 AS-SPACENET
|
||||
policy-options {
|
||||
replace:
|
||||
as-path-group NN {
|
||||
as-path a0 "^112(112)*$";
|
||||
as-path a1 "^112(.)*(1898|5539|8495|8763|8878|12136|12931|15909)$";
|
||||
as-path a2 "^112(.)*(21358|23456|23600|24151|25152|31529|34127|34906)$";
|
||||
as-path a3 "^112(.)*(35052|41720|43628|44450|196611)$";
|
||||
}
|
||||
}
|
||||
</code></pre>
|
||||
|
||||
<p>see <code>AS196611</code> in the end of the list ? That's <code>AS3.3</code> in 'asplain' notation.</p>
|
||||
|
||||
<p>If your router does not support ASN32 (yet) you should not use switch -3,
|
||||
and the result will be next:</p>
|
||||
|
||||
<pre><code> user@host:~>bgpq4 -f 112 AS-SPACENET
|
||||
no ip as-path access-list NN
|
||||
ip as-path access-list NN permit ^112( 112)*$
|
||||
ip as-path access-list NN permit ^112( [0-9]+)* (1898|5539|8495|8763)$
|
||||
ip as-path access-list NN permit ^112( [0-9]+)* (8878|12136|12931|15909)$
|
||||
ip as-path access-list NN permit ^112( [0-9]+)* (21358|23456|23600|24151)$
|
||||
ip as-path access-list NN permit ^112( [0-9]+)* (25152|31529|34127|34906)$
|
||||
ip as-path access-list NN permit ^112( [0-9]+)* (35052|41720|43628|44450)$
|
||||
</code></pre>
|
||||
|
||||
<p><code>AS196611</code> is no more in the list, however, <code>AS23456</code> (transition AS) would
|
||||
have been added to list if it were not present.</p>
|
||||
|
||||
<h2>DIAGNOSTICS</h2>
|
||||
|
||||
<p>When everything is OK, <code>bgpq4</code> generates result to standard output and
|
||||
exits with status == 0. In case of errors they are printed to stderr and
|
||||
program exits with non-zero status.</p>
|
||||
|
||||
<h2>NOTES ON ULTRA-LARGE PREFIX-LISTS</h2>
|
||||
|
||||
<p>To improve <code>bgpq4</code> performance when expanding extra-large AS-SETs you
|
||||
shall tune OS settings to enlarge TCP send buffer.</p>
|
||||
|
||||
<p>FreeBSD can be tuned in the following way:</p>
|
||||
|
||||
<pre><code>sysctl -w net.inet.tcp.sendbuf_max=2097152
|
||||
</code></pre>
|
||||
|
||||
<p>Linux can be tuned in the following way:</p>
|
||||
|
||||
<pre><code>sysctl -w net.ipv4.tcp_window_scaling=1
|
||||
sysctl -w net.core.rmem_max=2097152
|
||||
sysctl -w net.core.wmem_max=2097152
|
||||
sysctl -w net.ipv4.tcp_rmem="4096 87380 2097152"
|
||||
sysctl -w net.ipv4.tcp_wmem="4096 65536 2097152"
|
||||
</code></pre>
|
||||
|
||||
<p>Please note that generated prefix-lists may not fit your router's
|
||||
limitations. For example, JunOS supports only 85,325 prefixes in
|
||||
each prefix-list <a href="http://www.juniper.net/techpubs/en_US/junos11.4/topics/reference/configuration-statement/prefix-list-edit-policy-options.html">4</a>. </p>
|
||||
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<ol>
|
||||
<li><a href="http://www.radb.net/">Routing Arbiter</a></li>
|
||||
<li><a href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6599/data_sheet_C78-521821.html">Cisco documentation</a>
|
||||
for information on Cisco implementation of ASN32.</li>
|
||||
<li><a href="http://www.juniper.net/techpubs/en_US/junos11.4/topics/reference/configuration-statement/prefix-list-edit-policy-options.html">JunOS prefix-lists limitation</a></li>
|
||||
</ol>
|
||||
|
||||
<h2>AUTHORS</h2>
|
||||
|
||||
<p>Alexandre Snarskii <a href="mailto:snar@snar.spb.ru">snar@snar.spb.ru</a> maintained bgpq3</p>
|
||||
|
||||
<p>Job Snijders <a href="mailto:job@ntt.net">job@ntt.net</a> maintains bgpq4</p>
|
||||
Reference in New Issue
Block a user