mirrors/bgpq4
1
0
Fork 0
mirror of https://github.com/bgp/bgpq4 synced 2025-02-28 08:53:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #9 from stucchimax/master

Browse Source 
Make the examples more consistent, making use of -v4 and -v6 suffixes
This commit is contained in:
Job Snijders
2019-12-16 16:04:59 +01:00
committed by GitHub
parent 4fa8c504dd 40733b19ee
commit 2abddb85d4
1 changed files with 32 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
README.md
View File

@@ -180,24 +180,24 @@ EXAMPLES
-------- --------
Generating prefix filter for MikroTik for `AS20597`: Generating prefix filter for MikroTik for `AS20597`:
user@host:~>./bgpq4 -Kl eltel AS20597 user@host:~>./bgpq4 -Kl eltel-v4 AS20597
/routing filter add action=accept chain="eltel-V4" prefix=81.9.0.0/20 /routing filter add action=accept chain="eltel-v4" prefix=81.9.0.0/20
/routing filter add action=accept chain="eltel-V4" prefix=81.9.32.0/20 /routing filter add action=accept chain="eltel-v4" prefix=81.9.32.0/20
/routing filter add action=accept chain="eltel-V4" prefix=81.9.96.0/20 /routing filter add action=accept chain="eltel-v4" prefix=81.9.96.0/20
/routing filter add action=accept chain="eltel-V4" prefix=81.222.128.0/20 /routing filter add action=accept chain="eltel-v4" prefix=81.222.128.0/20
/routing filter add action=accept chain="eltel-V4" prefix=81.222.160.0/20 /routing filter add action=accept chain="eltel-v4" prefix=81.222.160.0/20
/routing filter add action=accept chain="eltel-V4" prefix=81.222.192.0/18 /routing filter add action=accept chain="eltel-v4" prefix=81.222.192.0/18
/routing filter add action=accept chain="eltel-V4" prefix=85.249.8.0/21 /routing filter add action=accept chain="eltel-v4" prefix=85.249.8.0/21
/routing filter add action=accept chain="eltel-V4" prefix=85.249.224.0/19 /routing filter add action=accept chain="eltel-v4" prefix=85.249.224.0/19
/routing filter add action=accept chain="eltel-V4" prefix=89.112.0.0/17 /routing filter add action=accept chain="eltel-v4" prefix=89.112.0.0/17
/routing filter add action=accept chain="eltel-V4" prefix=217.170.64.0/19 /routing filter add action=accept chain="eltel-v4" prefix=217.170.64.0/19
Generating named Juniper prefix-filter for `AS20597`: Generating named Juniper prefix-filter for `AS20597`:
user@host:~>bgpq4 -Jl eltel AS20597 user@host:~>bgpq4 -Jl eltel-v4 AS20597
policy-options { policy-options {
replace: replace:
prefix-list eltel { prefix-list eltel-v4 {
81.9.0.0/20; 81.9.0.0/20;
81.9.32.0/20; 81.9.32.0/20;
81.9.96.0/20; 81.9.96.0/20;
@@ -217,19 +217,19 @@ Generating named Juniper prefix-filter for `AS20597`:
For Cisco we can use aggregation (-A) flag to make this prefix-filter For Cisco we can use aggregation (-A) flag to make this prefix-filter
more compact: more compact:
user@host:~>bgpq4 -Al eltel AS20597 user@host:~>bgpq4 -Al eltel-v4 AS20597
no ip prefix-list eltel no ip prefix-list eltel-v4
ip prefix-list eltel permit 81.9.0.0/20 ip prefix-list eltel-v4 permit 81.9.0.0/20
ip prefix-list eltel permit 81.9.32.0/20 ip prefix-list eltel-v4 permit 81.9.32.0/20
ip prefix-list eltel permit 81.9.96.0/20 ip prefix-list eltel-v4 permit 81.9.96.0/20
ip prefix-list eltel permit 81.222.128.0/20 ip prefix-list eltel-v4 permit 81.222.128.0/20
ip prefix-list eltel permit 81.222.192.0/18 ip prefix-list eltel-v4 permit 81.222.192.0/18
ip prefix-list eltel permit 85.249.8.0/21 ip prefix-list eltel-v4 permit 85.249.8.0/21
ip prefix-list eltel permit 85.249.224.0/19 ip prefix-list eltel-v4 permit 85.249.224.0/19
ip prefix-list eltel permit 89.112.0.0/18 ge 19 le 19 ip prefix-list eltel-v4 permit 89.112.0.0/18 ge 19 le 19
ip prefix-list eltel permit 89.112.4.0/22 ip prefix-list eltel-v4 permit 89.112.4.0/22
ip prefix-list eltel permit 89.112.64.0/19 ip prefix-list eltel-v4 permit 89.112.64.0/19
ip prefix-list eltel permit 217.170.64.0/19 ge 20 le 20 ip prefix-list eltel-v4 permit 217.170.64.0/19 ge 20 le 20
and, as you see, prefixes `89.112.0.0/19` and `89.112.32.0/19` now aggregated and, as you see, prefixes `89.112.0.0/19` and `89.112.32.0/19` now aggregated
into single entry into single entry
@@ -268,10 +268,10 @@ generated policy-option term now allows more-specific routes in range
Of course, `bgpq4` supports IPv6 (-6): Of course, `bgpq4` supports IPv6 (-6):
user@host:~>bgpq4 -6l as-retn-6 AS-RETN6 user@host:~>bgpq4 -6l as-retn-v6 AS-RETN6
no ipv6 prefix-list as-retn-6 no ipv6 prefix-list as-retn-v6
ipv6 prefix-list as-retn-6 permit 2001:7fb:fe00::/48 ipv6 prefix-list as-retn-v6 permit 2001:7fb:fe00::/48
ipv6 prefix-list as-retn-6 permit 2001:7fb:fe01::/48 ipv6 prefix-list as-retn-v6 permit 2001:7fb:fe01::/48
[....] [....]
and ASN32 and ASN32
@@ -391,8 +391,8 @@ SEE ALSO
AUTHORS AUTHORS
------- -------
Job Snijders [job@ntt.net](mailto:job@ntt.net) - Job Snijders [job@ntt.net](mailto:job@ntt.net)
Alexandre Snarskii [snar@snar.spb.ru](mailto:snar@snar.spb.ru) - Alexandre Snarskii [snar@snar.spb.ru](mailto:snar@snar.spb.ru)
Program Homepage Program Homepage
---------------- ----------------