ipng/ipng.ch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replace all post_url with Hugo ref blocks

Browse Source
This commit is contained in:
Pim van Pelt
2024-08-05 01:43:55 +02:00
parent c1f1775c91
commit a2f10236a3
56 changed files with 221 additions and 241 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/articles/2023-05-07-vpp-mpls-1.md
View File

@ -15,7 +15,7 @@ are shared between the two.
I've deployed an MPLS core for IPng Networks, which allows me to provide L2VPN services, and at the
same time keep an IPng Site Local network with IPv4 and IPv6 that is separate from the internet,
based on hardware/silicon based forwarding at line rate and high availability. You can read all
about my Centec MPLS shenanigans in [[this article]({% post_url 2023-03-11-mpls-core %})].
about my Centec MPLS shenanigans in [[this article]({{< ref "2023-03-11-mpls-core" >}})].
Ever since the release of the Linux Control Plane [[ref](https://github.com/pimvanpelt/lcpng)]
plugin in VPP, folks have asked "What about MPLS?" -- I have never really felt the need to go this
@ -23,7 +23,7 @@ rabbit hole, because I figured that in this day and age, higher level IP protoco
are just as performant, and a little bit less of an 'art' to get right. For example, the Centec
switches I deployed perform VxLAN, GENEVE and GRE all at line rate in silicon. And in an earlier
article, I showed that the performance of VPP in these tunneling protocols is actually pretty good.
Take a look at my [[VPP L2 article]({% post_url 2022-01-12-vpp-l2 %})] for context.
Take a look at my [[VPP L2 article]({{< ref "2022-01-12-vpp-l2" >}})] for context.
You might ask yourself: _Then why bother?_ To which I would respond: if you have to ask that question,
clearly you don't know me :) This article will form a deep dive into MPLS as implemented by VPP. In
@ -33,7 +33,7 @@ as a fully fledged provider- and provider-edge MPLS router.
## Lab Setup
A while ago I created a [[VPP Lab]({% post_url 2022-10-14-lab-1 %})] which is pretty slick, I use it
A while ago I created a [[VPP Lab]({{< ref "2022-10-14-lab-1" >}})] which is pretty slick, I use it
all the time. Most of the time I find myself messing around on the hypervisor and adding namespaces
with interfaces in it, to pair up with the VPP interfaces. And I tcpdump a lot! It's time for me to
make an upgrade to the Lab -- take a look at this picture:
@ -145,7 +145,7 @@ machine, or emitting _egress_ from any port on any machine, respectively.
## Preparing the LAB
I wrote a little bit about the automation I use to maintain a few reproducable lab environments in a
[[previous article]({% post_url 2022-10-14-lab-1 %})], so I'll only show the commands themselves here,
[[previous article]({{< ref "2022-10-14-lab-1" >}})], so I'll only show the commands themselves here,
not the underlying systems. When the LAB boots up, it comes with a basic Linux CP configuration that
uses OSPF and OSPFv3 running in Bird2, to connect the `vpp0-0` through `vpp0-3` machines together (each
router's Gi10/0/0 port connects to the next router's Gi10/0/1 port). LAB0 is in use by