035fd5fdecb7bf93895e3a00c8e7aed1b50cc1ef
howto/mikrotik/ptp32.md
| ... | ... | @@ -1,3 +1,5 @@ |
| 1 | +# How to setup Mikrotik with point-to-point /32 address on interfaces |
|
| 2 | + |
|
| 1 | 3 | ## RouterOS issues |
| 2 | 4 | |
| 3 | 5 | * RouterOS doesn't have direct Point-to-Point addresses. |
| ... | ... | @@ -5,7 +7,7 @@ |
| 5 | 7 | |
| 6 | 8 | The long explanation about how mikrotik resolves recursive routes is documentated at [Mikrotik's page](https://wiki.mikrotik.com/wiki/Manual:IP/Route#Nexthop_lookup). |
| 7 | 9 | |
| 8 | -How can we workaround these issues? Simple. We setup a /32 on the Point-to-Point interface, we setup a direct route to our to other peer (using the interface as next-hop for this route) and use bgp filters to change the next-hop interface. |
|
| 10 | +How can we workaround these issues? Simple. We setup a /32 on the Point-to-Point interface, we setup a direct route to the other peer (using the interface as next-hop for this route) and use bgp filters to change the next-hop interface. |
|
| 9 | 11 | |
| 10 | 12 | ## Legend |
| 11 | 13 | |
| ... | ... | @@ -14,7 +16,7 @@ How can we workaround these issues? Simple. We setup a /32 on the Point-to-Point |
| 14 | 16 | * gre-dn42-peer -> This is the name of the interface |
| 15 | 17 | * 1.1.1.1 - peer external IP |
| 16 | 18 | * 2.2.2.2 - your external IP |
| 17 | - * bgp-dn42-peer-in -> This is the name of the chain filter. You should use a different chain per point to point link |
|
| 19 | + * bgp-dn42-peer-in -> This is the name of the chain filter. You need to use a different chain per point to point link |
|
| 18 | 20 | |
| 19 | 21 | ## Setup |
| 20 | 22 |