Originally created by @lordraiden on GitHub (Sep 20, 2025).
I'd like to suggest adding support for amneziawg-go as an optional backend alongside WireGuard.
Why amneziawg-go?
No kernel dependency: Runs entirely in user space, simplifying deployment on systems without WireGuard kernel module.
Cross-platform: Easier to support on platforms like Windows/macOS where kernel-level WireGuard can be problematic.
Lightweight & fast: Designed for performance and minimal resource usage.
Built-in obfuscation: Helps bypass VPN blocks and DPI filtering.
This could broaden Pangolin’s compatibility and resilience in restrictive environments.
Thanks for considering!
Originally created by @lordraiden on GitHub (Sep 20, 2025).
I'd like to suggest adding support for amneziawg-go as an optional backend alongside WireGuard.
Why amneziawg-go?
- No kernel dependency: Runs entirely in user space, simplifying deployment on systems without WireGuard kernel module.
- Cross-platform: Easier to support on platforms like Windows/macOS where kernel-level WireGuard can be problematic.
- Lightweight & fast: Designed for performance and minimal resource usage.
- Built-in obfuscation: Helps bypass VPN blocks and DPI filtering.
This could broaden Pangolin’s compatibility and resilience in restrictive environments.
Thanks for considering!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @lordraiden on GitHub (Sep 20, 2025).
I'd like to suggest adding support for amneziawg-go as an optional backend alongside WireGuard.
Why amneziawg-go?
This could broaden Pangolin’s compatibility and resilience in restrictive environments.
Thanks for considering!
@oschwartz10612 commented on GitHub (Sep 20, 2025):
Thanks for the feature request! Going to move to a discussion so people can track and up vote