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

13
content/articles/2023-12-17-defra0-debian.md
View File

@ -18,8 +18,7 @@ which graduated into a feature called the Linux Control Plane plugin
for the Linux Control Plane, notably Neale Ranns from Cisco (these days Graphiant), and Matt Smith
and Jon Loeliger from Netgate (who ship this as TNSR [[ref](https://netgate.com/tnsr)], check it out!).
I helped as well, by adding a bunch of Netlink handling and VPP->Linux synchronization code,
which I've written about a bunch on this blog in the 2021 VPP development series [[ref]({% post_url
2021-08-12-vpp-1 %})].
which I've written about a bunch on this blog in the 2021 VPP development series [[ref]({{< ref "2021-08-12-vpp-1" >}})].
At the time, Ubuntu and CentOS were the supported platforms, so I installed a bunch of Ubuntu
machines when doing the deploy with my buddy Fred from IP-Max [[ref](https://ip-max.net)]. But as
@ -33,8 +32,7 @@ I took stock of the fleet at the end of 2023, and I found the following:
* ***OpenBSD***: 3 virtual machines, bastion jumphosts connected to Internet and IPng Site Local
* ***Ubuntu***: 4 physical machines, VPP routers (`nlams0`, `defra0`, `chplo0` and `usfmt0`)
* ***Debian***: 22 physical machines and 116 virtual machines, running internal and public services,
almost all of these machines are entirely in IPng Site Local [[ref]({% post_url
2023-03-11-mpls-core %})], not connected to the
almost all of these machines are entirely in IPng Site Local [[ref]({{< ref "2023-03-11-mpls-core" >}})], not connected to the
internet at all.
It became clear to me that I could make a small sprint to standardize all physical hardware on
@ -48,10 +46,9 @@ unilaterally :)
## Upgrading to Debian
Luckily, I already have a fair number of VPP routers that have been deployed on Debian (mostly
_Bullseye_, but one of them is _Bookworm_), and my LAB environment [[ref]({% post_url
2022-10-14-lab-1 %})] is running Debian Bookworm as well. Although its native habitat is Ubuntu, I
_Bullseye_, but one of them is _Bookworm_), and my LAB environment [[ref]({{< ref "2022-10-14-lab-1" >}})] is running Debian Bookworm as well. Although its native habitat is Ubuntu, I
regularly run VPP in a Debian environment, for example when Adrian contributed the MPLS code
[[ref]({% post_url 2023-05-21-vpp-mpls-3 %})], he also recommended Debian 12, because that ships
[[ref]({{< ref "2023-05-21-vpp-mpls-3" >}})], he also recommended Debian 12, because that ships
with a modern libnl which supports a few bits and pieces he needed.
### Preparations
@ -281,7 +278,7 @@ Debian 12 _netinst_ ISO:
At this point I can't help but smile. I'm sitting here in Br&uuml;ttisellen, roughly 400km south of
this computer in Frankfurt, and I am looking at the VGA output of a fresh Debian installer. Come on,
you have to admit, that's pretty slick! Installing Debian follows pretty precisely my previous VPP#7
article [[ref]({% post_url 2021-09-21-vpp-7 %})]. I go through the installer options and a few
article [[ref]({{< ref "2021-09-21-vpp-7" >}})]. I go through the installer options and a few
minutes later, it's mission accomplished. I give the router its IPv4/IPv6 address in _IPng Site
Local_, so that it has management network connectivity, and just before it wants to reboot, I
quickly edit `/etc/default/grub` to turn on serial output, just like in the article: