Seeding requires port forwarding. Downloading doesn’t require port forwarding.
You think that seeding doesn’t work without manual port forwarding - - that’s incorrect. Seeding works with automatic port forwarding. But you don’t know this because you haven’t ever done it. You don’t even use Mullvad for torrenting know whether seeding works with it.
Wrong again. I just told you how seeding can work without port forwarding of any kind. You’re just parroting babble you clearly have no understanding about. I mean it’s pretty obvious to us you’re out of your depth.
No. When behind a firewall, port forwarding is required for seeding. The only time when port forwarding isn’t necessary for seeding is when a client ISN’T behind a firewall. Virtually every consumer grade router has a firewall enabled by default. That means everyone who uses such a router while seeding must have some form of port forwarding enabled in order for seeding to work.
Again, Mullvad blocks “manual” port forwarding. Thus, in order to seed on Mullvad when behind a firewall, automatic port forwarding must be enabled in order for seeding to work Otherwise, incoming connections wouldn’t work at all. A router firewall that doesn’t support automatic port forwarding cannot seed when using Mullvad.
You persist on your ignorance, incredible. I’m already tired of telling you that whatever you say about routers are meaningless when applied to a VPN tunnel. Second, I’ve also shown you how you can seed using outbound only connections, which does not require port-forwarding. RTFM.
Now you can choose to learn, or you can choose to ignore everything we’ve told you and remain looping the same funny text about “automatic port forwarding”. Like the the other user said, pretty sure you saw your port closed when you checked the website, so why keep the techbro jig up my dude?
Outbound connections are for downloading, inbound connections are for seeding. When behind a firewall, an inbound connection won’t work unless a port is forwarded. Users can’t connect to a Plex server behind a firewall unless a port on the firewall is manually forwarded. This is why Mullvad doesn’t work with Plex servers are behind a firewall. Unlike Plex, bittorent does care about which port is on the firewall is forwarded. That’s why seeding on Mullvad works with automatic port forwarding, and not “manual” port forwarding. Seeding behind a firewall requires that an inbound connection can penetrate the firewall through a forwarded port. Because Mullvad doesn’t permit manual port forwarding, seeding doesn’t work with a router unless the router supports automatic port forwarding.
I explained why seeding on Mullvad works with automatic port forwarding, but not manual router port forwarding. Yet you keep insisting that seeding with Mullvad when behind a router doesn’t work - - that’s simply incorrect. Seeding from behind a router with Mullvad does in fact work without manual port forwarding. I know this because I’ve actually done it myself.
That’s why seeding on Mullvad works with automatic port forwarding, and not “manual” port forwarding.
Mullvad does not support port forwarding in any form. Not automatic. Not manual. I’ve already said that multiple times. But since you don’t believe me, maybe you’ll believe Mullvad themselves?
If you’re still skeptical, go ahead and ask them yourself:
So what’s more likely - that seeding works on Mullvad because seeding simply doesn’t require port forwarding (as a multitude of sources have already told you), or because of the convoluted explanation you made up in your head that depends on a feature the VPN provider says they don’t support?
Your first statement is wrong so I stopped reading there. Inform yourself, I already gave you the links where you can learn more and see how you’re able to seed using outbound connections. We know you have no idea what you’re talking about, don’t waste my time further. Cheers
Mullvad does not support port forwarding in any form. Not automatic. Not manual. I’ve already said that multiple times. But since you don’t believe me, maybe you’ll believe Mullvad themselves?
I’m a Mullvad customer who torrents with their VPN. Do you even use a VPN while torrenting? If so, then you know that port forwarding is required to allow incoming connections through the VPN when behind a firewall. Mullvad doesn’t support MANUAL port forwarding. Thus, Mullvad is useless to firewall users that can’t implement AUTOMATIC port forwarding. Nonetheless, Mullvad allows torrenting. AUTOMATIC port forwarding is the only way that an incoming connection can pass through Mullvad’s VPN when behind a firewall.
You keep repeating the same gibberish while ignoring every source I provide that refutes you.
You act like a VPN can allow all incoming connections through a firewall by default without port forwarding. That defeats the purpose of a VPN - - It doesn’t make any sense whatsoever.
Go back and read this and try again.
You didn’t post any links to your sources.
Since you know so much, explain how incoming connections via a VPN can penetrate a firewall without port forwarding.
I’ll wait.
There are links for every quote. Try clicking the blue text genius.
None of the information that you posted answers my question. My answer includes: (1) a firewall, and (2) VPN used TOGETHER - - not one or the other.
Let’s start by revisiting your previous statement of “Outbound connections are for downloading, inbound connections are for seeding.” Which is completely nonsensical. You don’t seem to understand how the internet works on a basic level, so it’s no surprise you’re getting tripped up by how port forwarding interplays with that. Your entire mental model is wrong.
There’s no such thing as inbound or outbound connections. There are inbound or outbound requests to establish a connection. And once a connection is established, it’s a two-way street. Data can flow either direction and it doesn’t matter which side initiated it originally. This concept is what allows the internet to function as we know it.
Firewall rules dictate whether the initial requests are allowed to pass through. If you have closed ports, then inbound requests are all denied and you must rely solely on sending outbound requests to find a peer. Those outbound requests can only be received by peers who have port forwarding enabled themselves. This is the “passive vs active” mode I previously referenced. But again, once a connection is established, you can both send and receive data freely (download and upload).
I’m not sure why you think adding in a VPN changes things. Conceptually, it all behaves exactly the same. Except instead of your traffic exiting on your home router, it’s sent through a tunnel to the VPN server. So now your traffic is subject to the VPN’s firewall rules instead of your home router’s (which only sees an encrypted data stream). The VPN connection itself may use certain ports to establish the tunnel, but that doesn’t apply to the encapsulated data.