103bc28a4b9377641e4b6bff7acbae5a02f816ca
howto/OpenBGPD.md
... | ... | @@ -5,14 +5,14 @@ The [portable version](https://openbgpd.org/ftp.html) should run with little to |
5 | 5 | Only IPv6 is used for the sake of simplicity. |
6 | 6 | Neighbors use ULA addresses (/127 transfer net) assigned from one of the peer's allocation. |
7 | 7 | |
8 | -The goal is to have a small, yet complete setup for all peers with ROA validation and other safety measurements in place. |
|
8 | +The goal is to have a small, yet complete setup for all peers with ROA validation and other safety measures in place. |
|
9 | 9 | |
10 | 10 | # Configuration |
11 | 11 | [`/etc/bgpd.conf`](https://man.openbsd.org/bgpd.conf.5) contains all information and may include further (automatically generated) files, as is done in this guide. |
12 | 12 | |
13 | 13 | As per the manual, configuration is divided into logical sections; [`/etc/examples/bgpd.conf`](http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/etc/examples/bgpd.conf?rev=HEAD&content-type=text/plain&only_with_tag=MAIN) is a complete and commented example which this guide is roughly based on. |
14 | 14 | |
15 | -By default, [bgpd(8)](http://man.openbsd.org/bgpd.8) listens on all local addresses (on the current default [`routing domain`](http://man.openbsd.org/rdomain.4)), but this guide explicitly listens on the configured transfer ULA only for each peer to better illustrate of this setup. |
|
15 | +By default, [bgpd(8)](http://man.openbsd.org/bgpd.8) listens on all local addresses (on the current default [`routing domain`](http://man.openbsd.org/rdomain.4)), but this guide explicitly listens on the configured transfer ULA only for each peer to better illustrate this setup. |
|
16 | 16 | |
17 | 17 | ## local host |
18 | 18 | Information such as ASN, router ID and allocated networks are required: |
... | ... | @@ -57,7 +57,7 @@ neighbor $A_remote { |
57 | 57 | |
58 | 58 | ## filter rules |
59 | 59 | **bgpd** blocks all BGP __UPDATE__ messages by default. |
60 | -The filter rules are evaluated in sequential order, form first to last. |
|
60 | +The filter rules are evaluated in sequential order, from first to last. |
|
61 | 61 | The last matching allow or deny rule decides what action is taken. |
62 | 62 | |
63 | 63 | Start off with basic protection and sanity rules: |
... | ... | @@ -101,7 +101,7 @@ match from any community GRACEFUL_SHUTDOWN set { localpref 0 } |
101 | 101 | |
102 | 102 | # ROA |
103 | 103 | |
104 | -An roa-set can be generated from the registry directly or you can use the following pre-build tables. |
|
104 | +An roa-set can be generated from the registry directly or you can use the following pre-built tables. |
|
105 | 105 | |
106 | 106 | One single `roa-set` may be defined, against which **bgpd** will validate the origin of each prefix; this allows filter rules to use the `ovs` keyword as demonstrated above. |
107 | 107 |