All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Network Architecture: Using VXLAN Inside WireGuard for Site-to-Site Overlay Networks

By

mlhpdx

4mo ago· 5 min readenInsight

Summary

The article discusses network architecture recommendations for site-to-site overlay networks, specifically addressing whether to use VXLAN over WireGuard or WireGuard over VXLAN. The author recommends using WireGuard as the primary transport layer with VXLAN inside it, arguing that WireGuard's purpose is to securely connect networks across untrusted channels. The content emphasizes that WireGuard should form the foundational secure connection, while VXLAN can be used within that secure tunnel for additional network segmentation or functionality when needed.

Key quotes

· 5 pulled
For site-to-site overlay networks, use wireguard, vxlan should be inside of it, if at all.
Your 'network' is connected by wireguard, and it contains details like vxlan.
Even within your network, when crossing security boundaries across untrusted channels, you can use wireguard.
Others mentioned tailscale, it's cool and all but you don't always need it.
You should do so because that's the purpose of wireguard, to connect networks securely across secure channels.
Snippet from the RSS feed
For site-so-site ovelay networks, use wireguard, vxlan should be inside of it, if at all. Your "network" is connected by wireguard, and it contains details like vxlan. Even within your network, when crossing security boundaries across untrusted channels,

You might also wanna read