From f5ba86dfa5e1dac10144b236ec370860fc69ab65 Mon Sep 17 00:00:00 2001 From: Job Snijders Date: Tue, 31 Dec 2019 13:29:05 +0100 Subject: [PATCH] Change prompt in docs --- README.md | 16 ++++++++-------- bgpq4.8 | 14 +++++++------- 2 files changed, 15 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 161523c..0354f2c 100644 --- a/README.md +++ b/README.md @@ -167,7 +167,7 @@ EXAMPLES -------- Generating prefix filter for MikroTik for `AS20597`: - user@host:~>./bgpq4 -Kl eltel-v4 AS20597 + $ ./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.32.0/20 /routing filter add action=accept chain="eltel-v4" prefix=81.9.96.0/20 @@ -181,7 +181,7 @@ Generating prefix filter for MikroTik for `AS20597`: Generating named Juniper prefix-filter for `AS20597`: - user@host:~>bgpq4 -Jl eltel-v4 AS20597 + $ bgpq4 -Jl eltel-v4 AS20597 policy-options { replace: prefix-list eltel-v4 { @@ -204,7 +204,7 @@ Generating named Juniper prefix-filter for `AS20597`: For Cisco we can use aggregation (-A) flag to make this prefix-filter more compact: - user@host:~>bgpq4 -Al eltel-v4 AS20597 + $ bgpq4 -Al eltel-v4 AS20597 no ip prefix-list eltel-v4 ip prefix-list eltel-v4 permit 81.9.0.0/20 ip prefix-list eltel-v4 permit 81.9.32.0/20 @@ -227,7 +227,7 @@ Well, for Juniper we can generate even more interesting policy-statement, using `-M `, `-r `, `-R ` and hierarchical names: - user@host:~>bgpq4 -AJEl eltel/specifics -r 29 -R 32 -M "community blackhole" AS20597 + $ bgpq4 -AJEl eltel/specifics -r 29 -R 32 -M "community blackhole" AS20597 policy-options { policy-statement eltel { term specifics { @@ -255,7 +255,7 @@ generated policy-option term now allows more-specific routes in range Of course, `bgpq4` supports IPv6 (-6): - user@host:~>bgpq4 -6l as-retn-v6 AS-RETN6 + $ bgpq4 -6l as-retn-v6 AS-RETN6 no ipv6 prefix-list as-retn-v6 ipv6 prefix-list as-retn-v6 permit 2001:7fb:fe00::/48 ipv6 prefix-list as-retn-v6 permit 2001:7fb:fe01::/48 @@ -263,7 +263,7 @@ Of course, `bgpq4` supports IPv6 (-6): and assumes your device supports 32-bit ASNs - user@host:~>bgpq4 -Jf 112 AS-SPACENET + $ bgpq4 -Jf 112 AS-SPACENET policy-options { replace: as-path-group NN { @@ -283,7 +283,7 @@ If you want to generate configuration not for routers, but for some other programs/systems, you may use user-defined formatting, like in example below: - user@host:~>bgpq4 -F "ipfw add pass all from %n/%l to any\\n" as3254 + $ bgpq4 -F "ipfw add pass all from %n/%l to any\\n" as3254 ipfw add pass all from 62.244.0.0/18 to any ipfw add pass all from 91.219.29.0/24 to any ipfw add pass all from 91.219.30.0/24 to any @@ -296,7 +296,7 @@ Please note that no new lines inserted automatically after each sentence, you have to add them into format string manually, elsewhere output will be in one line (sometimes it makes sense): - user@host:~>bgpq4 -6F "%n/%l; " as-eltel + $ bgpq4 -6F "%n/%l; " as-eltel 2001:1b00::/32; 2620:4f:8000::/48; 2a04:bac0::/29; 2a05:3a80::/48; DIAGNOSTICS diff --git a/bgpq4.8 b/bgpq4.8 index 29a8b07..f54ae0d 100644 --- a/bgpq4.8 +++ b/bgpq4.8 @@ -135,7 +135,7 @@ those objects will be excluded from expansion. Generating named juniper prefix-filter for AS20597: .nf .RS -~>bgpq4 -Jl eltel AS20597 +$ bgpq4 -Jl eltel AS20597 policy-options { replace: prefix-list eltel { @@ -161,7 +161,7 @@ For Cisco we can use aggregation (-A) flag to make this prefix-filter more compact: .nf .RS -~>bgpq4 -Al eltel AS20597 +$ 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 @@ -183,7 +183,7 @@ Well, for Juniper we can generate even more interesting policy-options, using -M , -R and hierarchical names: .nf .RS -~>bgpq4 -AJEl eltel/specifics -r 29 -R 32 -M "community blackhole" AS20597 +$ bgpq4 -AJEl eltel/specifics -r 29 -R 32 -M "community blackhole" AS20597 policy-options { policy-statement eltel { term specifics { @@ -212,7 +212,7 @@ blackhole (defined elsewhere in configuration). Of course, this version supports IPv6 (-6): .nf .RS -~>bgpq4 -6l as-retn-6 AS-RETN6 +$ 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 @@ -222,7 +222,7 @@ ipv6 prefix-list as-retn-6 permit 2001:7fb:fe01::/48 and assumes your device supports 32-bit ASNs .nf .RS -~>bgpq4 -Jf 112 AS-SPACENET +$ bgpq4 -Jf 112 AS-SPACENET policy-options { replace: as-path-group NN { @@ -242,7 +242,7 @@ other programs/systems, you may use user-defined formatting, like in example below: .nf .RS -user@host:~>bgpq4 -F "ipfw add pass all from %n/%l to any\\n" as3254 +$ bgpq4 -F "ipfw add pass all from %n/%l to any\\n" as3254 ipfw add pass all from 62.244.0.0/18 to any ipfw add pass all from 91.219.29.0/24 to any ipfw add pass all from 91.219.30.0/24 to any @@ -258,7 +258,7 @@ you have to add them into format string manually, elsewhere output will be in one line (sometimes it makes sense): .nf .RS -user@host:~>bgpq4 -6F "%n/%l; " as-eltel +$ bgpq4 -6F "%n/%l; " as-eltel 2001:1b00::/32; 2620:4f:8000::/48; 2a04:bac0::/29; 2a05:3a80::/48; .RE .fi