From f301e09bc74ce8ebf1212798a2cfa62ca61ab157 Mon Sep 17 00:00:00 2001 From: bullshar-k <273740932+bullshar-k@users.noreply.github.com> Date: Wed, 5 Aug 2026 20:29:57 -0400 Subject: [PATCH] add card --- index.xml | 9 +- posts/adguard/index.html | 204 +++++++++++++++++++++++++++++++++++++ posts/index.html | 6 ++ posts/index.xml | 9 +- posts/wireguard/index.html | 2 +- sitemap.xml | 3 + 6 files changed, 230 insertions(+), 3 deletions(-) create mode 100644 posts/adguard/index.html diff --git a/index.xml b/index.xml index 4d8a080..cd7cfbe 100644 --- a/index.xml +++ b/index.xml @@ -39,7 +39,7 @@ http://localhost:1313/posts/wireguard/ Sat, 25 Jul 2026 00:00:00 +0000 http://localhost:1313/posts/wireguard/ - <h2 id="quick-guide">Quick guide</h2> <pre tabindex="0"><code>apt update &amp;&amp; apt upgrade apt install wireguard-tools git go iptables git clone https://github.com/bullshar-k/wg.conf cd wgconf go build main.go ./main -peer 10 -dest server_ip -port 51855 mv server.conf /etc/wireguard wg-quick up server </code></pre><p>From there you move the client 1-10 onto the appropriate clients and use wg-quick up on them too. Depending on your VPS you may need traffic forwarding post up rules like this;</p> <pre tabindex="0"><code>PostUp = iptables -A FORWARD -i server -j ACCEPT PostUp = iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i server -j ACCEPT PostDown = iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE </code></pre><p><em>If it isn&rsquo;t apparent this goes in the <code>[INTERFACE]</code> section after the interface info before the first <code>[PEER]</code> Ensure <code>server</code> is the name of the .conf file as that will be the name of the interface, and <code>eth0</code> is the name of your WAN facing NIC interface.</em></p> + <h2 id="quick-guide">Quick guide</h2> <pre tabindex="0"><code>apt update &amp;&amp; apt upgrade apt install wireguard-tools git go iptables git clone https://github.com/bullshar-k/wgconf cd wgconf go build main.go ./main -peer 10 -dest server_ip -port 51855 mv server.conf /etc/wireguard wg-quick up server </code></pre><p>From there you move the client 1-10 onto the appropriate clients and use wg-quick up on them too. Depending on your VPS you may need traffic forwarding post up rules like this;</p> <pre tabindex="0"><code>PostUp = iptables -A FORWARD -i server -j ACCEPT PostUp = iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i server -j ACCEPT PostDown = iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE </code></pre><p><em>If it isn&rsquo;t apparent this goes in the <code>[INTERFACE]</code> section after the interface info before the first <code>[PEER]</code> Ensure <code>server</code> is the name of the .conf file as that will be the name of the interface, and <code>eth0</code> is the name of your WAN facing NIC interface.</em></p> Self hosting monero node @@ -55,6 +55,13 @@ http://localhost:1313/posts/benchmark/ <p>Both tests were done separately, not in concurrency, with the same background activity on the host machine. Scores are difference from Arch - Artix. If the number is positive Arch scored higher. Percent diffs are calcualted as follows: 100(|diff|/arch&rsquo;s score)</p> <p>Gentoo wiki has an article with the breakdown comparison of these two @<a href="https://wiki.gentoo.org/wiki/Comparison_of_init_systems">Comparison of init systems</a></p> <hr> <h2 id="environment">Environment</h2> <table> <thead> <tr> <th>Ram</th> <th>Swap</th> <th>Storage</th> <th>Filesys</th> <th>DE</th> <th>Compiler</th> <th>Benchmark</th> </tr> </thead> <tbody> <tr> <td>16GiB</td> <td>None</td> <td>50GiB NVMe</td> <td>ext4</td> <td>none, TTY</td> <td>GCC 13.3.0</td> <td>FOSSbench</td> </tr> </tbody> </table> <hr> <h2 id="results">Results</h2> <table> <thead> <tr> <th>Native integer math</th> <th>Wide integer math</th> <th>Floating point math</th> <th>Prime numbers</th> <th>Extended instructions</th> <th>Compression</th> <th>Encryption</th> <th>Physics</th> <th>Sorting</th> <th>Memory latency</th> <th>Memory bandwidth</th> </tr> </thead> <tbody> <tr> <td>-514.3</td> <td>-689.5</td> <td>277</td> <td>-44.5</td> <td>492.2</td> <td>2079.9</td> <td>213</td> <td>78</td> <td>224</td> <td>-4</td> <td>15568.7</td> </tr> <tr> <td>-0.41%</td> <td>-0.59%</td> <td>1.34%</td> <td>-0.35%</td> <td>0.19%</td> <td>20.66%</td> <td>2.4%</td> <td>2.53%</td> <td>6.94%</td> <td>-5.39%</td> <td>9.04%</td> </tr> </tbody> </table> + + Adguard home + http://localhost:1313/posts/adguard/ + Sun, 28 Jun 2026 00:00:00 +0000 + http://localhost:1313/posts/adguard/ + <hr> <h2 id="installation-itself">Installation itself</h2> <p>Very easy, good jobs on the devs overall. My upstream is <code>9.9.9.9:853</code> and I have wireguard running on that VM so it proxies to one of my VPSes in another country.</p> <hr> <h2 id="mullvad-linux-client-lan-sharing">Mullvad linux client LAN sharing</h2> <p>It does NOT play nice. It does not let you use your own DNS even with lockdown mode off, LAN sharing on, and custom DNS enabled. DNS goes out and it doesn&rsquo;t get it back from adguard because mullvad actually never changes the interfaces DNS to the custom one. It only changes it to SEND dns queries, not RECEIVE, so you are effectively left WITHOUT DNS unless you set it manually like so.</p> + OPNsense http://localhost:1313/posts/opnsense/ diff --git a/posts/adguard/index.html b/posts/adguard/index.html new file mode 100644 index 0000000..2e091f5 --- /dev/null +++ b/posts/adguard/index.html @@ -0,0 +1,204 @@ + + + + + + + Adguard home - bullshark369.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+ +
+
+ +
+
+ +
+
+

