summaryrefslogtreecommitdiff
path: root/content/2023/always-have-the-entire-network-in-mind.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/2023/always-have-the-entire-network-in-mind.md')
-rw-r--r--content/2023/always-have-the-entire-network-in-mind.md25
1 files changed, 0 insertions, 25 deletions
diff --git a/content/2023/always-have-the-entire-network-in-mind.md b/content/2023/always-have-the-entire-network-in-mind.md
deleted file mode 100644
index f95fa51d..00000000
--- a/content/2023/always-have-the-entire-network-in-mind.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: "Always Have the Entire Network in Mind"
-category: engineering
-abstract: fixing torrent by fixing the network config
-date: 2023-03-08T14:46:19+01:00
-year: 2023
-draft: false
-tags:
-- deluge
-- rtorrent
-- synology
-- unify
-- firewall
-- sysadmin
----
-{{<img-pull-right "bittorrent-logo.png" "BitTorrent 4 lyfe">}}
-Recently I moved my torrenting from Synology's Download Station to dedicated programs inside Docker - first Deluge, now rTorrent. And it was slow, impossibly slow. Those clients even had problems getting the real names of the torrents, not to mention connecting to any clients.
-
-Guess what the problem was.
-
-Of course, as always, it was the sysadmin.
-
-Synology is plug-and-play enough to use UPnP. My poor docker-locked clients did not. I needed to create a forwarding rule on my router which would point the port to the Synology and configure Docker to forward the port to the Docker container.
-
-I am not a smart admin.