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@ -10,12 +10,12 @@ title: VPP with Babel - Part 1
|
||||
Ever since I first saw VPP - the Vector Packet Processor - I have been deeply impressed with its
|
||||
performance and versatility. For those of us who have used Cisco IOS/XR devices, like the classic
|
||||
_ASR_ (aggregation services router), VPP will look and feel quite familiar as many of the approaches
|
||||
are shared between the two. Thanks to the [[Linux ControlPlane]({% post_url 2021-08-12-vpp-1 %})]
|
||||
are shared between the two. Thanks to the [[Linux ControlPlane]({{< ref "2021-08-12-vpp-1" >}})]
|
||||
plugin, higher level control plane software becomes available, that is to say: things like BGP,
|
||||
OSPF, LDP, VRRP and so on become quite natural for VPP.
|
||||
|
||||
IPng Networks is a small service provider that has built a network based entirely on open source:
|
||||
[[Debian]({% post_url 2023-12-17-defra0-debian %})] servers with widely available Intel and Mellanox
|
||||
[[Debian]({{< ref "2023-12-17-defra0-debian" >}})] servers with widely available Intel and Mellanox
|
||||
10G/25G/100G network cards, paired with [[VPP](https://fd.io/)] for the dataplane, and
|
||||
[[Bird2](https://bird.nic.cz/)] for the controlplane.
|
||||
|
||||
@ -191,7 +191,7 @@ Babel-Bird out for a test flight. Thank you for the Babel-Bird-Build, Summer!
|
||||
|
||||
### Babel and the LAB
|
||||
|
||||
I decide to take an IPng [[lab]({% post_url 2022-10-14-lab-1 %})] out for a spin. These labs come
|
||||
I decide to take an IPng [[lab]({{< ref "2022-10-14-lab-1" >}})] out for a spin. These labs come
|
||||
with four VPP routers and two Debian machines connected like so:
|
||||
|
||||
{{< image src="/assets/vpp-mpls/LAB v2.svg" alt="Lab Setup" >}}
|
||||
@ -288,8 +288,8 @@ IPv6 loopbacks across the network.
|
||||
|
||||
IPv6 pings and looks good. However, IPv4 endpoints do not ping yet. The first thing I look at, is
|
||||
does VPP understand how to interpret an IPv4 route with an IPv6 nexthop? I think it does, because I
|
||||
remember reviewing a change from Adrian during our MPLS [[project]({% post_url 2023-05-28-vpp-mpls-4
|
||||
%})], which he submitted in this [[Gerrit](https://gerrit.fd.io/r/c/vpp/+/38633)]. His change
|
||||
remember reviewing a change from Adrian during our MPLS [[project]({{< ref "2023-05-28-vpp-mpls-4" >}})],
|
||||
which he submitted in this [[Gerrit](https://gerrit.fd.io/r/c/vpp/+/38633)]. His change
|
||||
allows VPP to use routes with `rtnl_route_nh_get_via()` to map them to a different address family,
|
||||
exactly what I am looking for. The routes are correctly installed in the FIB:
|
||||
|
||||
@ -415,7 +415,7 @@ loop0 (up):
|
||||
```
|
||||
|
||||
The Linux ControlPlane configuration will always synchronize interface information from VPP to
|
||||
Linux, as I described back then when I [[worked on the plugin]({% post_url 2021-08-13-vpp-2 %})].
|
||||
Linux, as I described back then when I [[worked on the plugin]({{< ref "2021-08-13-vpp-2" >}})].
|
||||
Babel starts and sets next hops for IPv4 that look like this:
|
||||
|
||||
```
|
||||
@ -631,7 +631,7 @@ to retire the many /31 IPv4 and /112 IPv6 transit networks (which consume about
|
||||
IPv4 addresses!). I will discuss my change with the VPP and Babel/Bird Developer communities and see
|
||||
if it makes sense to upstream my changes. Personally, I think it's a reasonable direction, because
|
||||
(a) both changes are backwards compatible and (b) its semantics are pretty straight forward. I'll
|
||||
also add some configuration knobs to [[vppcfg]({% post_url 2022-04-02-vppcfg-2 %})] to make it
|
||||
also add some configuration knobs to [[vppcfg]({{< ref "2022-04-02-vppcfg-2" >}})] to make it
|
||||
easier to configure VPP in this way.
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user