one thing to note, depending on your usecase, if it is pure performance also look into the mtu settings. in your demo the vxlan interface was bigger than the wireguard one, meaning one big vxlan datagram would encapsulate into 1 more additional wireguard packet which needs to be sent, easily doubling the required packets
Yeah true. Every cunt and his dog takes a cut out of the MTU these days. It really was just to demo the concept though. MTU talk is for another day/video.
i love keeping it simple like this for teaching and demo purposes. best way to start learning networking is two pcs directly connected by a cat cable, make sure you understand everything going on. expand from there
This is a new one for me. Have a video idea if you have time, I have a pfsense box running 2 vlans (1&2), obviously both on 2 diff subnets. My issue is getting multicast between then through the dell power connect switch. I have no idea how to do it. Any pointers for simply doing it so I can access my had homerun from either clan would be great
Nice one! I didn't know about VXLANs. Thanks for the tip! Curious why the bind was against dev eno1, I was thinking it would be wg0 since the traffic is all popping out of wireguard?
The VXLAN was bound to eno1 since eno1 and the other side (Aruba switch) would be sharing the same Layer 2 domain. The reason it's not bound to wg0 is because VXLAN travels over Layer 3. So the Linux machine only needs to know how to get to the other side via it's L3 routing table.
Why would I have a broadcast storm in the first place? That would take out a LAN as it is. This demo was just a very crude example of the concept anyway.
I’ve heard VXLAN used a billion times but never actually heard about how it works, this was a cool overview!
Well, there you go
I've seen VXLAN in my router's settings, but never thought to learn what it does, thanks for this quick and simple explanation!
Did not know it was that easy to get a basic setup with vxlan.
VXLAN is awesome, just connected a customer to our EVPN fabric. Coolest thing about it is the multi-homing.
one thing to note, depending on your usecase, if it is pure performance also look into the mtu settings. in your demo the vxlan interface was bigger than the wireguard one, meaning one big vxlan datagram would encapsulate into 1 more additional wireguard packet which needs to be sent, easily doubling the required packets
Yeah true. Every cunt and his dog takes a cut out of the MTU these days. It really was just to demo the concept though. MTU talk is for another day/video.
I love this, but what is your HA setup managing at Scott place?
i love keeping it simple like this for teaching and demo purposes. best way to start learning networking is two pcs directly connected by a cat cable, make sure you understand everything going on. expand from there
Many people skip the basics
Ethernet MTU is 1500, vxlan MTU is 1450 and WG 1420... I would love to see a pcap at each level to see how much fragmentation is going on here...
This is a new one for me. Have a video idea if you have time, I have a pfsense box running 2 vlans (1&2), obviously both on 2 diff subnets. My issue is getting multicast between then through the dell power connect switch. I have no idea how to do it. Any pointers for simply doing it so I can access my had homerun from either clan would be great
You need a multicast gateway setup. Or if it's mdns an mdns gateway. There's probably an addon for that in pfsense
Nice one! I didn't know about VXLANs. Thanks for the tip!
Curious why the bind was against dev eno1, I was thinking it would be wg0 since the traffic is all popping out of wireguard?
As I mentioned, if you want a sub interface with a vlan...
The VXLAN was bound to eno1 since eno1 and the other side (Aruba switch) would be sharing the same Layer 2 domain. The reason it's not bound to wg0 is because VXLAN travels over Layer 3. So the Linux machine only needs to know how to get to the other side via it's L3 routing table.
Aww... you left out the good BGP stuff!
Mate, people cry if I don't mention basic stuff half of the time
Would you kill your WAN now when there's a broadcast storm on your LAN?
Why would I have a broadcast storm in the first place? That would take out a LAN as it is.
This demo was just a very crude example of the concept anyway.
@TallPaulTech very fair, it's not of much use if the LAN is down as well