Hello.
I am an opensuse user for a little bit more than a month now. Overall I am kind of new to linux, being a linux user for less than a year. Leap 42.2 works fantastic for me and it is exactly what I want, currently being my main OS. Since I installed it I encountered no problems at all. But there is just this one thing that bothers me… I still believe the problem is due to my lack of knowledge and competence. That’s why I’m asking for help.
Ok, so I use openSuSE Leap 42.2 with KDE. I installed Ktorrent right after installing openSuSE. I downloaded few things and it did what it was supposed to while downloading, but after downloading it refused to upload(seed). It’s uploading very rarely and for a very short duration. I tried to upload a torrent that I know for sure has huge demand for seeding. I tried to upload this same torrent from different distros and computers and in all cases it worked. I’m sure there is demand for downloading. I tried to change the default port from ktorrent settings, but it didn’t solve the problem. I downloaded qbittorrent tried to upload from it… and it still didn’t work.
When I tried to change the ports in ktorrent I changed them with the default that qbittorrent came with. To be honest I’m not very familiar with networking and so on…
This problem exists for every torrent downloaded.
By default in ktorrent settings under ports & limits:
Port: 6881
UDP tracker port: 8888
According to this site: http://portchecker.co/
Both of them are closed… what confuses me is that this site actually shows all my ports as closed. No matter which one I try.
I am not sure what causes this problem, but I’m pretty sure it’s because of my lack of competence. Maybe I should be able to resolve it using YaST, but I do not know how to do so.
Thanks in advance to anyone who can help me or atleast give me a hint of what I should try to do.
MainBattleDank schrieb:
>
>
> By default in ktorrent settings under ports & limits:
> Port: 6881
> UDP tracker port: 8888
>
> According to this site:
> http://portchecker.co/
> Both of them are closed… what confuses me is that this site actually
> shows all my ports as closed. No matter which one I try.
> I am not sure what causes this problem, but I’m pretty sure it’s because
> of my lack of competence. Maybe I should be able to resolve it using
> YaST, but I do not know how to do so.
> Thanks in advance to anyone who can help me or atleast give me a hint of
> what I should try to do.
Most likely a firewalling and/or port forwarding issue, you have to allow
incoming traffic on those ports.
Depending on how you are connected this means allowing these connections not
only for your client (SuSEfirewall2) but also in your router (port forwarding).
Without allowing incoming connections, seeding is still possible but in most
cases rare and slow (which matches your description quite well).
AK
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
For the following, you should know about some terminology
torrent file - It’s not the shared file itself, it’s a tiny file which only contains a description of the file that is being shared.
shared file - This is the actual file with content you want to share
tracker - A well known server typically with its own URL that stores and serves torrent files.
DHT, Peer Sharing - Alternatives to using a well known tracker which can be vulnerable to attacks. Instead, torrent clients are given the capability to themselves act as torrent file servers, so it’s far more resistant to attacks, but to find a specific torrent file can be problematic.
Whenever you deploy a machine acting as a Server on the Internet, you need to
Open up firewall ports for your service As others have noted, you may have firewalls on your machine (openSUSE) and your router gateway.
Typically, your home machine will not be assigned a public IP address and will be assigned a private address with NAT configured on your gateway router. The reason why private IP address networks work is that they are not addressable on the Internet. You have two solutions…
You can configure address forwarding on your Gateway router to your home machine. This will require your home machine running ktorrent to be assigned a permanent address which can be done one of two ways… Configure a static IP address or configure a DHCP assigned lease (preferred when possible, see your gateway router documentation).
Assign a public IP address to your home machine. See your gateway router instructions.
Of course, make sure that the service is running on your machine. In your case, this would be simply done by making sure ktorrent is running, and your file is configured to be shared.
Beyond the above, there are some things you need to configure that are specific to torrents…
When you are the original seeder, you need to typically set up a method for people to know about your torrent file. You start off by creating a torrent file as you’ve probably done which is a plain text file that describes a number of things like if you are registered with any trackers, any special methods which might be supported like DHT and peer sharing and the file itself… name, number of chunks, chunk size, hash strings, etc.
Although you can distribute the above torrent file any way you wish (email, from a website, twitter, etc), the most reliable and usual way is to register and upload a copy of your torrent file (not the shared file itself) to a tracker. After that, all people need to do is query the tracker to find your torrent file which is downloaded, and then their torrent client can try to contact others sharing the file whom the tracker knows about.
Without a tracker, DHT and Peer sharing set up every machine that has your torrent file as a mini-tracker, but because they are not easily discovered may take a lot longer to provide information for others. So, for instance even if you didn’t set up your port forwarding correctly, <some> other nodes will still find your machine and download your file if they support DHT and Peer Sharing.
Any breakdown in any of the above will prevent your machine from working as a Seeder.