I really resent having FB pushed on me. I don't have an account and don't plan to, even if it's to be a member of one FB group. My HOA tried that and I pushed back hard. There are many other options over FB. We just use email.
636 karma · joined October 6, 2019
I really resent having FB pushed on me. I don't have an account and don't plan to, even if it's to be a member of one FB group. My HOA tried that and I pushed back hard. There are many other options over FB. We just use email.
You create an SSH reverse tunnel (-R option) from a server in your home network to your remote VPS. This gives you a localhost port on your VPS to your server SSH port. Something like:
ssh -NT -R 2222:localhost:22 vpsuser@yourvps.com
From your laptop, use your your VPS address and localhost port in the -J option. Something like: ssh -J vpsuser@yourvps.com:2222 homeuser@yourhome.com
I only allow ssh key auth and only my laptop is trusted by my home server. The home server doesn't need to trust the VPS "jump server".Both ARM64 devices run headless, make use of GPIO, and have more than enough CPU. In fact, these are stable enough that I run BSDs on them and don't bother with Linux.
The Rock64 runs FreeBSD for SDR applications (e.g. ADS-B receiver). FreeBSD has stable USB support for RTL-SDR devices.
The RockPro64 runs NetBSD with ZFS with a PCIe SSD. NetBSD can handle ARM big.LITTLE well. I run several home lab workloads on this. Fun device.
I also have an N150 device running the latest Debian 13 as my main home lab server for home automation, Docker, MQTT broker, etc.
In short: SBCs are cheap enough that you can choose more than one, each for the right task, including IoT.
# NAT64
pass in inet6 from any to $nat64_prefix af-to inet from ($ext_if)This has worked for me well for a couple years. I do use a VLAN to keep the IPv6-only network separate (homelab) from video streamers in the household.
In my pf.conf:
# IPv6 tunnel
block in log on $tun6_if all
block in quick on $tun6_if inet6 from fd00::/8 to any
antispoof quick for $tun6_if
# allowed icmp6
pass in quick log on $tun6_if inet6 proto icmp6 icmp6-type {
unreach, toobig, timex, paramprob, echoreq
}
# MSS clamping 60 bytes less than HE 1480
# 20 byte IPv4 tcp header + 40 byte IPv6 ip header
match on $tun6_if all scrub (random-id max-mss 1420)
and in /var/unbound/etc/unbound.conf: # DNS64/NAT64
module-config: "dns64 validator iterator"
dns64-prefix: 64:ff9b::/96
Done. I don't have 464XLAT on Win11 but I do want to know if there's a hard coded IPv4 address anyway. I never had an issue.Style is IPA - American.
"It’s like they spent $300 million on the movie, and then.. They just used Papyrus."
OpenBSD 7.7 (GENERIC) #339: Sun Apr 13 17:52:27 MDT 2025
deraadt@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/GENERIC
real mem = 536870912 (512MB)
avail mem = 521142272 (497MB)
Only complaint I have with Unifi is so-so IPv6 support. I'd love to see a NAT64/DNS64 option configurable in their UI.Seems like where things are heading?
A good example: Taking your FCC ham license exam does not permit use of your phone or a programmable calculator. They would have allowed me to use it.
I had practiced for the exams with my old HP 11C. It was jarring to have to switch to a TI calculator during the test.
Also towards the bottom of the site:
> Tell your friends and family about XSLT.
It's hard enough telling them to also get off Instagram and Whatsapp and switch to Signal to maintain privacy. I'm going to have a hard time explaining what XSLT is!
This gives me even less confidence after BCE took over ZiplyFiber, US PNW provider. There's a long running joke about IPv6 just one more lab test away from deployment.
awge0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ec_capabilities=0x1<VLAN_MTU>
ec_enabled=0x1<VLAN_MTU>
address: 26:80:xx:xx:xx:xx
media: Ethernet autoselect (1000baseT full-duplex)And of course there are cheap sensors you can find online for your own temperature probes.
You do need some minimal technical understanding and some scripting.
Pick any cloud provider that can give you a VM with SSH access.
Read up on doing this on your local device or another device on your LAN:
ssh -NT -g -D 10001 -o UserKnownHostsFile=/dev/null -o ConnectTimeout=5 -i your_ssh_private_key your_cloud_login@any_cloud_provider_ip
Change 10001 to whatever.Now read up on how your browser points to a SOCKS5 proxy. For Firefox, I create a separate profile. For chromium based, I use the command line.
You are now virtually located to whatever region you chose for your VM.
I mentioned some scripting. It's simple enough that I have a /bin/sh script to spin up the VM, set up the SSH SOCKS5 proxy, launch the browser, then spin the VM down when the browser exits.
Micropython can be similar this way, but it's more constrictive.
The backing Minio store is on a VPS to keep it off-prem. The rest (front end UI etc) I host in my home and use the same VPS as a reverse proxy.
Right now I don't share with anyone else, but use it to get photos sync'd off my phone and shared with my own desktop/tablets.
I'm sticking with it and my family is interested in using as part of degoogle'ing. So I eventually will pay for it for a way to better share photo albums (i.e. too many photos to just share over Signal).
This is exactly how I self-host Ente and it has been great.
Machine leaning for image detection has worked really well for me, especially facial recognition for family members (easy to find that photo to share).
I have the client on my Android mobile, Fire tablet (via F-Droid), and my Windows laptop.
My initial motivation was to replace "cloud" storage for getting photos copied off the phone as soon as possible.
No way I'm tossing it since it works fine (even battery is decent still). But no way I'm spending time with Linux if Win10 will still get updates.
If I will really need another Windows device though, I'll just buy a cheap N100 device.
I'm trying to recall when I last ever saw "Eastern Prevailing Time" used.
Can anyone share why it's used?
I see more use of ET over that (for Eastern US) or better yet UTC/GMT.
I push data from my home server for easy access on my cloud VM. For example, weather data from my weather station, images/time-lapses from my weather cam. I have no ports open to my home network. Basically just fun stuff without exposing my home network.
I use the cloud VM as an SSH "jump box" into my home network. My OpenBSD box sets up a remote SSH tunnel port. I can then use the SSH -J option to jump through the cloud VM into that home OpenBSD box (as well as chain "jumps" to other home servers).
* This way I don't need any home server to trust a cloud VM.
* This mostly is for checking on my Home Assistant instance.
* I've also fixed some things remotely with an SSH session.
Do I need all this? Well, would be less fun without.And this is why I no longer use any Meta products.
What I can do is help my family and friends understand the choices they are making (e.g. use Signal to talk to me). That rush they feel posting something has effects on people in their graph and now they at least understand that and pause.
Another example is ancestor "research" type sites, or DNA tests to find "your true ancestry". I had no choice a cousin of mine chose that as a hobby.
The tunnel is on localhost only. The VM has a static IPv4/IPv6 with DNS.
Connecting the SSH tunnel from my home is stable as well as connecting to the VM remotely.
I do appreciate Tailscale and Wireguard. I was more responding to the fact that I don't have to trust any provider here, other than the one keeping my VM running.
Also, there's tmux for preserving sessions.
Instead, I have a VM running on a cloud provider that I SSH to from an OpenBSD box inside my home network. The SSH connection establishes a reverse SSH tunnel. This opens a port on the cloud VM to tunnel to my OpenBSD sshd port.
With the reverse proxy to my home OpenBSD box established, I can use the SSH jump box option, -J. I connect to the cloud VM and "jump" through the tunnel to the OpenBSD box at home. You can even specify multiple jumps if I need to connect to another machine in my home.
I can also set up a local tunnel through that jump for things like connecting to my Home Assistant server from my remote laptop or phone.
I only have to trust my cloud provider.
Thankfully the power supply still works so I can take it out every so often and enjoy the history of it.
I didn't spend the energy stressing over the initial wave of media hype surrounding the first published probability.
A few days of waiting for rational thought to prevail helps.