<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Homelab on Jonas&#39; Blog</title>
    <link>https://log.jnsmr.ch/categories/homelab/</link>
    <description>Recent content in Homelab on Jonas&#39; Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 27 Mar 2026 22:00:00 +0100</lastBuildDate>
    <atom:link href="https://log.jnsmr.ch/categories/homelab/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Wake-on-GPIO</title>
      <link>https://log.jnsmr.ch/post/2026-03-27-wake-on-gpio/</link>
      <pubDate>Fri, 27 Mar 2026 22:00:00 +0100</pubDate>
      <guid>https://log.jnsmr.ch/post/2026-03-27-wake-on-gpio/</guid>
      <description>&lt;p&gt;Alternative title: How to spend an afternoon at Bastli.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Wake-on-LAN has a few issues that I personally don&amp;rsquo;t like.&#xA;The primary thing that I don&amp;rsquo;t like is that it relies on the mainboard and network interface to be not-quite-shutdown.&#xA;This leads to some unnecessary power draw while the PC/server is supposed to be shut down.&lt;/p&gt;&#xA;&lt;p&gt;In addition to that, the way WOL works bothers me.&#xA;Basically, the OS needs to shut down in a very specific way and instruct the NIC to wait for WOL-packets. Every single time.&#xA;It is &lt;em&gt;not&lt;/em&gt; a one-off configuration option that is stored on a NIC (at least not on my hardware).&#xA;This leads to WOL not working when a PC didn&amp;rsquo;t experience a clean shutdown.&#xA;This happened to me multiple times, sometimes because power went out for a bit, other times simply because the PC crashed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stuff I&#39;ve spent entirely too much time on during the last 2 weeks</title>
      <link>https://log.jnsmr.ch/post/2025-12-05-networking-overkill/</link>
      <pubDate>Fri, 05 Dec 2025 11:25:00 +0100</pubDate>
      <guid>https://log.jnsmr.ch/post/2025-12-05-networking-overkill/</guid>
      <description>&lt;p&gt;This blog post comes in two variants, based on a simple condition.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Are you my thesis supervisor: I&amp;rsquo;ve done lots of thesis :) this blog post is finished now.&lt;/li&gt;&#xA;&lt;li&gt;Otherwise: keep reading&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Recently I stumbled upon my old NAS.&#xA;It&amp;rsquo;s been turned off since a while, and I really had no clue what&amp;rsquo;s on it.&#xA;However, I decided I should integrate it in my &amp;ldquo;homelab&amp;rdquo;.&#xA;The homelab I had at that point consisted exclusively of one old desktop computer at my parents place.&#xA;Further, the computer is directly connected to the ISP router, and essentially everything I accessed was over the public internet (with good credentials of course).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self Hosting Gitea</title>
      <link>https://log.jnsmr.ch/post/2023-03-19-self-hosting-gitea/</link>
      <pubDate>Sun, 19 Mar 2023 22:13:00 +0000</pubDate>
      <guid>https://log.jnsmr.ch/post/2023-03-19-self-hosting-gitea/</guid>
      <description>&lt;p&gt;Some time ago I decided I want to take matters into my own hands and host my own code.&#xA;I was aware of a few git hosting services: GitHub, GitLab, BitBucket, and Gitea.&lt;/p&gt;&#xA;&lt;p&gt;GitHub was no option, as you can&amp;rsquo;t self-host that.&lt;/p&gt;&#xA;&lt;p&gt;I was not very familiar with GitLab, and it looked clunky, big, and slow to me.&lt;/p&gt;&#xA;&lt;p&gt;BitBucket I was not a fan of due to it being product of an Australian company. &lt;a href=&#34;https://fee.org/articles/australia-s-unprecedented-encryption-law-is-a-threat-to-global-privacy/&#34;&gt;See here why that might not be a good thing&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