Adguard home

+ +
+
+
+

Installation itself

+

Very easy, good jobs on the devs overall. My upstream is 9.9.9.9:853 and I have wireguard running on that VM so it proxies to one of my VPSes in another country.

+
+

Mullvad linux client LAN sharing

+

It does NOT play nice. It does not let you use your own DNS even with lockdown mode off, LAN sharing on, and custom DNS enabled. DNS goes out and it doesn’t get it back from adguard because mullvad actually never changes the interfaces DNS to the custom one. +It only changes it to SEND dns queries, not RECEIVE, so you are effectively left WITHOUT DNS unless you set it manually like so.

+
sudo resolvectl dns eno1 192.168.1.50
+sudo resolvectl domain eno1 "~."
+
+
+
+ +
+

@bullshark369.org maintained by shark

+ +
+ + + + + + + + + + + + + +
+ +
+ + + +
+ + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/posts/index.html b/posts/index.html index ef9463c..5c60d0d 100644 --- a/posts/index.html +++ b/posts/index.html @@ -137,6 +137,12 @@

A likely slightly innacurate benchmark of OpenRC vs SystemD in CPU math operations

+
+
Jun 28, 2026
+

Adguard home

+

Setting up adguard home, and mostly my issues with LAN sharing on Mullvad

+
+
Jun 19, 2026

OPNsense

