diff options
| -rw-r--r-- | docs/configuration/protocols/ospf.md | 6 | ||||
| -rw-r--r-- | docs/vpp/configuration/ipsec.md | 6 |
2 files changed, 6 insertions, 6 deletions
diff --git a/docs/configuration/protocols/ospf.md b/docs/configuration/protocols/ospf.md index 7736f0c9..4fcca823 100644 --- a/docs/configuration/protocols/ospf.md +++ b/docs/configuration/protocols/ospf.md @@ -1460,9 +1460,9 @@ set protocols ospfv3 redistribute connected show ipv6 ospfv3 redistribute ``` -Cost calculation wireguard interfaces is unreliable as ospfv3 uses the link -speed to calculate the link cost. You might therefore want to set the link -cost to a fixed value on WireGuard tunnels. +Cost calculation for WireGuard interfaces is unreliable as ospfv3 uses the +link speed to calculate the link cost. You might therefore want to set the +link cost to a fixed value on WireGuard tunnels. Example configuration for WireGuard interfaces: diff --git a/docs/vpp/configuration/ipsec.md b/docs/vpp/configuration/ipsec.md index 9dc0fca5..710a94b3 100644 --- a/docs/vpp/configuration/ipsec.md +++ b/docs/vpp/configuration/ipsec.md @@ -10,7 +10,7 @@ lastproofread: '2025-09-04' # VPP IPsec Configuration VPP Dataplane in VyOS can offload IPSec processing from kernel. This allows -to speed-up IPSec traffic handling significantly, when necessary conditions +to speed up IPSec traffic handling significantly when necessary conditions are met. :::{note} @@ -36,7 +36,7 @@ configuration itself. IPSec configuration management and control-plane operation, like IKE negotiation, is still done by the kernel and other daemons. After an IPSec tunnel is configured in the kernel, VPP receives the necessary -information via netlink messages and creates a corresponding SAs and policies +information via netlink messages and creates corresponding SAs and policies to be able to offload the traffic. When VPP is used for offloading IPsec, it creates a virtual interface of a @@ -208,7 +208,7 @@ Improper IPsec configuration can lead to various issues, including: - **Conflicting with kernel routes** If the kernel routes synchronization option is enabled, VPP will install - all the routes from kernel. If you have there routes configured via VTI + all the routes from kernel. If you have these routes configured via VTI interfaces to the IPsec peer, they will conflict with the policy routes created for the IPsec tunnel in VPP. Consider using policy-based IPSec configuration to avoid this or |