User Tools

Site Tools


networking:containerlab:srv6_l3vpn

Differences

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

Link to this comparison view

Next revision
Previous revision
networking:containerlab:srv6_l3vpn [2026/06/05 19:32] – created 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|}}
  
 ---- ----
Line 1479: Line 1481:
 interface eth2 interface eth2
  description "to p1 - eth2"  description "to p1 - eth2"
- ipv6 address 2001:db8:12::4/64+ ipv6 address 2001:db8:14::2/64
  ipv6 router isis SR  ipv6 router isis SR
  isis network point-to-point  isis network point-to-point
networking/containerlab/srv6_l3vpn.1780687960.txt.gz · Last modified: by jonathan