<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[punkt.codes blog]]></title><description><![CDATA[Dive into the raw, unfiltered journey of a blogger navigating the tech world. Experience the highs and lows of coding, tech projects, 3D printing and anything in between.]]></description><link>https://punkt.codes</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1704456051546/A9Vw04Yly.png</url><title>punkt.codes blog</title><link>https://punkt.codes</link></image><generator>RSS for Node</generator><lastBuildDate>Sat, 11 Apr 2026 23:02:46 GMT</lastBuildDate><atom:link href="https://punkt.codes/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Fixing errors during patching of the Veeam Recovery Media in combination with tmpfs /tmp]]></title><description><![CDATA[If you try to patch the Recovery Media in Veeam Agent for Linux, you might encounter the following or a similar error:

The reason for it is most likely that your system uses tmpfs for /tmp and runs out of space during the patching process.
In my cas...]]></description><link>https://punkt.codes/fixing-errors-during-patching-of-the-veeam-recovery-media-in-combination-with-tmpfs-tmp</link><guid isPermaLink="true">https://punkt.codes/fixing-errors-during-patching-of-the-veeam-recovery-media-in-combination-with-tmpfs-tmp</guid><category><![CDATA[Tuxedo OS]]></category><category><![CDATA[tempfs]]></category><category><![CDATA[veeam]]></category><category><![CDATA[Ubuntu]]></category><category><![CDATA[Ubuntu 22.04]]></category><dc:creator><![CDATA[Patsch]]></dc:creator><pubDate>Tue, 07 May 2024 12:55:40 GMT</pubDate><content:encoded><![CDATA[<p>If you try to patch the Recovery Media in Veeam Agent for Linux, you might encounter the following or a similar error:</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1715086401542/c62bf720-b4ce-42e6-a8da-ffe30f5ae685.png" alt class="image--center mx-auto" /></p>
<p>The reason for it is most likely that your system uses <code>tmpfs</code> for <code>/tmp</code> and runs out of space during the patching process.</p>
<p>In my case, I encountered this issue when using the free <a target="_blank" href="https://www.veeam.com/linux-backup-free.html">Veeam Agent for Linux</a> on a system that is running <a target="_blank" href="https://www.tuxedocomputers.com/en/TUXEDO-OS_1.tuxedo">TUXEDO OS</a>, which is based on Ubuntu 22.04 LTS.</p>
<p>To fix the issue, I created a separate directory on my root drive and assigned it within the <code>[core]</code> section of the <code>veeam.ini</code> config file as <code>tempFolder</code>.</p>
<p>To do so follow this steps:</p>
<ol>
<li><p>Create the separate directory (you can basically create it wherever you want, just make sure you have enough free disk space at its location):<br /> <code>sudo mkdir /.veeam-tmp</code></p>
</li>
<li><p>Open the Veeam config file /etc/veeam/veeam.ini and add the line <code>tempFolder = /.veeam-tmp</code> within the [core] section:</p>
<pre><code class="lang-plaintext"> ...
 [core]
 ...
 # Custom temp folder
 tempFoler = /.veeam-tmp
</code></pre>
</li>
</ol>
<p><mark>Note:</mark> to patch the Recovery Media you also need to install the package <code>squashfs-tools</code> manually, otherwise you will receive an error as well. To do so execute:</p>
<p><code>sudo apt install sqashfs-tools</code></p>
]]></content:encoded></item><item><title><![CDATA[How to Debug WireGuard: Enabling Kernel Logging]]></title><description><![CDATA[WireGuard, as far as I know, does not create log files, which can make it difficult to troubleshoot issues with the AllowedIPs configuration, particularly when not all traffic is intended to be routed through the tunnel.
However, as a kernel module, ...]]></description><link>https://punkt.codes/how-to-debug-wireguard-enabling-kernel-logging</link><guid isPermaLink="true">https://punkt.codes/how-to-debug-wireguard-enabling-kernel-logging</guid><category><![CDATA[wireguard]]></category><category><![CDATA[vpn]]></category><dc:creator><![CDATA[Patsch]]></dc:creator><pubDate>Mon, 19 Feb 2024 17:23:28 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/stock/unsplash/4Mw7nkQDByk/upload/8a526220b074d91ac683fbeebb2c80d5.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>WireGuard, as far as I know, does not create log files, which can make it difficult to troubleshoot issues with the <code>AllowedIPs</code> configuration, particularly when not all traffic is intended to be routed through the tunnel.</p>
<p>However, as a kernel module, it is possible to enable verbose logging for this module. To enable kernel logging, execute this command:</p>
<pre><code class="lang-bash"><span class="hljs-built_in">echo</span> <span class="hljs-string">"module wireguard +p"</span> | sudo tee /sys/kernel/debug/dynamic_debug/control
</code></pre>
<p>The log messages will be recorded in the kernel log, which can be monitored using:</p>
<pre><code class="lang-bash">sudo dmesg -wT
</code></pre>
<p>To disable logging, run:</p>
<pre><code class="lang-bash"><span class="hljs-built_in">echo</span> <span class="hljs-string">"module wireguard -p"</span> | sudo tee /sys/kernel/debug/dynamic_debug/control
</code></pre>
<p>In conclusion, debugging WireGuard can be facilitated by enabling kernel logging. This allows the capture and recording of log messages within the kernel log, which can then be monitored. It's important to remember to disable logging once done.</p>
]]></content:encoded></item></channel></rss>