Blog/fortigate wireguard migration #133
Open
+297
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Article Structure
Introduction with link to Fortinet's official deprecation notice
The Missing Layer: Data Plane vs. Control Plane - explains what WireGuard lacks by design
Choosing a WireGuard-Based Remote-Access Solution - comparison table (Defguard vs Tailscale vs NetBird vs WG Easy)
Enabling Transition from SSL VPN to Defguard - Control Plane capabilities for enterprise
Summary with CTA links
FAQ section (5 questions) with JSON-LD Schema.org markup