ANSWERED Setting-up Flint 2 as Wireguard client

[Tigron 0]

Hi,
I have just finished setting-up a Flint2 router as a wireguard client. The Flint2 seats behind my primary router which provides it access to the WAN.

I have downloaded a Wireguard config from the Config generator, loaded it and I can establish a connection with no problem. I have temporarily connected a PC to one of the LAN port and I can see that it's got the VPN IP when browsing.

However when I test my forwarded port I get the following error: "Connection refused 111". Is there a specific FW rule in the Flint2 to set-up in order to accept incoming connections?

Thanks for the help.
T

[Staff 10116]

  On 10/14/2024 at 12:11 PM, Tigron said:

However when I test my forwarded port I get the following error: "Connection refused 111". Is there a specific FW rule in the Flint2 to set-up in order to accept incoming connections?

Hello!

Yes, you need to handle packets in order to forward them to the proper destination. The VPN server sends incoming packets to Flint2, which in turn decrypts the VPN flow. Then, the router can not know the real, final destination of each unsolicited packet and you must define the proper rules. An example with iptables here:
https://airvpn.org/forums/topic/9270-how-to-forward-ports-in-dd-wrt-tomato-with-iptables/

According to online documentation it appears that Flint2 OEM firmware's graphical interface supports inbound port forwarding from the VPN interface, please check the router's manual.

Kind regards