JoLeKing

User Tools

Site Tools

Trace:
networking:containerlab:srv6_l3vpn

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
networking:containerlab:srv6_l3vpn [2026/06/08 12:30] – jonathannetworking:containerlab:srv6_l3vpn [2026/06/08 13:34] (current) – jonathan
Line 11: Line 11:
   * **Network Isolation**: Dedicated tenant routing is isolated using Linux VRF tables (RED and BLUE) bound to the physical interfaces.   * **Network Isolation**: Dedicated tenant routing is isolated using Linux VRF tables (RED and BLUE) bound to the physical interfaces.
   * **Data-Plane MTU Engineering**: The Core transit MTU is explicitly engineered to **1578 bytes** to accommodate the heavy overhead of SRv6 headers (IPv6 header + Segment Routing Header + 128-bit VPN SIDs) so that standard client frames (1500-byte MTU) bypass core fragmentation or dropping.   * **Data-Plane MTU Engineering**: The Core transit MTU is explicitly engineered to **1578 bytes** to accommodate the heavy overhead of SRv6 headers (IPv6 header + Segment Routing Header + 128-bit VPN SIDs) so that standard client frames (1500-byte MTU) bypass core fragmentation or dropping.
 +
 +{{:networking:containerlab:srv6-l3vpn.png?400|}}
  
 ---- ----
networking/containerlab/srv6_l3vpn.txt · Last modified: by jonathan