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

10
content/articles/2022-02-14-vpp-vlan-gym.md
View File

@ -20,7 +20,7 @@ can be shared between VPP and the Linux kernel in a clever way, so running softw
up and running, VPP has so much more to offer - many interesting L2 and L3 services that you'd expect
in commercial (and very pricy) routers like Cisco ASR are well within reach.
When Fred and I were in Paris [[report]({%post_url 2021-06-01-paris %})], I got stuck trying to
When Fred and I were in Paris [[report]({{< ref "2021-06-01-paris" >}})], I got stuck trying to
configure an Ethernet over MPLS circuit for IPng from Paris to Zurich. Fred took a look for me
and quickly determined "Ah, you forgot to do the VLAN gymnastics". I found it a fun way to describe
the solution to my problem back then, and come to think of it: the router really can be configured
@ -109,7 +109,7 @@ vpp# set interface l2 bridge BondEthernet0 10
And if I want to add an IP address (creating the equivalent of a routable _VLAN Interface_), I create what
is called a Bridge Virtual Interface or _BVI_, add that interface to the bridge domain, and optionally
expose it in Linux with the [LinuxCP]({%post_url 2021-09-21-vpp-7%}) plugin:
expose it in Linux with the [LinuxCP]({{< ref "2021-09-21-vpp-7" >}}) plugin:
```
vpp# bvi create instance 10 mac 02:fe:4b:4c:22:8f
@ -143,7 +143,7 @@ of what I might be able to configure on an L2 switch.
### L2 CrossConnect
I thought it'd be useful to point out another powerful concept, which made an appearance in my previous
post about [Virtual Leased Lines]({%post_url 2022-01-12-vpp-l2%}). If all I want to do is connect two
post about [Virtual Leased Lines]({{< ref "2022-01-12-vpp-l2" >}}). If all I want to do is connect two
interfaces together, there won't be a need for learning, L2 FIB, and so on. It is computationally much
simpler to just take any frame received on interface A and transmit it out on interface B, unmodified.
This is known in VPP as a layer2 crossconnect, and can be configured like so:
@ -318,12 +318,12 @@ The four concepts discussed here can be combined in countless interesting ways:
* Ensure that VLAN tags are popped and pushed consistently on tagged sub-interfaces
The practical conclusion is that VPP can provide fully transparent, dot1q and jumboframe enabled
virtual leased lines (see my previous post on [VLL performance]({%post_url 2022-01-12-vpp-l2 %})),
virtual leased lines (see my previous post on [VLL performance]({{< ref "2022-01-12-vpp-l2" >}})),
including using regular breakout switches to greatly increase the total port count for customers.
I'll leave you with a working example of an L2VPN between a breakout switch behind **nlams0.ipng.ch**
in Amsterdam and a remote VPP router in Zurich called **ddln0.ipng.ch**. Take the following
[S5860-20SQ]({%post_url 2021-08-07-fs-switch %}) switch, which connects to the VPP router on Te0/1
[S5860-20SQ]({{< ref "2021-08-07-fs-switch" >}}) switch, which connects to the VPP router on Te0/1
and a customer on Te0/2:
```