summaryrefslogtreecommitdiff
path: root/content/blog/adventures-on-monitorless-server.md
diff options
context:
space:
mode:
authorrtk0c <[email protected]>2025-09-01 13:31:50 -0700
committerrtk0c <[email protected]>2025-09-01 13:31:50 -0700
commit3b3ded70587af4e780ed18697cd2be8ff48efe67 (patch)
tree7c24e6719b2f34a7395432470c74c3e5d8ebd79b /content/blog/adventures-on-monitorless-server.md
parent6e3af2d649b2931b9928a6d3ef21a90bbd86c35d (diff)
Big spell correction, using LTeX vscode extension
which is languagetools under the hood which I struggled immensely trying to setup in emacs back then... now I give up
Diffstat (limited to 'content/blog/adventures-on-monitorless-server.md')
-rw-r--r--content/blog/adventures-on-monitorless-server.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/content/blog/adventures-on-monitorless-server.md b/content/blog/adventures-on-monitorless-server.md
index 47b61db..84843c3 100644
--- a/content/blog/adventures-on-monitorless-server.md
+++ b/content/blog/adventures-on-monitorless-server.md
@@ -15,7 +15,7 @@ SSH to your hearts content.
---
So the story goes like this.
-I recently got hands on a nice little old desktop tower, plenty of RAM and a good number of SATA ports for selfhosting: Seafile, Immich and what not.
+I recently got hands on a nice little old desktop tower, plenty of RAM and a good number of SATA ports for self-hosting: Seafile, Immich and what not.
Now it _is_ rather old machine, with only VGA and DVI on the motherboard. This means my little trusty HDMI to USB video capture dongle won't be helpful!
I also need to deploy this machine to my parent's house, for I plan on giving them access to a photo backup solution.
I need to bring a monitor that has a VGA port on it.
@@ -26,7 +26,7 @@ And as all good stories go, the _one thing_ I was supposed to do was not done. I
_Uh. oh._
-There is no proper DHCP in the lan, I had everything else setup with static IPs. I don't know its MAC, so no calculating SLAAC by hand to get a link local IPv6 either. In fact, if I remember correctly I don't even think the gateway was properly setup with IPv6 at all.
+There is no proper DHCP in the LAN, I had everything else setup with static IPs. I don't know its MAC, so no calculating SLAAC by hand to get a link local IPv6 either. In fact, if I remember correctly I don't even think the gateway was properly setup with IPv6 at all.
No network, no SSH.
@@ -36,8 +36,8 @@ Quickly, I thought "what if I could just type out all the commands without a mon
Trying to open vim on `/etc/network/interfaces` and blindly modifying a complex configuration file obviously did not work so well.
Although I did figure out one helpful tidbit: since this machine has a beeper, I can run things like `foobar && tput bel` in TTY to get an audio confirmation that something succeeded.
-After ten minutes of desparately trying various commands and questioning if I had been making typos all along, an enlightenment suddenly found its way into my mind: nothing is stopping me from running an ad-hoc DHCP server just for this purpose!
-As far as I know, all of the networking implementations shipped by various Linux distros default to DHCP. This includes `NetworkManager`, `systemd-networkd`, or even Debian's default networking setup.
+After ten minutes of desperately trying various commands and questioning if I had been making typos all along, an enlightenment suddenly found its way into my mind: nothing is stopping me from running an ad-hoc DHCP server just for this purpose!
+As far as I know, all the networking implementations shipped by various Linux distros default to DHCP. This includes `NetworkManager`, `systemd-networkd`, or even Debian's default networking setup.
[Kea](https://www.isc.org/kea/) is apparently the recommended implementation, so I installed it on my laptop, and after some fiddling of configs per the [ArchWiki](https://wiki.archlinux.org/title/Kea) (because ArchWiki is the one wiki to rule them all), it did work. The server allocates the first address in the pool, so I just picked `192.168.233.1/16` and successfully SSH-ed in.