ANSWERED P2P

[flat4 79]

This is not a airvpn issue as what I currently have is working but need some advice.
My firewall is a pfsense box and its been working for many years no issues. I have forwarded ports (thank you air) that are operational.  I recently discovered that if a tracker is using UDP to transfer or to call out I get nothing.
If the tracker uses tcp it works. At first I thought it might be the client I so I got a seedbox to test, its not the client because it  had no problems.

I have poured thru the firewall logs and cannot find were it blocking any udp so anyone else have a suggestions on what could be the issue. Both the airvpn port forward and my firewall rules allow tcp and udp.

[Staff 10014]

2 hours ago, flat4 said:

if a tracker is using UDP to transfer or to call out I get nothing.

Hello!

This reminds us of an ancient qBittorrent bug that could be caused by libtorrent. Do you run any torrent software based on libtorrent? If so which version? This bug was allegedly fixed years ago...
https://forum.qbittorrent.org/viewtopic.php?t=4342

Kind regards
 

[flat4 79]

I'm running transmission 4.0.6 on linux

[Staff 10014]

2 hours ago, flat4 said:

I'm running transmission 4.0.6 on linux

Hello!

It's not linked against libtorrent (its backend is libTransmission) so our previous speculation is wrong. To discern whether it is a Transmission specific problem, have you tested other torrent software with the same torrents?

Kind regards

 

[flat4 79]

Yes I have using the latest qbittorent version 5 same tracker same story its odd,

Like I said it not a air issue could be a firewall issue I just have not found the culprit. I have even tried just using UDP on my airvpn forward port still same results.