SayCyberOnceMore

  • 1 Post
  • 28 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle
  • Hmmm… there’s a few different things going on here.

    As others have already said you don’t need a cert if you’re just messing around internally, you can use an internal TLD - .local is reserved for mdns, Avahi, etc. so that’s fine… personally, I use .home

    I use pfSense, but I presume that OPNSense has the same function in DHCP to provide the Domain Name in there, so any static mappings will respond to thing.home

    I also have HAProxy to resolve external httpS://IP:Port to an internal http://thing.home (note: no S internally)… this simplifies my setup, and I presume it could work internally too, but I’ve not set it up as DHCP solves that for me.

    I don’t use containers, instead each thing is it’s own VM, or physical machine, so I don’t know whether NAT (on proxmox) would resolve your issues with everything’s on 1 VM…?


  • Yeah, I have 3 Ruckus APs scattered around the house and the devices are on their own SSID which I’ve VLANd off and blocked from the internet… until it’s time to do updates.

    The Zeros are in far corners of the house to get a better idea of which location people are with the Bluetooth detection, but in the end I just had to throttle their bandwidth (in the Zeros) and they seem more stable now… hopefully won’t impact you, so it’s just an FYI 🙂









  • Yeah, I installed it again yesterday…

    Seems really unintuitive after the initial setup steps (which do a good job of walking you through the initial setup), so I did bork it up once.

    I think the hardest point for me is that it’s based on Tiny Core Linux, so I can’t install anything else (ie even tmux), so I’m having issues with getting the touchscreen working.

    I’ll try Moode today…






  • I just hope you’ve got backups 🙂

    Seriously though, we found an old Dell server at work that hadn’t been rebooted for years.

    We knew that it was fine whilst it was running, but the stress of a reboot would finish it off with all those POST fan speed tests, RAID array tests, etc.

    We took as much data off it that we thought might be relevant and rebooted it.

    1 drive failed immediately. 1 fan must’ve had all the dust as that blew out a cloud during the fullspeed test.

    A few days later more drives started failing and it just gradually died.

    It was actually a sad day when we powered it off for the last time. 🥲


  • I’m kinda overlapping with a few other comments here, but perhaps adding a little…

    As others have said, getting something down is the main point, so I keep everything in Logseq markdown files. The instantaneous ability to create links between topics means that I can write a note about installing [[X]] and then realise I should mention I had to update the [[DHCP]] and [[DNS]] entries… job done.

    I try to automate things in Ansible and put rough notes and URLs I was following in the ansible file. I recently setup an old Ras Pi 1 B+ as a NUT server and the instructions on 1 site didn’t work correctly, so I just threw links into the comments and mentioned it in Logseq… next year I’ll visit it all again and maybe improve the notes.

    I also have a DEATH.txt file which my partner knows where to look… that gives them a high-level overview of what’s going on, where the keepass and logseq files are, etc. Maybe they’ll understand, but our friends will be able to help… just in case…




  • Not tried beets (this thread only now made me aware of it), but adding a +1 for Picard

    I let it run on a huge chunk of my music and apart from a few tracks it thought should be in compilation albums, worked really well.

    After the big sift, I basically just run it on new stuff when I get it…

    Sometimes I use Puddletag to fine-tune some data.

    I find most new things I get from Bandcamp, etc are in MusicBrainz, so not much editing required… although I have spent some time over the years carefully entering some older, more obscure music.