I think my Turris Omnia is interfering with my ability to seed torrents

  • I have a turris omnia
  • I have a server on the local network
  • I’m trying to seed a torrent with transmission-daemon
  • When I try to download the torrents with two different clients on the local network, it keeps starting for a while (seemingly) and then dropping the peer
  • I can see the peer first use my external IP and then it becomes my server’s internal IP and then it drops
  • One of the torrents was working great internally and externally and very quick/fast about a week ago.
  • I have done extensive troubleshooting on the server end–I’m convinced that’s not the problem
  • Since the server was seeding successfully a while ago, I have changed nothing on the router or server related to networking, really, that I’m aware of
  • The problem seems to be related to, possibly, maintaining peers

Update: I have masquerading enabled, but I cannot download the torrent I’m seeding, while others can! However, a week ago or more, I was able to download my own torrent from my server just fine. I think maybe the recent firmware update may have messed things up?

Another Update: One friend was able to download to 100%. Strangely. But now, another person isn’t able to download it at all.

So you have local peer discovery enabled ?

I’m not sure if Deluge nor Transmission have such an option. Just over a week ago maybe two or more, I was able to download it just fine on my network with Transmission.

I’ve even tried downloading it through VPN. I’ve also had a new friend try to download on their connection–they cannot, and yet a separate friend, yesterday, was able to. And whenever someone can’t download it, myself included, it seems to be about peer discovery.

The torrent is marked as public, if that’s what you mean.

UPDATE: I disabled ipv6 and I’m not sure if this is coincidence, but I think it’s all working now? Not for me inside the network, but for someone else.

ANOTHER UPDATE: no, my friend is in fact downloading it very inconsistent when they’re actually able to download, despite the server should always be seeding.

local peer discovery is disabled by default since it broadcasts torrent info across local network.

it will likely help in your case

lpd-enabled: Boolean (default = false)

Edit: should also be visible in gui

Yeah, I still can’t download it consistently. Even if I add my server IP (which I didn’t have to do before) it never pops up as a peer. I think others find the torrent to be very spotty. This is all very strange considering I don’t think any of my settings or router config is any different from a couple weeks ago or what have you and I wonder if the firmware update messed with things?

My friend was eventually able to download from my torrent but said it was spotty.

I believe the torrent is 100% legal, I could just post it here so others can test it out? It’s simply an archive of a church’s sermons from YouTube (they don’t have it monetized or anything).

UPDATE: oh wow, it finally started popping up as a peer on my local laptop client–thank you for your advice. I’ve noticed that before my torrent peer resolution was very quick but now it’s extremely slow to start seeding on the server. However, I saw it pop up, and then drop (my server as a peer). And it was seeding at a terribly slow speed.

Update: after killing transmission on my client machine, and letting deluge do its thing, my external IP is finally popping up as a peer and downloading like a madman.

Another update: ah, things have once again slowed down to a crawl. Like 0.1 K/s. I think this is what someone else was complaining about. And then it shot back up again? It is so strange. I have no idea what the fudge is going on.

Another update: and there we go, it dropped my local server from peers after dipping below 1 K/s. But then it came back above 1 M/s, and it’s falling again rapidly down to zero again and rinse wash repeat, sometimes dropping it as a peer. This seems to me to be some kind of weird traffic shaping or QoS thing or something?