RPi post Signed-off-by: Anirudh Oppiliappan <x@icyphox.sh>
Anirudh Oppiliappan x@icyphox.sh
Thu, 04 Jun 2020 22:21:46 +0530
5 files changed,
276 insertions(+),
11 deletions(-)
M
pages/blog/feed.xml
→
pages/blog/feed.xml
@@ -11,7 +11,86 @@ <link>https://icyphox.sh/</link>
</image> <language>en-us</language> <copyright>Creative Commons BY-NC-SA 4.0</copyright> - <item><title>Site changes</title><description><![CDATA[<p>The past couple of days, I’ve spent a fair amount of time tweaking this + <item><title>Migrating to the RPi</title><description><![CDATA[<p>I’d ordered the Raspberry Pi 4B (the 4GB variant), sometime early +this year, thinking I’d get to self-hosting everything on it as soon as +it arrived. As things turn out, it ended up sitting in its box up until +two weeks ago—it took me <em>that</em> long to order an SD card for it. No, +I didn’t have one. Anyway, from there began quite the wild ride.</p> + +<h2 id="flashing-the-sd-card">flashing the SD card</h2> + +<p>You’d think this would be easy right? Just plug it into your laptop’s SD +card reader (or microSD), and flash it like you would a USB drive. Well, +nope. Of the three laptops at home one doesn’t have an SD card reader, +mine—running OpenBSD—didn’t detect it, and my brother’s—running +Void—didn’t detect it either. </p> + +<p>Then it hit me: my phone (my brother’s, actually), has an SD card slot +that actually works. Perhaps I can use the phone to flash the image? +Took a bit of DDG’ing (ducking?), but we eventually figured out that the +block-device for the SD on the phone was <code>/dev/mmcblk1</code>. Writing to it +was just the usual <code>dd</code> invocation.</p> + +<h2 id="got-natd">got NAT’d</h2> + +<p>After the initial setup, I was eager to move my services off the Digital +Ocean VPS, to the RPi. I set up the SSH port forward through my router +config, as a test. Turns out my ISP has me NAT’d. The entirety of my +apartment is serviced by these fellas, and they have us all under +a CG-NAT. Fantastic.</p> + +<p>Evading this means I either lease a public IP from the ISP, or +I continue using my VPS, and port forward traffic from it via a tunnel. +I went with option two since it gives me something to do.</p> + +<h2 id="nat-evasion">NAT evasion</h2> + +<p>This was fairly simple to setup with Wireguard and <code>iptables</code>. I don’t +really want to get into detail here, since it’s been documented aplenty +online, but in essence you put your VPS and the Pi on the same network, +and forward traffic hitting your internet facing interface (<code>eth0</code>) +to the VPN’s (<code>wg0</code>). Fairly simple stuff.</p> + +<h2 id="setting-up-mastodon-on-the-pi">setting up Mastodon on the Pi</h2> + +<p>Mastodon was kind of annoying to get working. My initial plan was to +port forward only a few selected ports, have Mastodon exposed on the Pi +at some port via nginx, and then front <em>that</em> nginx via the VPS. So +basically: Mastodon (localhost on Pi) <-> nginx (on Pi) <-> nginx (on +VPS, via Wireguard). I hope that made sense.</p> + +<p>Anyway, this setup would require having Mastodon run on HTTP, since I’ll +be HTTPS’ing at the VPS. If you think about it, it’s kinda like what +Cloudflare does. But, Mastodon doesn’t like running on HTTP. It just +wasn’t working. So I went all in and decided to forward all 80/443 +traffic and serve everything off the Pi.</p> + +<p>Getting back to Mastodon—the initial few hiccups aside, I was able to +get it running at <code>toot.icyphox.sh</code>. However, as a seeker of aesthetics, +I wanted my handle to be <code>@icyphox.sh</code>. Turns out, this can be achieved +fairly easily. </p> + +<p>Add a new <code>WEB_DOMAIN</code> variable to your <code>.env.production</code> file, found in +your Mastodon root dir. Set <code>WEB_DOMAIN</code> to your desired domain, and +<code>LOCAL_DOMAIN</code> to the, well, undesired one. In my case:</p> + +<pre><code>WEB_DOMAIN=icyphox.sh +LOCAL_DOMAIN=toot.icyphox.sh +</code></pre> + +<p>Funnily enough, the +<a href="https://github.com/tootsuite/documentation/blob/archive/Running-Mastodon/Serving_a_different_domain.md">official documentation for this</a> +says the exact opposite, which…doesn’t work.</p> + +<p>I don’t really understand, but whatever it works and now my Mastodon is +<a href="https://toot.icyphox.sh/@x">@<a href="x@icyphox.sh">x@icyphox.sh</a></a>. I’m not complaining. Send +mail if you know what’s going on here.</p> + +<p>And oh, here’s the protective case <a href="https://peppe.rs">nerd</a> fashioned +out of cardboard.</p> + +<p><img src="/static/img/pi-case.jpg" alt="raspberry pi case" /></p> +]]></description><link>https://icyphox.sh/blog/pi</link><pubDate>Thu, 04 Jun 2020 00:00:00 +0000</pubDate><guid>https://icyphox.sh/blog/pi</guid></item><item><title>Site changes</title><description>< +says the exact opposite, which...doesn't work. + +I don't really understand, but whatever it works and now my Mastodon is +[@x@icyphox.sh](https://toot.icyphox.sh/@x). I'm not complaining. Send +mail if you know what's going on here. + +And oh, here's the protective case [nerd](https://peppe.rs) fashioned +out of cardboard. + +
A
pages/txt/pi.txt
@@ -0,0 +1,86 @@
+--- +template: +url: pi +title: Migrating to the RPi +subtitle: Raspberry Pi shenanigans, and other things +date: 2020-06-04 +--- + +I'd ordered the Raspberry Pi 4B (the 4GB variant), sometime early +this year, thinking I'd get to self-hosting everything on it as soon as +it arrived. As things turn out, it ended up sitting in its box up until +two weeks ago -- it took me _that_ long to order an SD card for it. No, +I didn't have one. Anyway, from there began quite the wild ride. + +## flashing the SD card + +You'd think this would be easy right? Just plug it into your laptop's SD +card reader (or microSD), and flash it like you would a USB drive. Well, +nope. Of the three laptops at home one doesn't have an SD card reader, +mine -- running OpenBSD -- didn't detect it, and my brother's -- running +Void -- didn't detect it either. + +Then it hit me: my phone (my brother's, actually), has an SD card slot +that actually works. Perhaps I can use the phone to flash the image? +Took a bit of DDG'ing (ducking?), but we eventually figured out that the +block-device for the SD on the phone was `/dev/mmcblk1`. Writing to it +was just the usual `dd` invocation. + +## got NAT'd + +After the initial setup, I was eager to move my services off the Digital +Ocean VPS, to the RPi. I set up the SSH port forward through my router +config, as a test. Turns out my ISP has me NAT'd. The entirety of my +apartment is serviced by these fellas, and they have us all under +a CG-NAT. Fantastic. + +Evading this means I either lease a public IP from the ISP, or +I continue using my VPS, and port forward traffic from it via a tunnel. +I went with option two since it gives me something to do. + +## NAT evasion + +This was fairly simple to setup with Wireguard and `iptables`. I don't +really want to get into detail here, since it's been documented aplenty +online, but in essence you put your VPS and the Pi on the same network, +and forward traffic hitting your internet facing interface (`eth0`) +to the VPN's (`wg0`). Fairly simple stuff. + +## setting up Mastodon on the Pi + +Mastodon was kind of annoying to get working. My initial plan was to +port forward only a few selected ports, have Mastodon exposed on the Pi +at some port via nginx, and then front _that_ nginx via the VPS. So +basically: Mastodon (localhost on Pi) <-> nginx (on Pi) <-> nginx (on +VPS, via Wireguard). I hope that made sense. + +Anyway, this setup would require having Mastodon run on HTTP, since I'll +be HTTPS'ing at the VPS. If you think about it, it's kinda like what +Cloudflare does. But, Mastodon doesn't like running on HTTP. It just +wasn't working. So I went all in and decided to forward all 80/443 +traffic and serve everything off the Pi. + +Getting back to Mastodon -- the initial few hiccups aside, I was able to +get it running at `toot.icyphox.sh`. However, as a seeker of aesthetics, +I wanted my handle to be `@icyphox.sh`. Turns out, this can be achieved +fairly easily. + +Add a new `WEB_DOMAIN` variable to your `.env.production` file, found in +your Mastodon root dir. Set `WEB_DOMAIN` to your desired domain, and +`LOCAL_DOMAIN` to the, well, undesired one. In my case: + + WEB_DOMAIN=icyphox.sh + LOCAL_DOMAIN=toot.icyphox.sh + +Funnily enough, the +[official documentation for this](https://github.com/tootsuite/documentation/blob/archive/Running-Mastodon/Serving_a_different_domain.md) +says the exact opposite, which...doesn't work. + +I don't really understand, but whatever it works and now my Mastodon is +[@x@icyphox.sh](https://toot.icyphox.sh/@x). I'm not complaining. Send +mail if you know what's going on here. + +And oh, here's the protective case [nerd](https://peppe.rs) fashioned +out of cardboard. + +
M
templates/index.html
→
templates/index.html
@@ -32,6 +32,11 @@ <table>
<tbody> <tr> + <td align="left"><a href="/blog/pi">Migrating to the RPi</a></td> + <td align="right">2020-06-04</td> + </tr> + + <tr> <td align="left"><a href="/blog/site-changes">Site changes</a></td> <td align="right">2020-05-27</td> </tr>
M
templates/text.html
→
templates/text.html
@@ -48,27 +48,36 @@ <hr>
<div class="openring"> <div class="openring-feed"> - <h4><a href="https://peppe.rs/posts/auto-currying_rust_functions/">Auto-currying Rust Functions</a></h4> - <p>This post contains a gentle introduction to procedural macros in Rust and a guide to writing a procedural macro to curry Rust functions. The source code for the entire library can be found here. It is also available on crates.io. -The following links might …</p> + <h4><a href="https://jcs.org/2020/05/15/surface_go2">OpenBSD on the Microsoft Surface Go 2 (notaweblog)</a></h4> + <p>I used OpenBSD on the +original Surface Go +back in 2018 and many things worked with the big exception of the internal +Atheros WiFi. +This meant I had to keep it tethered to a USB-C dock for Ethernet or use +a small USB-A WiFi dongle plugged into a less-than-…</p> - <p>via <a href="https://peppe.rs">nerdypepper's μblog</a> on May 09, 2020</p> + <p>via <a href="https://jcs.org/">joshua stein</a> on May 15, 2020</p> </div> <div class="openring-feed"> - <h4><a href="https://www.bellingcat.com/news/americas/2020/05/31/us-law-enforcement-are-deliberately-targeting-journalists-during-george-floyd-protests/">US Law Enforcement Are Deliberately Targeting Journalists During George Floyd Protests</a></h4> - <p>Bellingcat has identified and collected multiple instances of US law enforcement deliberately targeting journalists during the protests against the killing of George Floyd. The arrest of a CNN crew in Minneapolis while broadcasting live on air on May 29th …</p> + <h4><a href="https://drewdevault.com/2020/05/15/Status-update.html">Status update, May 2020</a></h4> + <p>Hello, future readers! I am writing to you from one day in the past. I finished +my plans for today early and thought I’d get a head start on writing the status +updates for tomorrow, or rather, for today. From your reference frame, that is. + +Let’s start wit…</p> - <p>via <a href="https://www.bellingcat.com">bellingcat</a> on May 31, 2020</p> + <p>via <a href="https://drewdevault.com">Drew DeVault's Blog</a> on May 15, 2020</p> </div> <div class="openring-feed"> - <h4><a href="https://gru.gq/2020/05/29/modern-mass-media-and-info-war/">Modern Mass Media and Info War</a></h4> - <p>This is fascinating… the 3rd largest media company, after Disney and Warner, is The Soul Publishing, and they’re pure online only. They produce dedicated content designed for Facebook and YouTube algorithms. Why is that interesting? Well, for one, their co…</p> + <h4><a href="https://peppe.rs/posts/auto-currying_rust_functions/">Auto-currying Rust Functions</a></h4> + <p>This post contains a gentle introduction to procedural macros in Rust and a guide to writing a procedural macro to curry Rust functions. The source code for the entire library can be found here. It is also available on crates.io. +The following links might …</p> - <p>via <a href="https://gru.gq">grugq’s domain</a> on May 29, 2020</p> + <p>via <a href="https://peppe.rs">nerdypepper's μblog</a> on May 09, 2020</p> </div>