No Upload when using Proton-PMP

[CrazyWolf13]

Hi
I've set up qbittorrent nox on a LXC on my Proxmox Cluster, behind my Opnsense, behind my ISP router(opnsense as subnet router)(not sure if that matters.)

My qbittorren sometimes had upload but very always rather slow, but due to me uploading a arch/ubuntu iso, I guess there are a lot of seeders with more than 60Mbit upload like me, tough I only hit like 2Mbit up at max, mostly only kbit/s.

After switching to protonVPN, with nat-pmp using wireguard and natpmpc as backend, I cannot get ANY upload, like litterally 0 not even a single bit.

I set up protonvpn, curl ip.me returns my protonvpn IP, I tested natpmp (public port) with a python script that returns text on successfull connection, and from a different machine I telneted that port and my VPN IP and got the message, so public port mapping is working.

I set qBittorrent to the public port displayed here: (attatchment pubport)

Download is also working fine, I just cannot get upload to work.

I have not set any upload limits, adblockers have been disabled. qBittorrent log shows no errors.

qBittorrent frontend looks like this: (attatchment seeding).

Thanks for any help/tips on how to debug this further, can't get why I woun't get ANY upload at all, and I really do not wanna be a leecher.

[bob2306]

3 out of 4 of those torrents don't appear to have anyone trying to download them. Note that in trackerless torrents seeds can appear in the peers column.

[CrazyWolf13]

bob2306 wrote:
> 3 out of 4 of those torrents don't appear to have anyone trying to download
> them.

While that may be true, I expect to at least get someone to download it when leaving it for 24hours on, I got not a single bit upload while leaving it over 2 days on seeding, so ther emust be something wrong.

[LilTroy]

Hi
I've set up qbittorrent nox on a LXC on my Proxmox Cluster, behind my Opnsense, behind my ISP router(opnsense as subnet router)(not sure if that matters.)

My qbittorren sometimes had upload but very always rather slow, but due to me uploading a arch/ubuntu iso, I guess there are a lot of seeders with more than 60Mbit upload like me, tough I only hit like 2Mbit up at max, mostly only kbit/s.

After switching to protonVPN, with nat-pmp using wireguard and natpmpc as backend, I cannot get ANY upload, like litterally 0 not even a single bit.

I set up protonvpn, curl ip.me returns my protonvpn IP, I tested natpmp (public port) with a python script that returns text on successfull connection, and from a different machine I telneted that port and my VPN IP and got the message, so public port mapping is working.

I set qBittorrent to the public port displayed here: (attatchment pubport)

Download is also working fine, I just cannot get upload to work.

I have not set any upload limits, adblockers have been disabled. qBittorrent log shows no errors.

qBittorrent frontend looks like this: (attatchment seeding).

Thanks for any help/tips on how to debug this further, can't get why I woun't get ANY upload at all, and I really do not wanna be a leecher.

Why use telnet and a python script to test connectivity? That's what netcat was developed for. You're mapping the same port over both TCP & UDP but telnet will only test TCP. I assume that your python script is for testing UDP? Run the “ss” command and check the socket statistics under qBittorrent's PID. Make sure that particular port is bound for UDP and is in the listening state for TCP. When you run natpmpc in your terminal are you looping it so that your port mappings are preserved? If not then they'll expire after only 1 minute. You can use the WHILE loop below.

Code: Select all

while true ; do date ; natpmpc -a 1 0 udp 60 -g 10.2.0.1 && natpmpc -a 1 0 tcp 60 -g 10.2.0.1 || { echo -e "ERROR with natpmpc command \a" ; break ; } ; sleep 45 ; done

I have no idea why Proton doesn't just build the NAT-PMP client into their Linux VPN app? It's in their Windows VPN client. I also think it's quite strange that they're using PMP in the first place. It was only designed to be used on consumer-grade equipment. The protocol's successor, Port Control Protocol (PCP), is used with carrier-grade equipment which is what their infrastructure actually consists of.

Also, for future reference, you don't need to redact the epoch info in your screenshot. It's just a Unix timestamp. You shouldn't use the blur effect (pixelization), either. Instead draw a solid black bar over the image text or sensitive area you'd like to censor. It's possible to completely reverse the blur effect via brute-force and recover the original information. This includes fogging.

• https://bishopfox.com/blog/unredacter-t ... pixelation

• Researchers Have Created a Tool That Can Perfectly Depixelate Faces