"
I hope it's OK to post on this old topic, but we are trialing Defguard right now as our insurance policy requires that we implement MFA on all VPN connectivity and Wireguard doesn't provide that functionality.
I'm wondering how best to encourage Defguard to submit their existing VPN Gateway plugin for Opnsense as a community plugin:
https://docs.defguard.net/features/gateway
https://github.com/DefGuard/gateway/tree/main/opnsense
https://github.com/DefGuard/gateway/releases/download/v1.5.1/defguard-gateway_1.5.1_x86_64-unknown-freebsd.pkg
It's currently implemented as a PKG, but I'd love to see it added to the community plugins repo. However, to facilitate that I'd like to provide Defguard with a concise roadmap on how to quickly tweak their existing code to align with what Opnsense expects for community packages.
I'm wondering how best to encourage Defguard to submit their existing VPN Gateway plugin for Opnsense as a community plugin:
https://docs.defguard.net/features/gateway
https://github.com/DefGuard/gateway/tree/main/opnsense
https://github.com/DefGuard/gateway/releases/download/v1.5.1/defguard-gateway_1.5.1_x86_64-unknown-freebsd.pkg
It's currently implemented as a PKG, but I'd love to see it added to the community plugins repo. However, to facilitate that I'd like to provide Defguard with a concise roadmap on how to quickly tweak their existing code to align with what Opnsense expects for community packages.
