commit b2cc8371b83c4ae7023f52a0c038aee2568cdfe7 parent 4f4f989c464df8f90fbeb6f2239751c8a1f3cd19 Author: Michał M. Sapka <michal@sapka.me> Date: Wed, 8 Mar 2023 14:51:16 +0100 feat: article for 2023-08-08 Diffstat:
4 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/assets/content_images/bittorrent-logo.png b/assets/content_images/bittorrent-logo.png Binary files differ. diff --git a/content/2023/always-have-the-entire-network-in-mind.md b/content/2023/always-have-the-entire-network-in-mind.md @@ -0,0 +1,25 @@ +--- +title: "Always Have the Entire Network in Mind" +category: "software" +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 now. 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. diff --git a/resources/_gen/images/bittorrent-logo_hu20ac0ac79972c8b309ffeba358af0315_14997_150x0_resize_q75_h2_box_3.webp b/resources/_gen/images/bittorrent-logo_hu20ac0ac79972c8b309ffeba358af0315_14997_150x0_resize_q75_h2_box_3.webp Binary files differ. diff --git a/resources/_gen/images/bittorrent-logo_hu20ac0ac79972c8b309ffeba358af0315_14997_300x0_resize_q75_h2_box_3.webp b/resources/_gen/images/bittorrent-logo_hu20ac0ac79972c8b309ffeba358af0315_14997_300x0_resize_q75_h2_box_3.webp Binary files differ.
