Details/info: qBittorrent v.3.3.16, Windows 10 64-bit Version 1803 (OS Build 17134.112) desktop, Ethernet connection, Linksys Router X6200, VPN (PIA v81).
I reside in Thailand and for optimal connection speed am using Singapore or Hong Kong server; PIA VPN does not support/provide port-forwarding for these servers.
Following the suggestion made by forum moderator Switeck I am actively pursuing a correct method to Port Forward port (51967) on my Linksys Router.
I consulted the straightforward instruction as shown in:
https://portforward.com/linksys/x6200/
And
https://portforward.com/networking/stat ... ows-10.htm
However, my endeavor came to an abrupt halt because of conflicting information produced by 'ipconfig /all' viz:
> Under 'Ethernet adapter Ethernet' the numbers for Default Gateway do NOT show.
> Under 'Ethernet adapter Local Area Connection' the numbers for Default Gateway Do show.
I was uncertain which collection of data to be used and/or on obtaining the missing default Gateway numbers to complete the Port Forwarding task.
Well, since this is an issue not really related to qBittorrent I searched for advise in other fora of which the responses are just as confusing (for me anyway).
I was advised:
# The default gateway is entirely up to you as to what is used, so long as you use something in one of the 2 below ranges of IP Addresses (you would assign this IP Address in your router settings)
# If the BitTorrent traffic is going through the VPN, your router doesn't know anything about it. The only traffic it knows about is that which comes in on whatever port the VPN software uses. You can forward all the ports you want, but if the application is using the VPN, it won't matter.
And other info I found:
# Port forwarding is useful for torrents only as far as I know. In fact, I would go so far as to say it is required for torrents. Without port forwarding you simply cannot upload data. (Meaning you cannot seed.)
# Port forwarding does reduce anonymity. But in most cases it is so trivial a difference that you may as well ignore it. Depending on your torrent client, it may entirely disregard your VPN and use another interface. I think that is the main problem with uTorrent. It will use any interface it can latch onto with complete and total ignorance of what you tell it to use. That is why I use qBittorrent as my client. I can tell it to use only a single network interface and it will not fall back to another if that one fails.
AFAIC all this is somehow in disagreement and thus far didn't help me to accomplish my original task.
When on the Internet the PIA VPN is always connected to (Singapore) 196.52.34.13; (start application at login, auto-connect on launch).
FYI: In Network Connection, the Ethernet is shown as 'Unidentified network'.
My qBittorrent client is seeding.
I'd be most grateful if the resident experts would advise on which avenue to follow to complete Port Forwarding.
Port Forward the port used for incoming connection [Solved]
-
Kay
Port Forward the port used for incoming connection [Solved]
Last edited by Kay on Sat Jun 23, 2018 11:08 pm, edited 1 time in total.
-
Switeck
Re: Port Forward the port used for incoming connection.
"PIA VPN does not support/provide port-forwarding for these servers."
If a VPN does not provide port forwarding, you won't get any incoming connections while using it.
"You can forward all the ports you want, but if the application is using the VPN, it won't matter."
Port forwarding your router will then mean traffic may come in on it which bypasses your VPN connection...defeating any "security" it may offer, at least if qBitTorrent responds to traffic not through the VPN.
So it might matter, but not in a useful way.
"Depending on your torrent client, it may entirely disregard your VPN and use another interface."
qBitTorrent may do that as well if it's not bound to the VPN in qBT's advanced settings.
"Port forwarding is useful for torrents only as far as I know."
Some old LAN-based multiplayer games require port forwarding to work if played over the internet.
"Without port forwarding you simply cannot upload data. (Meaning you cannot seed.)"
Not totally true, although it's sort-of true if you're using private trackers with required minimum upload-vs-download ratios.
A firewalled seed (or peer with parts other peers are missing) can upload to other peers provided it can make an outgoing connection to them. This is impossible if THEIR firewall blocks the firewalled seed.
So, a firewalled seed and firewalled peer cannot normally connect to each other. There is a special way using uTP connections those can connect to each other, (UDP-based STUN) but they require the help of unfirewalled peers/seeds to do so.
On a torrent with lots of unfirewalled peers, a firewalled seed could connect and upload to ALL of them.
But on a private tracker, by the time a firewalled seed could attempt to connect to unfirewalled peers they will likely be seeds as well and no uploading will happen.
(btw, I'm not a moderator here)
If a VPN does not provide port forwarding, you won't get any incoming connections while using it.
"You can forward all the ports you want, but if the application is using the VPN, it won't matter."
Port forwarding your router will then mean traffic may come in on it which bypasses your VPN connection...defeating any "security" it may offer, at least if qBitTorrent responds to traffic not through the VPN.
So it might matter, but not in a useful way.
"Depending on your torrent client, it may entirely disregard your VPN and use another interface."
qBitTorrent may do that as well if it's not bound to the VPN in qBT's advanced settings.
"Port forwarding is useful for torrents only as far as I know."
Some old LAN-based multiplayer games require port forwarding to work if played over the internet.
"Without port forwarding you simply cannot upload data. (Meaning you cannot seed.)"
Not totally true, although it's sort-of true if you're using private trackers with required minimum upload-vs-download ratios.
A firewalled seed (or peer with parts other peers are missing) can upload to other peers provided it can make an outgoing connection to them. This is impossible if THEIR firewall blocks the firewalled seed.
So, a firewalled seed and firewalled peer cannot normally connect to each other. There is a special way using uTP connections those can connect to each other, (UDP-based STUN) but they require the help of unfirewalled peers/seeds to do so.
On a torrent with lots of unfirewalled peers, a firewalled seed could connect and upload to ALL of them.
But on a private tracker, by the time a firewalled seed could attempt to connect to unfirewalled peers they will likely be seeds as well and no uploading will happen.
(btw, I'm not a moderator here)
-
Kay
Re: Port Forward the port used for incoming connection.
My post wasn't intended to provoke any hostility towards your goodself; I sincerely value your advice!
Please my accept apologies if you interpreted my post as unfriendly; Rest assured that it wasn't meant that way at all!
I merely was presenting the responses received and articles researched to find out which of the (conflicting) data to be used as produced by 'ipconfig /all'; I did not expect you to respond to these.
It's very frustrating that nobody offered an explanation other than 'default gateway is entirely up to you' and frankly was hoping receiving a little a help here.
Again, it never was on my mind causing aggravation.
Please my accept apologies if you interpreted my post as unfriendly; Rest assured that it wasn't meant that way at all!
I merely was presenting the responses received and articles researched to find out which of the (conflicting) data to be used as produced by 'ipconfig /all'; I did not expect you to respond to these.
It's very frustrating that nobody offered an explanation other than 'default gateway is entirely up to you' and frankly was hoping receiving a little a help here.
Again, it never was on my mind causing aggravation.
-
Switeck
Re: Port Forward the port used for incoming connection.
You haven't offended me, I just don't want to lead you and others reading this message thread down an incorrect path concerning problems of VPN and port forwarding.
If you're using a VPN that doesn't offer port forwarding, you can't fix that by anything you do.
I didn't answer the "default gateway is entirely up to you" issue because I wasn't sure exactly what that meant either. It could mean the VPN provider doesn't care what you connect to the VPN as long as you're using the 2 correct VPN ips to do it. Or I have no idea.
"Modern" (in quotes because some are quite old) online multiplayer games get around needing the players to be port forwarded so their computers accept incoming connections because everyone connects through a central server. That central server (or servers!) has to handle everyone's network traffic for the game -- and it can be enormous in the case of massively multiplayer games, such as fantasy worlds with 1000's of players online at once!
Maybe I should've used a
with my not a moderator comment? 
If you're using a VPN that doesn't offer port forwarding, you can't fix that by anything you do.
I didn't answer the "default gateway is entirely up to you" issue because I wasn't sure exactly what that meant either. It could mean the VPN provider doesn't care what you connect to the VPN as long as you're using the 2 correct VPN ips to do it. Or I have no idea.
"Modern" (in quotes because some are quite old) online multiplayer games get around needing the players to be port forwarded so their computers accept incoming connections because everyone connects through a central server. That central server (or servers!) has to handle everyone's network traffic for the game -- and it can be enormous in the case of massively multiplayer games, such as fantasy worlds with 1000's of players online at once!
Maybe I should've used a
with my not a moderator comment? -
Kay
Re: Port Forward the port used for incoming connection.
Okay; I am glad you didn't perceive my post as offensive - Peace!
In relation to the Port Forward issue while connected to a (PIA) VPN, I really don't know what am missing as am unable to reconcicle your two messages viz:
1. You should look up how to port forward the port qBitTorrent is listening on (its incoming port) on your Linksys router. The port needs to be forwarded to your computer's LAN ip
2. If you're using a VPN that doesn't offer port forwarding, you can't fix that by anything you do.
I stick to #2 - I'd better give up the Port Forward idea as causes headaches and the old version of qBittorrent is working satisfactory. Cheers.
In relation to the Port Forward issue while connected to a (PIA) VPN, I really don't know what am missing as am unable to reconcicle your two messages viz:
1. You should look up how to port forward the port qBitTorrent is listening on (its incoming port) on your Linksys router. The port needs to be forwarded to your computer's LAN ip
2. If you're using a VPN that doesn't offer port forwarding, you can't fix that by anything you do.
I stick to #2 - I'd better give up the Port Forward idea as causes headaches and the old version of qBittorrent is working satisfactory. Cheers.
-
Switeck
Re: Port Forward the port used for incoming connection.
To clarify, those are 2 different and sadly unrelated scenarios for you:
1.When you're using a direct internet connection as opposed to a VPN, you want your direct internet connection's IPv4 ip address forwarded to your computer -- and that means port forwarding your Linksys router to your computer's LAN ip and then qBitTorrent would get incoming connections.
2.But with the VPN, the VPN's end IPv4 ip address (that you connect to/through) is what needs to be port forwarded...and that's something THEY (the company running the VPN) have to do because you do not have configuration access to their networking equipment.
If they say they don't provide port forwarding, there's nothing you can do.
1.When you're using a direct internet connection as opposed to a VPN, you want your direct internet connection's IPv4 ip address forwarded to your computer -- and that means port forwarding your Linksys router to your computer's LAN ip and then qBitTorrent would get incoming connections.
2.But with the VPN, the VPN's end IPv4 ip address (that you connect to/through) is what needs to be port forwarded...and that's something THEY (the company running the VPN) have to do because you do not have configuration access to their networking equipment.
If they say they don't provide port forwarding, there's nothing you can do.
-
Kay
Re: Port Forward the port used for incoming connection.
[quote="Switeck"]
To clarify, those are 2 different and sadly unrelated scenarios for you:
1.When you're using a direct internet connection as opposed to a VPN, you want your direct internet connection's IPv4 ip address forwarded to your computer -- and that means port forwarding your Linksys router to your computer's LAN ip and then qBitTorrent would get incoming connections.
2.But with the VPN, the VPN's end IPv4 ip address (that you connect to/through) is what needs to be port forwarded...and that's something THEY (the company running the VPN) have to do because you do not have configuration access to their networking equipment.
If they say they don't provide port forwarding, there's nothing you can do.
[/quote]
Thanks for clarifying these points.
I modify my original post and add [Solved] beside the topic.
To clarify, those are 2 different and sadly unrelated scenarios for you:
1.When you're using a direct internet connection as opposed to a VPN, you want your direct internet connection's IPv4 ip address forwarded to your computer -- and that means port forwarding your Linksys router to your computer's LAN ip and then qBitTorrent would get incoming connections.
2.But with the VPN, the VPN's end IPv4 ip address (that you connect to/through) is what needs to be port forwarded...and that's something THEY (the company running the VPN) have to do because you do not have configuration access to their networking equipment.
If they say they don't provide port forwarding, there's nothing you can do.
[/quote]
Thanks for clarifying these points.
I modify my original post and add [Solved] beside the topic.