ANSWERED Trouble getting ufw to let traffic through a port

[Kaappi 0]

So I forwarded a port on AirVPN and then made qBittorrent use the same port for incoming connections, bound it to the specific interface etc etc. Now the trouble I'm facing is actually getting ufw to letting traffic through.

I did:

sudo ufw allow qbittorrent

And as it assigns a different port number compared to the one I've forwarded I went and edited the file in /etc/ufw/applications.d/ufw-bittorrent and changed the port and protocol.

Afterwards I did:

sudo ufw reload
sudo ufw status verbose

The output from the status command tells me that it didn't change the port and now I'm wondering how I could change it? Or did I do something wrong?

Thanks.

[Staff 10079]

@Kaappi

Hello!

Please find the solution on ufw manual (see below for a quick rule). We want to warn you: you have forwarded only incoming UDP, while qBittorrent relies a lot on TCP. Please make sure to forward TCP too for the port you have been assigned.
sudo ufw allow in on <tun interface name> from any to any port <your reserved port number>

Kind regards
 

[Kaappi 0]

5 hours ago, Staff said:

@Kaappi

Hello!

Please find the solution on ufw manual (see below for a quick rule). We want to warn you: you have forwarded only incoming UDP, while qBittorrent relies a lot on TCP. Please make sure to forward TCP too for the port you have been assigned.
sudo ufw allow in on <tun interface name> from any to any port <your reserved port number>

Kind regards
 

Thanks for the response. I wasn't sure whether or not wireguard supported TCP, but I guess I was wrong. I now have forwarded both, and at the same time I fixed the issue. Nothing on my end was listening to the port So when I opened qBittorrent it instantly started working!

[Staff 10079]

1 hour ago, Kaappi said:

I wasn't sure whether or not wireguard supported TCP

Hello!

We're glad to know the the problem is resolved.
 

1 hour ago, Kaappi said:

I wasn't sure whether or not wireguard supported TCP

WireGuard doesn't support TCP as a VPN connection protocol, but this is unrelated. When a tunnel is established over UDP,  any transport layer protocol packets (TCP, UDP, RDP etc. etc.) get wrapped inside UDP.

Kind regards