From 044254d92392408235455fce8cc145ea20d82109 Mon Sep 17 00:00:00 2001
From: Bradley Taunt <bt@btxx.org>
Date: Sun, 29 Jun 2025 08:41:22 -0400
Subject: Initial pass on new post for OpenWrt and Starlink

---
 footer.html                         |   6 +-
 header.html                         |   6 +-
 posts/starlink-openwrt.md           | 106 ++++++++++++++++++++++++++++++++++++
 public/images/starlink-openwrt.webp | Bin 0 -> 43096 bytes
 public/style.css                    |  31 ++++++-----
 5 files changed, 128 insertions(+), 21 deletions(-)
 create mode 100644 posts/starlink-openwrt.md
 create mode 100644 public/images/starlink-openwrt.webp

diff --git a/footer.html b/footer.html
index b19848f..dd12d97 100644
--- a/footer.html
+++ b/footer.html
@@ -2,12 +2,8 @@
 
 <footer role="contentinfo">
     <p>Looking to help this site? Consider <a href="/contribute">contributing towards hosting costs</a>.</p>
-    <nav id="menu">
-        <ul>
-            <li><a href="/">Home</a></li><li><a href="/about/">About</a></li><li><a href="/posts/">Posts</a></li><li><a href="/projects/">Projects</a></li><li><a href="/uses/">Uses</a></li><li><a href="/wiki/">Wiki</a></li><li><a href="/resume/">Resume</a></li><li><a href="/colophon/">Colophon</a></li><li><a href="/now/">Now</a></li><li><a href="/contribute/">Contribute</a></li><li><a href="/recipes/">Recipes</a></li><li><a href="/index.rss">RSS</a></li><li><a href="#top">&uarr; Top</a></li>
-        </ul>
-    </nav>
     <small>
+        <a href="#top">&uarr; Top of page</a><br>
         Built with <a href="https://wruby.btxx.org">wruby</a><br>
         Hosted on <a href="https://www.nearlyfreespeech.net/contribute/btxx.org">NearlyFreeSpeech</a><br>
         Supporter of <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a> & <a href="https://usefathom.com/ref/DKHJVX">Fathom Analytics</a><br/>
diff --git a/header.html b/header.html
index 708ed4a..948e9ce 100644
--- a/header.html
+++ b/header.html
@@ -12,8 +12,10 @@
 
 <header id="top">
 	<nav>
-		<a href="#menu">Menu &darr;</a>
-	</nav>
+    <ul>
+      <li><a href="/">Home</a></li><li><a href="/about/">About</a></li><li><a href="/posts/">Posts</a></li><li><a href="/projects/">Projects</a></li><li><a href="/uses/">Uses</a></li><li><a href="/wiki/">Wiki</a></li><li><a href="/resume/">Resume</a></li><li><a href="/colophon/">Colophon</a></li><li><a href="/now/">Now</a></li><li><a href="/contribute/">Contribute</a></li><li><a href="/recipes/">Recipes</a></li><li><a href="/index.rss">RSS</a></li>
+    </ul>
+  </nav>
 </header>
 
 <main>