diff --git a/posts/index.xml b/posts/index.xml index 2049159..abe9e19 100644 --- a/posts/index.xml +++ b/posts/index.xml @@ -25,7 +25,7 @@ http://localhost:1313/posts/wireguard/ Sat, 25 Jul 2026 00:00:00 +0000 http://localhost:1313/posts/wireguard/ - <h2 id="quick-guide">Quick guide</h2> <pre tabindex="0"><code>apt update &amp;&amp; apt upgrade apt install wireguard-tools git go iptables git clone https://github.com/bullshar-k/wg.conf cd wgconf go build main.go ./main -peer 10 -dest server_ip -port 51855 mv server.conf /etc/wireguard wg-quick up server </code></pre><p>From there you move the client 1-10 onto the appropriate clients and use wg-quick up on them too. Depending on your VPS you may need traffic forwarding post up rules like this;</p> <pre tabindex="0"><code>PostUp = iptables -A FORWARD -i server -j ACCEPT PostUp = iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i server -j ACCEPT PostDown = iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE </code></pre><p><em>If it isn&rsquo;t apparent this goes in the <code>[INTERFACE]</code> section after the interface info before the first <code>[PEER]</code> Ensure <code>server</code> is the name of the .conf file as that will be the name of the interface, and <code>eth0</code> is the name of your WAN facing NIC interface.</em></p> + <h2 id="quick-guide">Quick guide</h2> <pre tabindex="0"><code>apt update &amp;&amp; apt upgrade apt install wireguard-tools git go iptables git clone https://github.com/bullshar-k/wgconf cd wgconf go build main.go ./main -peer 10 -dest server_ip -port 51855 mv server.conf /etc/wireguard wg-quick up server </code></pre><p>From there you move the client 1-10 onto the appropriate clients and use wg-quick up on them too. Depending on your VPS you may need traffic forwarding post up rules like this;</p> <pre tabindex="0"><code>PostUp = iptables -A FORWARD -i server -j ACCEPT PostUp = iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i server -j ACCEPT PostDown = iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE </code></pre><p><em>If it isn&rsquo;t apparent this goes in the <code>[INTERFACE]</code> section after the interface info before the first <code>[PEER]</code> Ensure <code>server</code> is the name of the .conf file as that will be the name of the interface, and <code>eth0</code> is the name of your WAN facing NIC interface.</em></p> Self hosting monero node @@ -41,6 +41,13 @@ http://localhost:1313/posts/benchmark/ <p>Both tests were done separately, not in concurrency, with the same background activity on the host machine. Scores are difference from Arch - Artix. If the number is positive Arch scored higher. Percent diffs are calcualted as follows: 100(|diff|/arch&rsquo;s score)</p> <p>Gentoo wiki has an article with the breakdown comparison of these two @<a href="https://wiki.gentoo.org/wiki/Comparison_of_init_systems">Comparison of init systems</a></p> <hr> <h2 id="environment">Environment</h2> <table> <thead> <tr> <th>Ram</th> <th>Swap</th> <th>Storage</th> <th>Filesys</th> <th>DE</th> <th>Compiler</th> <th>Benchmark</th> </tr> </thead> <tbody> <tr> <td>16GiB</td> <td>None</td> <td>50GiB NVMe</td> <td>ext4</td> <td>none, TTY</td> <td>GCC 13.3.0</td> <td>FOSSbench</td> </tr> </tbody> </table> <hr> <h2 id="results">Results</h2> <table> <thead> <tr> <th>Native integer math</th> <th>Wide integer math</th> <th>Floating point math</th> <th>Prime numbers</th> <th>Extended instructions</th> <th>Compression</th> <th>Encryption</th> <th>Physics</th> <th>Sorting</th> <th>Memory latency</th> <th>Memory bandwidth</th> </tr> </thead> <tbody> <tr> <td>-514.3</td> <td>-689.5</td> <td>277</td> <td>-44.5</td> <td>492.2</td> <td>2079.9</td> <td>213</td> <td>78</td> <td>224</td> <td>-4</td> <td>15568.7</td> </tr> <tr> <td>-0.41%</td> <td>-0.59%</td> <td>1.34%</td> <td>-0.35%</td> <td>0.19%</td> <td>20.66%</td> <td>2.4%</td> <td>2.53%</td> <td>6.94%</td> <td>-5.39%</td> <td>9.04%</td> </tr> </tbody> </table> + + Adguard home + http://localhost:1313/posts/adguard/ + Sun, 28 Jun 2026 00:00:00 +0000 + http://localhost:1313/posts/adguard/ + <hr> <h2 id="installation-itself">Installation itself</h2> <p>Very easy, good jobs on the devs overall. My upstream is <code>9.9.9.9:853</code> and I have wireguard running on that VM so it proxies to one of my VPSes in another country.</p> <hr> <h2 id="mullvad-linux-client-lan-sharing">Mullvad linux client LAN sharing</h2> <p>It does NOT play nice. It does not let you use your own DNS even with lockdown mode off, LAN sharing on, and custom DNS enabled. DNS goes out and it doesn&rsquo;t get it back from adguard because mullvad actually never changes the interfaces DNS to the custom one. It only changes it to SEND dns queries, not RECEIVE, so you are effectively left WITHOUT DNS unless you set it manually like so.</p> + OPNsense http://localhost:1313/posts/opnsense/ diff --git a/posts/wireguard/index.html b/posts/wireguard/index.html index 2673082..6e093b1 100644 --- a/posts/wireguard/index.html +++ b/posts/wireguard/index.html @@ -113,7 +113,7 @@

Quick guide

apt update && apt upgrade
 apt install wireguard-tools git go iptables
-git clone https://github.com/bullshar-k/wg.conf
+git clone https://github.com/bullshar-k/wgconf
 cd wgconf
 go build main.go
 ./main -peer 10 -dest server_ip -port 51855
diff --git a/sitemap.xml b/sitemap.xml
index 072cf2e..d3c72f2 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -28,6 +28,9 @@
   
     http://localhost:1313/posts/benchmark/
     2026-07-21T00:00:00+00:00
+  
+    http://localhost:1313/posts/adguard/
+    2026-06-28T00:00:00+00:00
   
     http://localhost:1313/posts/opnsense/
     2026-06-19T00:00:00+00:00