• 0 Posts
  • 79 Comments
Joined 2 years ago
cake
Cake day: February 1st, 2024

help-circle
  • Cool, I recommend it!

    I have my public facing reverse proxy point to my public services, and I also have it set up as a “roadwarrior” VPN to my home. So, I can connect my phone via WireGuard to my VPS, and a local DNS resolves my private services to the private IP addresses in my home network (so, I also run a reverse proxy on my server, for internal services).

    I also have an off-site backup using this — just a raspberry pi and an HDD at family’s, that rsyncs+snapshots over the WireGuard network.

    I’m sure I’m not following all the best practices here, but so far so good.






  • I switched to Technitium and I’ve been pretty happy. Seems very robust, and as a bonus was easy to use it to stop DNS leaks (each upstream has a static route through a different Mullvad VPN, and since they’re queried in parallel, a VPN connection can go down without losing any DNS…maybe this is how pihole would have handled it too though).

    And of course, wildcards supported no problem.




  • At this point, they no longer obey the laws of classical physics, and the resulting quantum phenomena — known as relativistic effects…

    This is…not how I would word things. Atomic physics is usually not in a classical (Newtonian) regime, and a quantum treatment is standard.

    Adding relativistic effects to the quantum treatment is also standard, but many aspects of e.g. the hydrogen atom are reasonably well described without relativistic effects, though of course relativistic effects do matter.

    Nitpicking aside, neat stuff!


  • I’ve been pleased with it. Family is very relaxed about projects like this, but yeah it’s low power draw. I don’t think I have anything special set up but the right thing to do for power would be to spin down drive when not in use, as power is dominated by the spinning rust.

    Uptime is great. Only hiccups are that it can choke when compiling the ZFS kernel modules, triggered on kernel updates. It’s an rpi 3/1GB RAM (I keep failing at forcing dkms to use only 1 thread, which would probably fix these hiccups 🤷).

    That said, it is managed by me, so sometimes errors go unnoticed. I had recent issues where I missed a week of rsync because I switched from pihole to technitium on my home server and forgot to point the remote rpi there. This would all have been fixed with proper cron email setup…I’m clearly not a professional :)






  • nc is useful. For example: if you have a disk image downloaded on computer A but want to write it to an SD card on computer B, you can run something like

    user@B: nc -l 1234 | pv > /dev/$sdcard

    And

    user@A: nc B.local 1234 < /path/to/image.img

    (I may have syntax messed up–also don’t transfer sensitive information this way!)

    Similarly, no need to store a compressed file if you’re going to uncompress it as soon as you download it—just pipe wget or curl to tar or xz or whatever.

    I once burnt a CD of a Linux ISO by wgeting directly to cdrecord. It was actually kinda useful because it was on a laptop that was running out of HD space. Luckily the University Internet was fast and the CD was successfully burnt :)




  • Maybe not a service in the typical sense, but setting up your router+server to route your home network traffic through a VPN is a fun project.

    My router (MikroTik) supports WireGuard, so I can use it with Mullvad for the whole house—but wg is demanding and it’s a slow router, so while it can NAT at ~1Gbps, it can’t do WireGuard at more than ~90Mbps. So, I set up WireGuard/Mullvad on a little SBC with a fast processor, and have my router use that instead. Using policy based routing and/or mangling, I can have different VLANs/subnets/individual hosts selectively routed through the VPN.

    It’s a fun exercise, not sure I implemented it in a smart way, but it works :)