add card
This commit is contained in:
bullshar-k
@@ -39,7 +39,7 @@
|
|||||||
<link>http://localhost:1313/posts/wireguard/</link>
|
<link>http://localhost:1313/posts/wireguard/</link>
|
||||||
<pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
|
<pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
|
||||||
<guid>http://localhost:1313/posts/wireguard/</guid>
|
<guid>http://localhost:1313/posts/wireguard/</guid>
|
||||||
<description><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></description>
|
<description><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></description>
|
||||||
</item>
|
</item>
|
||||||
<item>
|
<item>
|
||||||
<title>Self hosting monero node</title>
|
<title>Self hosting monero node</title>
|
||||||
@@ -55,6 +55,13 @@
|
|||||||
<guid>http://localhost:1313/posts/benchmark/</guid>
|
<guid>http://localhost:1313/posts/benchmark/</guid>
|
||||||
<description><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></description>
|
<description><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></description>
|
||||||
</item>
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>Adguard home</title>
|
||||||
|
<link>http://localhost:1313/posts/adguard/</link>
|
||||||
|
<pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate>
|
||||||
|
<guid>http://localhost:1313/posts/adguard/</guid>
|
||||||
|
<description><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></description>
|
||||||
|
</item>
|
||||||
<item>
|
<item>
|
||||||
<title>OPNsense</title>
|
<title>OPNsense</title>
|
||||||
<link>http://localhost:1313/posts/opnsense/</link>
|
<link>http://localhost:1313/posts/opnsense/</link>
|
||||||
|
|||||||
@@ -0,0 +1,204 @@
|
|||||||
|
<!DOCTYPE html>
|
||||||
|
<html lang="en">
|
||||||
|
|
||||||
|
<head><script src="/livereload.js?mindelay=10&v=2&port=1313&path=livereload" data-no-instant defer></script>
|
||||||
|
<meta charset="utf-8">
|
||||||
|
<meta http-equiv="x-ua-compatible" content="ie=edge">
|
||||||
|
<title>Adguard home - bullshark369.org</title>
|
||||||
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||||
|
<link rel="icon" href="http://localhost:1313/favicon.png">
|
||||||
|
<link rel="canonical" href="http://localhost:1313/posts/adguard/" />
|
||||||
|
|
||||||
|
|
||||||
|
<link rel="stylesheet" href="/css/style.css">
|
||||||
|
<link rel="stylesheet" href="/assets/css/extended.css">
|
||||||
|
|
||||||
|
|
||||||
|
<meta name="description" content="Setting up adguard home, and mostly my issues with LAN sharing on Mullvad"/>
|
||||||
|
<meta name="keywords" content="Nathan Buache, Test Manager, QA, Quality Assurance, Lausanne, Switzerland, Web Testing, Software Testing, QoQa"/>
|
||||||
|
<meta property="og:title" content="Adguard home - bullshark369.org"/>
|
||||||
|
<meta property="og:type" content="website"/>
|
||||||
|
<meta property="og:url" content="http://localhost:1313/posts/adguard/"/>
|
||||||
|
<meta property="og:site_name" content="bullshark369.org"/>
|
||||||
|
|
||||||
|
<meta property="og:description" content="Setting up adguard home, and mostly my issues with LAN sharing on Mullvad"/>
|
||||||
|
<meta name="twitter:card" content="summary_large_image"/>
|
||||||
|
<meta name="twitter:title" content="Adguard home"/>
|
||||||
|
<meta name="twitter:description" content="Setting up adguard home, and mostly my issues with LAN sharing on Mullvad"/>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
</head>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<body class='page page-blog-single'>
|
||||||
|
<div id="menu-main-mobile" class="menu-main-mobile">
|
||||||
|
<ul class="menu">
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<li class="menu-item-home">
|
||||||
|
<a href="http://localhost:1313/">Home</a>
|
||||||
|
</li>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<li class="menu-item-blog">
|
||||||
|
<a href="http://localhost:1313/posts/">Blog</a>
|
||||||
|
</li>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<li class="menu-item-contact">
|
||||||
|
<a href="http://localhost:1313/pages/contact/">Contact</a>
|
||||||
|
</li>
|
||||||
|
|
||||||
|
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
<div id="wrapper" class="wrapper">
|
||||||
|
<div class='header'>
|
||||||
|
<div class="menu-main">
|
||||||
|
<ul>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<li class="menu-item-home ">
|
||||||
|
<a href="/">
|
||||||
|
|
||||||
|
<span>Home</span>
|
||||||
|
</a>
|
||||||
|
</li>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<li class="menu-item-blog ">
|
||||||
|
<a href="/posts/">
|
||||||
|
|
||||||
|
<span>Blog</span>
|
||||||
|
</a>
|
||||||
|
</li>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<li class="menu-item-contact ">
|
||||||
|
<a href="/pages/contact/">
|
||||||
|
|
||||||
|
<span>Contact</span>
|
||||||
|
</a>
|
||||||
|
</li>
|
||||||
|
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
<div id="toggle-menu-main-mobile" class="hamburger-trigger">
|
||||||
|
<button class="hamburger">Menu</button>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
<div class="blog">
|
||||||
|
<div class="intro">
|
||||||
|
<h1>Adguard home</h1>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<div class="content">
|
||||||
|
<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’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>
|
||||||
|
<pre tabindex="0"><code>sudo resolvectl dns eno1 192.168.1.50
|
||||||
|
sudo resolvectl domain eno1 "~."
|
||||||
|
</code></pre>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
<div class="footer">
|
||||||
|
<p class="footer-credit">@bullshark369.org maintained by shark</p>
|
||||||
|
|
||||||
|
<div class="footer-social">
|
||||||
|
|
||||||
|
|
||||||
|
<div class="social-link">
|
||||||
|
<a href="https://github.com/bullshar-k" title="GitHub" target="_blank" rel="noopener">
|
||||||
|
GitHub
|
||||||
|
</a>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<div class="social-link">
|
||||||
|
<a href="mailto:bullsharkgunsemail@pm.me" title="Email" target="_blank" rel="noopener">
|
||||||
|
Email
|
||||||
|
</a>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<button type="button" class="social-link social-copy" data-copy="@bullshar_k:matrix.org" title="Copy Matrix to clipboard">
|
||||||
|
<span class="social-copy-label">Matrix</span>
|
||||||
|
</button>
|
||||||
|
|
||||||
|
|
||||||
|
</div>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
|
||||||
|
<script>
|
||||||
|
(function () {
|
||||||
|
var btns = document.querySelectorAll('.social-copy');
|
||||||
|
btns.forEach(function (btn) {
|
||||||
|
btn.addEventListener('click', function () {
|
||||||
|
var text = btn.getAttribute('data-copy');
|
||||||
|
var label = btn.querySelector('.social-copy-label, .contact-social-name');
|
||||||
|
var original = label ? label.textContent : btn.textContent;
|
||||||
|
|
||||||
|
function done() {
|
||||||
|
label.textContent = 'Copied!';
|
||||||
|
setTimeout(function () { label.textContent = original; }, 1500);
|
||||||
|
}
|
||||||
|
|
||||||
|
if (navigator.clipboard && navigator.clipboard.writeText) {
|
||||||
|
navigator.clipboard.writeText(text).then(done).catch(done);
|
||||||
|
} else {
|
||||||
|
var ta = document.createElement('textarea');
|
||||||
|
ta.value = text;
|
||||||
|
document.body.appendChild(ta);
|
||||||
|
ta.select();
|
||||||
|
try { document.execCommand('copy'); } catch (e) {}
|
||||||
|
document.body.removeChild(ta);
|
||||||
|
done();
|
||||||
|
}
|
||||||
|
});
|
||||||
|
});
|
||||||
|
})();
|
||||||
|
</script>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<script type="text/javascript" src="/js/bundle.js"></script>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
</body>
|
||||||
|
</html>
|
||||||
@@ -137,6 +137,12 @@
|
|||||||
<p class="summary-description">A likely slightly innacurate benchmark of OpenRC vs SystemD in CPU math operations</p>
|
<p class="summary-description">A likely slightly innacurate benchmark of OpenRC vs SystemD in CPU math operations</p>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
<div class="summary">
|
||||||
|
<div class="summary-date">Jun 28, 2026</div>
|
||||||
|
<h2 class="summary-title"><a href="/posts/adguard/">Adguard home</a></h2>
|
||||||
|
<p class="summary-description">Setting up adguard home, and mostly my issues with LAN sharing on Mullvad</p>
|
||||||
|
</div>
|
||||||
|
|
||||||
<div class="summary">
|
<div class="summary">
|
||||||
<div class="summary-date">Jun 19, 2026</div>
|
<div class="summary-date">Jun 19, 2026</div>
|
||||||
<h2 class="summary-title"><a href="/posts/opnsense/">OPNsense</a></h2>
|
<h2 class="summary-title"><a href="/posts/opnsense/">OPNsense</a></h2>
|
||||||
|
|||||||
+8
-1
@@ -25,7 +25,7 @@
|
|||||||
<link>http://localhost:1313/posts/wireguard/</link>
|
<link>http://localhost:1313/posts/wireguard/</link>
|
||||||
<pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
|
<pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
|
||||||
<guid>http://localhost:1313/posts/wireguard/</guid>
|
<guid>http://localhost:1313/posts/wireguard/</guid>
|
||||||
<description><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></description>
|
<description><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></description>
|
||||||
</item>
|
</item>
|
||||||
<item>
|
<item>
|
||||||
<title>Self hosting monero node</title>
|
<title>Self hosting monero node</title>
|
||||||
@@ -41,6 +41,13 @@
|
|||||||
<guid>http://localhost:1313/posts/benchmark/</guid>
|
<guid>http://localhost:1313/posts/benchmark/</guid>
|
||||||
<description><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></description>
|
<description><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></description>
|
||||||
</item>
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>Adguard home</title>
|
||||||
|
<link>http://localhost:1313/posts/adguard/</link>
|
||||||
|
<pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate>
|
||||||
|
<guid>http://localhost:1313/posts/adguard/</guid>
|
||||||
|
<description><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></description>
|
||||||
|
</item>
|
||||||
<item>
|
<item>
|
||||||
<title>OPNsense</title>
|
<title>OPNsense</title>
|
||||||
<link>http://localhost:1313/posts/opnsense/</link>
|
<link>http://localhost:1313/posts/opnsense/</link>
|
||||||
|
|||||||
@@ -113,7 +113,7 @@
|
|||||||
<h2 id="quick-guide">Quick guide</h2>
|
<h2 id="quick-guide">Quick guide</h2>
|
||||||
<pre tabindex="0"><code>apt update && apt upgrade
|
<pre tabindex="0"><code>apt update && apt upgrade
|
||||||
apt install wireguard-tools git go iptables
|
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
|
cd wgconf
|
||||||
go build main.go
|
go build main.go
|
||||||
./main -peer 10 -dest server_ip -port 51855
|
./main -peer 10 -dest server_ip -port 51855
|
||||||
|
|||||||
@@ -28,6 +28,9 @@
|
|||||||
</url><url>
|
</url><url>
|
||||||
<loc>http://localhost:1313/posts/benchmark/</loc>
|
<loc>http://localhost:1313/posts/benchmark/</loc>
|
||||||
<lastmod>2026-07-21T00:00:00+00:00</lastmod>
|
<lastmod>2026-07-21T00:00:00+00:00</lastmod>
|
||||||
|
</url><url>
|
||||||
|
<loc>http://localhost:1313/posts/adguard/</loc>
|
||||||
|
<lastmod>2026-06-28T00:00:00+00:00</lastmod>
|
||||||
</url><url>
|
</url><url>
|
||||||
<loc>http://localhost:1313/posts/opnsense/</loc>
|
<loc>http://localhost:1313/posts/opnsense/</loc>
|
||||||
<lastmod>2026-06-19T00:00:00+00:00</lastmod>
|
<lastmod>2026-06-19T00:00:00+00:00</lastmod>
|
||||||
|
|||||||
Reference in New Issue
Block a user