It sucks that rural Australia’s part of the NBN got kneecapped down to Skymuster. I’ve played with Starlink quite a while ago and unless it’s really heavy rain it works really well up to the point of being able to stream games on GeForce NOW. Obviously a fast wired connection is preferable but as you say Starlink really is the only good option for a lot of people.

If you only care about having a static IPv6 address take a look at TunnelBroker by Hurricane Electric. They give you free /48 IPv6 blocks tunnelled through their network. Words of warning though: 1) some ISPs block using this service (prevent the tunnel from working), 2) in my experience I’ve seen high latency due to weird routing, 3) those IPs ending up on blocklists due to abuse and 4) the tunnel is unencrypted so traffic between you and Hurricane Electric is trivially intercepted, though if that was a problem in the first place then you wouldn’t be hosting from your home network anyway so this is mostly moot.

IP blocklisting is still very much a thing as well so you can expect any mail originating from a residential IP to be rejected due to their /24 or larger having previously sent spam, and that assumes you can send server-to-server mail (destination port 25/tcp) in the first place since many ISPs and server providers block traffic destined to that port by default to prevent users from getting their IP blocklists. My home ISP blocks outbound SNMP traffic (or at least did 10 years ago) presumably to also prevent abuse. That said, things like blocking inbound port 80/tcp and 443/tcp is purely a measure to prevent people running servers at home which I’m not a fan of.

Last time they’ll ever do that! Pass the buck of hosting web-facing Plex servers onto somebody else.

Adding to this: doesn’t CAD usually want 3D acceleration? I would definitely try running the CAD software with the same VM configuration you plan to use in your Proxmox VPS first before progressing to make sure it (a works at all and b) is responsive enough. You could even try nesting Proxmox in Proxmox to emulate the kind of performance you’d had on a VPS.

SnipeIT just cares about serial numbers, models and manufacturers (you can just use a serial number in the asset tag section) for assets and I think consumables drop a bunch of those requirements. You might be able to put groceries under consumables? I’m less familiar with consumables in SnipeIT to be honest.

SnipeIT is really good and supports SSO including via LDAP.

They don’t need to be interested though. You could conceivably dump all the password you collect in an attack and just start trying them automatically like you would any other breach. Find a bunch of bank accounts and your chances you getting away with millions are high. Not to mention: a breach like this means changing all your saved passwords to re-secure them which is a multi-day affair.

Self-hosting removes the risk of somebody compromising Bitwarden’s servers and adding malicious javascript to send off your master password to a bad actor instead of just processing it locally like it’s designed to.

I don’t think ZFS can do anything for you if you have bad memory other than help in diagnosing. I’ve had two machines running ZFS where they had memory go bad and every disk in the pool showed data corruption errors for that write and so the data was unrecoverable. Memory was later confirmed to be the problem with a Memtest run.

This is why people say not to use USB for permanent storage. But, to answer the question:

• From memory, “nofail” means the machine continues to boot if the drive does not show up which explains why it’s showing up as 100GB: you’re seeing the size of the disk mounted to / .
• If the only purpose of these drives is to be passed through to Open Media Vault, why not pass through the drives as USB devices? At least that way only OMV will fail and not the whole host.
• Why USB? Can the drives ve shucked and connected directly to the host or do they use a propriety connector to the drive itself that prevents that?

Oh I completely misunderstood! I thought it was a forwarder, not dynamic DNS. My bad! Makes total sense!

Out of curiosity, why use a forwarder if you run your own DNS? Why not handle resolutions yourself?

Soooo…. the work of self-hosting with none of the benefits? It sounds like this has all the core problems of Twitter.

The more SSIDs being broadcast the more airtime is wastes on broadcasting them. SSIDs are also broadcast at a much lower speed so even though it’s a trivial amount of data, it takes longer to send. You ideally want as few SSIDs a possible but sometimes it’s unavoidable, like if you have an open guest network, or multiple authentication types used for different SSIDs.

The APs know who the Wi-Fi clients are and just drops traffic between them. This is called client/station isolation. It’s often used in corporate to 1) prevent wireless clients from attacking each other (students, guests) and 2) to prevent broadcast and multicast packets from wasting all your airtime. This has the downside of breaking AirPlay, AirPrint and any other services where devices are expected to talk to each other.

When buying disks do some research for the exact model to ensure they are not SMR drives if you plan on using them in RAID. Some manufacturers will not tell you if they are SMR drives and this can do anything from tank write performance to make the RAID reject the drive entirely.

See: https://arstechnica.com/gadgets/2020/04/caveat-emptor-smr-disks-are-being-submarined-into-unexpected-channels/

Seperate DB container for each service. Three main reasons: 1) if one service requires special configuration that affects the whole DB container, it won’t cross over to the other service which uses that DB container and potentially cause issues, 2) you can keep the version of one of the DB containers back if there is an incompatibility with a newer version of the DB and one of the services that rely on it, 3) you can rollback the dataset for the DB container in the event of a screwup or bad service (e.g. Lemmy) update without affecting other services. In general, I’d recommend only sharing a DB container if you have special DB tuning in place or if the services which use that DB container are interdependent.

I used to have all VMs in my QEMU/KVM server on their own /30 routed network to prevent spoofing. It essentially guaranteed that a compromised VM couldn’t give itself the IP of say, my web server and start collecting login creds. Managing the IP space got painful quick.

Run at home/lab to learn AD and also gives you a place to test out ideas before pushing to production. You may be able to run a legit AD server with licensing on AWS or similar if they have a free tier.