From 4c17989711a76866214f71f645fdf8fe785c15ad Mon Sep 17 00:00:00 2001 From: mms Date: Tue, 5 Dec 2023 11:57:10 +0100 Subject: chore: extract old blog posts to section --- .../2023/always-have-the-entire-network-in-mind.md | 25 ---------------------- 1 file changed, 25 deletions(-) delete mode 100644 content/2023/always-have-the-entire-network-in-mind.md (limited to 'content/2023/always-have-the-entire-network-in-mind.md') 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 ---- -{{}} -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. -- cgit v1.2.3