（此視頻中顯示的所有私鑰均已銷毀）時間戳：0:00 介紹 2:12 生成 Mullvad 配置文件 6:16 pfSense WireGuard 隧道創建 8:15 pfSense WireGuard Peer 創建 10:27 pfSense 介面分配和定址 17:35 pfSense 網關監控 21:00 pfSense 網關組 22:32 用於基於策略的路由的 pfSense 防火牆規則 24:03 pfSense NAT 規則 25:20 演示和測試 最新版本：https://github.com/theonemcdonald/pfSense-pkg-WireGuard /releases/latest 項目：https://github.com/theonemcdonald/pfSense-pkg-WireGuard 支持：GitHub 贊助商：https://github.com/sponsors/theonemcdonald PayPal：https://paypal.me/rcmcdonald91 BTC： 3DLpMTP1Ddrv2EFT6MbVJ1tKzYYvXAHQNF LTC：MAzGepkVp1yfvvraHZWDsFSojLTnCUActf 討論：Reddit：https://reddit.com/r/PFSENSE 論壇：https://forum.netgate.com/category.com/82 wireguard-returns-as-an-experimental-package.html 。
pfSense WireGuard 指南系列 001 – Mullvad 故障轉移
8 comments
Comments are closed.
When you were done with everything on the pfsense side how did you activate the wireguard before testing? Thank you
I think I ran into an issue, I have a site-to-site tunnel using wireguard, one end on pfsense(ISP->pfsense, public static IP) and the other end on a raspberry pi(ISP->their device->pi, public dynamic IP- which I map to one of my subdomain using a script -30 min ttl).
On pfsense side, the peer endpoint is this subdomain, it seems to get stuck with that IP address. It doesn't seem to retry/look up the new record after the ttl expiry, meaning my tunnel will be broken once my ISP issues new IP on raspberry pi side. I would have to stop/start fiddle with end point to re-stablish tunnel. This can be addressed somehow?
Thank you for making this very detailed tutorial. Excellent delivery, as usual!
This is cool! Thank you!
This is cool! Thank you!
Cool introduction on how to use your package. Thank your for your awesome development on this wg package!!
One question: Why do we exactly need the NAT rule? I did not get that.
Brilliant. Looking forward to more and Thank you, too you and the other contributors for taking on this project!!
This is awesome. Thank you for the hard work and guide!