4272a5a9108d43cf80f44b2ac68cd6e27f035b19
howto/SRv6.md
| ... | ... | @@ -2,7 +2,7 @@ |
| 2 | 2 | layout: post_dn42 |
| 3 | 3 | title: "SRv6 for Default Routing Table" |
| 4 | 4 | --- |
| 5 | -In previous [post](howto/DN42-Over-SRv6-L3VPN), I have wrote how did I deploy DN42 over SRv3 L3VPN on my infrastructure, but haven't mention a more popular scenario: SRv6 for traffic looking up default routing table, not everyone want to mess with VRF (it's a trouble for service deployment and eBGP peering either). |
|
| 5 | +In previous [post](/howto/DN42-Over-SRv6-L3VPN), I have wrote how did I deploy DN42 over SRv3 L3VPN on my infrastructure, but haven't mention a more popular scenario: SRv6 for traffic looking up default routing table, not everyone want to mess with VRF (it's a trouble for service deployment and eBGP peering either). |
|
| 6 | 6 | |
| 7 | 7 | This article is about how to configure SRv6 for default routing table, with help of Containerlab for demostration. |
| 8 | 8 | |
| ... | ... | @@ -51,7 +51,7 @@ net.vrf.strict_mode resets 0 everytime a new VRF adds, to prevent network operat |
| 51 | 51 | # 4 BGP SRv6 for Default Routing Table |
| 52 | 52 | No VRF configuration involved in FRR, all happens in default scope. |
| 53 | 53 | |
| 54 | -Skip the deamons, SRv6 Locator and IS-IS configuration as they already shown in previous [post](howto/DN42-Over-SRv6-L3VPN). |
|
| 54 | +Skip the deamons, SRv6 Locator and IS-IS configuration as they already shown in previous [post](/howto/DN42-Over-SRv6-L3VPN). |
|
| 55 | 55 | |
| 56 | 56 | Send SRv6 encapsulation information in Unicast families, and use "sid export" instead "sid vpn export". |
| 57 | 57 | |
| ... | ... | @@ -426,7 +426,7 @@ rtt min/avg/max/mdev = 0.117/0.151/0.180/0.025 ms |
| 426 | 426 | ``` |
| 427 | 427 | |
| 428 | 428 | # 7 Known Limits |
| 429 | -This section is copied from my previous [post](howto/DN42-Over-SRv6-L3VPN). |
|
| 429 | +This section is copied from my previous [post](/howto/DN42-Over-SRv6-L3VPN). |
|
| 430 | 430 | |
| 431 | 431 | ## 7.1 NAT |
| 432 | 432 | When destination route has SRv6 encapsulation, the traffic won't trigger SNAT rule in netfilter, instead, it encapsulates into SRv6 traffic directly then send out. |