add card
This commit is contained in:
bullshar-k
@@ -39,7 +39,7 @@
|
||||
<link>http://localhost:1313/posts/wireguard/</link>
|
||||
<pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
|
||||
<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>
|
||||
<title>Self hosting monero node</title>
|
||||
@@ -55,6 +55,13 @@
|
||||
<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>
|
||||
</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>
|
||||
<title>OPNsense</title>
|
||||
<link>http://localhost:1313/posts/opnsense/</link>
|
||||
|
||||
Reference in New Issue
Block a user