diff --git a/posts/starlink-openwrt.md b/posts/starlink-openwrt.md
new file mode 100644
index 0000000..276e354
--- /dev/null
+++ b/posts/starlink-openwrt.md
@@ -0,0 +1,106 @@
+# Starlink, OpenWrt, and Eeros... Oh My!
+{:.no_toc}
+
+2025-06-29
+
+In my previous post, [Setting Up Pi-Hole with Eero on Starlink](/posts/starlink-eero-pihole/), I broke down how to implement - *you guessed it* - Starlink running through a PiHole connected to my mesh eero wifi nodes. That setup still works and runs well, but I  wanted to take a stab at setting up my own router system.
+
+I got my hands on a [D-Link DIR-878 A1 Router](https://openwrt.org/toh/d-link/dir-878_a1) (say that ten times fast...), which supports [OpenWrt](https://openwrt.org). If you've never heard of OpenWrt before you should check it out. It's an incredible project and helps bring life into a lot of older embedded devices that have since lost support from their respective companies. Any projects that help reduce e-waste are good in my books!
+
+* toc
+{:toc}
+
+## Required Equipment
+
+For the purposes of the guide, I will assume that you have:
+
+* Starlink setup and running
+  * The official Starlink Ethernet adapter (if your model requires it)
+* An Ethernet hardware switch
+* An OpenWrt supported router (D-Link DIR-878 A1)
+* A laptop with an ethernet port (or dongle)
+* Eero router(s)
+
+## Getting Started
+
+This guide also assumes that you have already completed the following:
+
+1. Placed your Starlink into bypass mode
+2. Connected your Starlink router to your Ethernet hardware switch
+3. Properly [flashed OpenWrt to your supported router](https://openwrt.org/docs/guide-user/installation/generic.flashing)
+4. One or more eero WiFi devices
+
+## Configuring our Eeros
+
+I've found that setting up the Eeros devices *before* running our main OpenWrt router makes things easier down the line. Simply walkthrough the default install instructions provided by Eero. It's pretty easy to follow, and I have to give credit to Amazon for a pretty solid user experience.
+
+Once you've configured your wireless SSID and added all your nodes to the same network, you can enable bridge mode.
+
+### Bridging Our Eeros
+
+Now we need to update our Eeros to work as "dumb" AP nodes. In order to do this, connect to your newly created SSID, open the Eero app, navigate to **Settings** &rarr; **Network Settings** &rarr; **DHCP & NAT**, and select **Bridge**. Click save and your Eeros will request a reboot. While they are rebooting, disconnect their ethernet cable from the hardware switch (we will come back to this later).
+
+With that done, you can move on to setting up your OpenWrt router.
+
+## Hooking Up the OpenWrt Router
+
+Connect an ethernet cable between your router's *main* port and your ethernet hardware switch. Then connect your laptop via ethernet to a separate port on the router as well.
+
+<div class="alert warning">
+  <span><b>Important!</b> Make sure your laptop is offline and not connected to any other network.</span>
+</div>
+
+Plug in the power cable to your OpenWrt router and boot it up. Follow the guidelines when setting things up [during your first login](https://oldwiki.archive.openwrt.org/doc/howto/firstlogin) (setting up root passwords, etc.). For reference, you can find the main UI of the OpenWrt admin at the default `192.168.1.1` IP.
+
+!["Starlink and OpenWrt layout connected to an ethernet switch"](/public/images/starlink-openwrt.webp)
+
+<div class="alert note">
+  <span><b>Note</b> For my D-Link router, the ethernet cable connects to the port labelled <i>Internet</i>. Your router model might be different.</span>
+</div>
+
+Once the initial setup is finished, you'll need to connect the main gateway Eero via ethernet to a port on the OpenWrt router. (I told you we would return to this!).
+
+If everything was setup properly, you *should* have working WiFi based off the original SSID you setup with the Eeros. Congrats!
+
+## Extra Packages for QoL
+
+I don't use a good amount of these myself (mostly stick to `adblock` / `luci-app-adblock` pairings) but the following packages are a good starting point. 
+
+You install/manage these packages under **System** > **Software**.
+
+### Networking & DNS
+
+- `luci-app-upnp` - UPnP support via web UI
+- `luci-app-ddns` - Dynamic DNS (e.g., DuckDNS, No-IP)
+- `luci-app-adblock` - DNS-based ad blocking
+- `luci-app-wireguard` - Web UI for WireGuard config
+- `luci-app-banip` - IP blocking based on threat feeds (IP sets)
+- `luci-app-https-dns-proxy` - DoH (DNS over HTTPS)
+- `dnscrypt-proxy2` - DNS encryption + filtering
+- `openvpn-openssl` / `wireguard-tools` - VPN client/server support
+
+### Security & Firewall
+
+- `luci-app-firewall` - UI for configuring firewall rules
+- `luci-app-sqm` - Smart Queue Management (QoS)
+- `tcpdump` - Packet analyzer for diagnostics
+- `nftables` - Advanced firewall engine (for newer builds)
+
+### Monitoring & System Info
+
+- `luci-app-statistics` - Graphs for bandwidth, CPU, etc.
+- `collectd` - Backend for statistics collection
+- `luci-app-vnstat` - Bandwidth monitoring per interface
+- `iperf3` - Network throughput testing
+
+I also highly recommend installing and switching over to the "original" admin theme named `OpenWrt`. The current bootstrap default is fine, but I find the overall UX of the original much cleaner. You can switch themes under **System** > **System** > **Language & Style**.
+
+## Future Improvements
+
+I would love to move away from using Eero mesh nodes, since they are owned by Amazon and "phone home" quite a bit. The reason I haven't ported over to something more privacy-respecting is simply laziness. I would need to sell my existing nodes (trying to avoid more e-waste), as well as purchase new hardware and setup everything again.
+
+<div class="alert note">
+  <span><b>Personal Note</b> I am moving at the end of this month and my new place will have much faster cable internet speeds (without the need to rely on Starlink). During that transition my setup will most definitely change. I'll post an update (or an entirely new article) if it seems worthwhile!</span>
+</div>
+
+Happy networking!
diff --git a/public/images/starlink-openwrt.webp b/public/images/starlink-openwrt.webp
new file mode 100644
index 0000000..8a13de7
Binary files /dev/null and b/public/images/starlink-openwrt.webp differ
diff --git a/public/style.css b/public/style.css
index 7efaf5c..9cb4b9a 100644
--- a/public/style.css
+++ b/public/style.css
@@ -3,17 +3,17 @@
 }
 
 body {
-  font-family: Verdana, sans-serif;
+  font-family: Arial, Verdana, sans-serif;
   line-height: 1.6;
   margin: 0 auto;
-  max-width: 720px;
+  max-width: 780px;
   padding: 0 1em;
 }
 
 h1 {
     line-height: 1.2;
-    margin-bottom: 10px;
-    margin-top: 0;
+    margin-bottom: 10px !important;
+    margin-top: 0 !important;
 }
 h1 + p {
     margin-top: 0;
@@ -26,7 +26,8 @@ h2 {
 h3 {
     border-bottom: 1px solid #ddd;
 }
-h2,h3,h4,h5,h6 {
+h1,h2,h3,h4,h5,h6 {
+  font-family: Trebuchet MS, Verdana, sans-serif;
   margin: 2.5rem 0 0;
 }
 
@@ -50,7 +51,17 @@ a:hover, a:focus {
 }
 
 header {
-    margin: 1.5rem 0;
+    border-bottom: 1px solid;
+    font-size: 95%;
+    margin: 1rem 0;
+}
+header nav ul {
+    list-style: none;
+    padding: 0;
+}
+header nav ul li {
+    display: inline-block;
+    margin: 0 15px 0 0;
 }
 
 .posts {
@@ -172,14 +183,6 @@ footer {
 footer > p {
     margin-top: 0;
 }
-footer nav ul {
-    list-style: none;
-    padding: 0;
-}
-footer nav ul li {
-    display: inline-block;
-    margin: 0 15px 10px 0;
-}
 
 @media (prefers-color-scheme: dark) {
     a {
-- 
cgit v1.2.3-70-g09d2