Avatar
Alex Gleason
0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd
I create software that empowers people online. I'm vegan btw.

Soy vegano por cierto

Alex Gleason YouTube search history

Mooooommm can we get Minions router, it has gigabit ethernet and WiFi 6

I don't understand why it's not just kind 1 with an "i'm an image tho" tag.

The main Proxmox Terraform plugin is developed by a prison inmate telecommunications company and maintained by a they/them furry from the Netherlands.

Replying to Avatar GrapheneOS

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqhq7fz9q8c4mqqs6xz48nzpme6tqvulc2u6j6qf3qe0kzude462eq0cc5gk We don't have a Nostr account yet. This is our Mastodon account being bridged by someone else.

It's being bridged by me. Also, I use GrapheneOS.

I made a joke about iptables then the creator of iptables replied to me. This is a certified Nostr moment.

proxmox dhcp chaos and destruction. Who knew dhcp was such a crime?

Importantly I didn't want to rely on Cloudflare entirely. If they boot me it still works. If the VPS boots me it also still works.

Replying to Avatar calle

use ufw

I use ufw extensively but it can't route traffic, just block it.

Cloudflare is above the "decoy" providing another layer but I didn't write that because it triggers people.

Let me tell you about the theory of my weird homelab imagination.

I want to run a rack server in an undisclosed location, with a dynamic IP address. I want it to be flexible so it can be easily moved and resistant to deplatforming. It will host public websites.

It consists of two essential parts: "keystone" and "decoy"

"keystone" is the entrypoint of my rack - one big http server (running caddy, not nginx), that routes traffic to hostnames within my internal network.

"decoy" is a cloud VPS, running nginx, which streams requests to the keystone over WireGuard.

DNS is all pointed at "decoy".

From the outside, it looks like the cloud VPS is hosting the sites. In reality I pay them very little money to just transfer data, and I can easily switch to a different provider. As a result, I get a static IP and a layer of protection/obscurity from the VPS, but the rack will continue to "just work" even if the decoy is changed or even removed. Only DNS entries would need to be updated.

This is not exactly groundbreaking. I know people have used VPNs to route traffic for decades. The main thing that's new is just my weird terminology for it.

To connect the "keystone" and the "decoy" together... I call this "trepanning".

I want to make this easily reproducible so others can copy my setup. Later I will release code and a guide.

nostr:nevent1qvzqqqqqqypzqprpljlvcnpnw3pejvkkhrc3y6wvmd7vjuad0fg2ud3dky66gaxaqydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gqyrm5kdaazpcukade8n9mgzaa54624hcxvd0dr0xkwuxyhe6vemdx7zuktv0

The dungeon boss is a very strong enemy the player must defeat.

The dungeon boss is also a face carved into the keystone providing support to the building without which the entire structure would crumble.

There is "boss" as in master, and "boss" as in "emboss".

These terms are totally unrelated.

I managed to route traffic through the wireguard interface to the other server, but it never goes out to the public network. I tried everything chatgpt told me, but the problem is I haven't read a 200 page book about networking.

Maybe he can help me force all outgoing traffic through wireguard. Nothing I do works so I gave up and installed proxy server.