# WireGuard connection to Flint 2 succeeds from LAN, but fails from outside network

**URL:** <https://forum.gl-inet.com/t/wireguard-connection-to-flint-2-succeeds-from-lan-but-fails-from-outside-network/68462>\
**Category:** VPN, DNS, Leaks\
**Created:** [April 30, 2026, 6:56pm UTC](https://forum.gl-inet.com/t/wireguard-connection-to-flint-2-succeeds-from-lan-but-fails-from-outside-network/68462 "2026-04-30T18:56:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![janedenone](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/da6949/32.png) [@janedenone](https://forum.gl-inet.com/u/janedenone)\
**Post date:** [May 2, 2026, 6:20am UTC](https://forum.gl-inet.com/t/wireguard-connection-to-flint-2-succeeds-from-lan-but-fails-from-outside-network/68462/4 "2026-05-02T06:20:28Z")

</div>

I was under the impression that configuring and activating the WireGuard server on the router modified the firewall accordingly. I did not open the port manually before the reset (when the WireGuard configuration did work). Edit: Confirmed, there is a rule wgserver2lan. But for the wgserver interface, LuCi says “Unsupported protocol type.” After installing the missing bits of luci-proto-wireguard, this message is still there (but as I wrote in my original post, the WireGuard tunnel works from within the LAN).

---

_[View the full topic](https://forum.gl-inet.com/t/wireguard-connection-to-flint-2-succeeds-from-lan-but-fails-from-outside-network/68462)._