Replace all post_url with Hugo ref blocks
This commit is contained in:
content
articles
2021-02-27-network.md2021-03-27-coloclue-vpp.md2021-05-26-amsterdam.md2021-05-28-lille.md2021-06-01-paris.md2021-07-03-geneva.md2021-07-26-bucketlist.md2021-08-07-fs-switch.md2021-08-13-vpp-2.md2021-08-15-vpp-3.md2021-08-25-vpp-4.md2021-08-26-fiber7-x.md2021-09-02-vpp-5.md2021-09-21-vpp-7.md2021-10-24-as8298.md2021-11-26-netgate-6100.md2021-12-23-vpp-playground.md2022-02-14-vpp-vlan-gym.md2022-02-21-asr9006.md2022-03-03-syslog-telegram.md2022-03-27-vppcfg-1.md2022-04-02-vppcfg-2.md2022-10-14-lab-1.md2022-11-20-mastodon-1.md2022-11-24-mastodon-2.md2022-11-27-mastodon-3.md2022-12-05-oem-switch-1.md2022-12-09-oem-switch-2.md2023-02-12-fitlet2.md2023-02-24-coloclue-vpp-2.md2023-03-11-mpls-core.md2023-03-17-ipng-frontends.md2023-03-24-lego-dns01.md2023-04-09-vpp-stats.md2023-05-07-vpp-mpls-1.md2023-05-17-vpp-mpls-2.md2023-05-21-vpp-mpls-3.md2023-05-28-vpp-mpls-4.md2023-08-06-pixelfed-1.md2023-08-27-ansible-nginx.md2023-10-21-vpp-ixp-gateway-1.md2023-11-11-mellanox-sn2700.md2023-12-17-defra0-debian.md2024-01-27-vpp-papi.md2024-02-10-vpp-freebsd-1.md2024-02-17-vpp-freebsd-2.md2024-03-06-vpp-babel-1.md2024-04-06-vpp-ospf.md2024-04-27-freeix-1.md2024-05-17-smtp.md2024-05-25-nat64-1.md2024-06-22-vpp-ospf-2.md2024-06-29-coloclue-ipng.md2024-07-05-r86s.md2024-08-03-gowin.md
services.md@ -15,14 +15,13 @@ 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" >}})].
|
||||
|
||||
In the last article, I explored VPP's MPLS implementation a little bit. All the while,
|
||||
[@vifino](https://chaos.social/@vifino) has been tinkering with the Linux Control Plane and adding
|
||||
MPLS support to it, and together we learned a lot about how VPP does MPLS forwarding and how it
|
||||
sometimes differs to other implementations. During the process, we talked a bit about
|
||||
_implicit-null_ and _explicit-null_. When my buddy Fred read the [[previous article]({% post_url
|
||||
2023-05-07-vpp-mpls-1 %})], he also talked about a feature called _penultimate-hop-popping_ which
|
||||
_implicit-null_ and _explicit-null_. When my buddy Fred read the [[previous article]({{< ref "2023-05-07-vpp-mpls-1" >}})], he also talked about a feature called _penultimate-hop-popping_ which
|
||||
maybe deserves a bit more explanation. At the same time, I could not help but wonder what the
|
||||
performance is of VPP as a _P-Router_ and _PE-Router_, compared to say IPv4 forwarding.
|
||||
|
||||
@ -32,7 +31,7 @@ performance is of VPP as a _P-Router_ and _PE-Router_, compared to say IPv4 forw
|
||||
|
||||
For this article, I'm going to boot up instance LAB1 with no changes (for posterity, using image
|
||||
`vpp-proto-disk0@20230403-release`), and it will be in the same state it was at the end of my
|
||||
previous [[MPLS article]({% post_url 2023-05-07-vpp-mpls-1 %})]. To recap, there are four routers
|
||||
previous [[MPLS article]({{< ref "2023-05-07-vpp-mpls-1" >}})]. To recap, there are four routers
|
||||
daisychained in a string, and they are called `vpp1-0` through `vpp1-3`. I've then connected a
|
||||
Debian virtual machine on both sides of the string. `host1-0.enp16s0f3` connects to `vpp1-3.e2`
|
||||
and `host1-1.enp16s0f0` connects to `vpp1-0.e3`. Finally, recall that all of the links between these
|
||||
@ -286,7 +285,7 @@ operation performed on a packet does cost valuable CPU cycles.
|
||||
I can't really perform a loadtest on the virtual machines backed by Open vSwitch, while tightly
|
||||
packing six machines on one hypervisor. That setup is made specifically to do functional testing and
|
||||
development work. To do a proper loadtest, I will need bare metal. So, I grabbed three Supermicro
|
||||
SYS-5018D-FN8T, which I'm running throughout [[AS8298]({% post_url 2021-02-27-network %})], as I
|
||||
SYS-5018D-FN8T, which I'm running throughout [[AS8298]({{< ref "2021-02-27-network" >}})], as I
|
||||
know their performance quite well. I'll take three of these, and daisychain them with TenGig ports.
|
||||
This way, I can take a look at the cost of _P-Routers_ (which only SWAP MPLS labels and forward the
|
||||
result), as well as _PE-Routers_ (which have to encapsulate, and sometimes decapsulate the IP or
|
||||
@ -295,7 +294,7 @@ Ethernet traffic).
|
||||
These machines get a fresh Debian Bookworm install and VPP 23.06 without any plugins. It's weird for
|
||||
me to run a VPP instance without Linux CP, but in this case I'm going completely vanilla, so I
|
||||
disable all plugins and give each VPP machine one worker thread. The install follows my popular
|
||||
[[VPP-7]({% post_url 2021-09-21-vpp-7 %})]. By the way did you know that you can just type the search query [VPP-7] directly into Google to find this article. Am I an influencer now? Jokes aside, I decide to call the bare metal machines _France_,
|
||||
[[VPP-7]({{< ref "2021-09-21-vpp-7" >}})]. By the way did you know that you can just type the search query [VPP-7] directly into Google to find this article. Am I an influencer now? Jokes aside, I decide to call the bare metal machines _France_,
|
||||
_Belgium_ and _Netherlands_. And because if it ain't dutch, it ain't much, the Netherlands machine
|
||||
sits on top :)
|
||||
|
||||
|
Reference in New Issue
Block a user