ANSWERED Do i need to make firewall rules to port forward?

[Askr 0]

Hello, I have a forwarded port set up following the guide (https://airvpn.org/faq/p2p/) and it works perfectly fine for qBittorrent, however Nicotine+ cannot connect on tcp and says the port is closed. Setting a firewall rule to allow incoming traffic, on the VPN Network interface, to my specific forwarded port allows the connection for N+. In the guide there is no mention of having to change firewall settings in order to make use of the forwarded port. Am i doing something wrong here? and is making this rule safe as in not getting my real ip detected.

The rule I made that worked was Allow In on tun0 interface, using both protocols, on Port #

I am using Linux Mint 21.3, with the firewall in the default state of "Incoming: Deny" and "Outgoing: Allow"

[Staff 10116]

  On 10/11/2024 at 9:36 PM, Askr said:

the firewall in the default state of "Incoming: Deny"

Hello!

In this case it is self-evident that you must add a rule to allow incoming packets to the desired application's port to make that application reachable from the outside. Note that Eddie's and AirVPN Suite's Network Lock will set policy and new rules either with nft or iptables on the default table chains and by default this feature will allow incoming packets from the VPN server entry IP addresses.

Kind regards
 

[Askr 0]

Thank you for the help, I have set the rules back up for tun0 in on the specific port i have.