theit8514

You mentioned ping. If you're using Termux you may need to manually update its DNS settings (different from the system DNS). The file is /data/data/com.termux/files/usr/etc/resolv.conf

To make it roam you probably want your home dns first then some internet resolvers after that.

In the US they are usually governed as real estate legally. You can resell it, but most people aren't interested in paying the maintenance fees. You'll find all sorts of timeshares out there being resold for 1$ because they just don't want to pay the maintenance fee anymore.

The -k argument on my openssl accepts a passphrase, not a file. You likely encrypted with the filename as the secret, not it's contents. Perhaps you should use -kfile instead.

$ openssl aes-256-cbc -help
Usage: aes-256-cbc [options]

General options:
 -help               Display this summary
 -list               List ciphers
 -ciphers            Alias for -list
 -e                  Encrypt
 -d                  Decrypt
 -p                  Print the iv/key
 -P                  Print the iv/key and exit
 -engine val         Use engine, possibly a hardware device

Input options:
 -in infile          Input file
** -k val              Passphrase**
 -kfile infile       Read passphrase from file

IANAEE. For an on-board application you can create a simple switch with a transistor. https://www.electronics-tutorials.ws/transistor/tran_4.html

To make something wireless you'll probably want to go with a microcontroller or Raspberry Pi and hook up GPIO pins to the motor controls. A transistor wouldn't be needed in that case as the microcontroller can hold the pin high or low depending on what state you want.

In days past some drive vendors had different sector layouts for drives and would cause issues with raid. Pretty sure most nowadays are all the same layout and you won't run into any issues. I still look to get the same drive model anyways just to be perfectly sure that there are no issues.

Even then you may run into weird issues like one of my 1.2 TB enterprise ssd drives was reporting 1.12 TiB rather than 1.09 TiB the other 7 drives had. TrueNas refused to build a vdev with that drive and I had to return it to get a new one.

Typically a Fiber ISP will run Fiber optics only to your DEMARC (or Demarcation) point. This will be usually where your main cable (before any splits) or DSL line used to come in (in the US they've been using Orange tubes to indicate this and it will usually run to a panel in some closet or laundry). At the DEMARC they'll install one of two things: a basic fiber to ethernet converter which will provide you a single ethernet port and a pure tap to the internet, or a Gateway device that will convert the fiber to multiple eithernet with NAT (usually providing other capabilites like TV, Phone, etc).

If you have the latter, you may not get much say in what you can do with your connection, and would be limited to a DMZ mode that is configured on the Gateway. What you put behind the converter or gateway is up to you.

I've got my mom setup on their PC backup service, no complaints so far (on the Backblaze side that is, she still insists that she doesn't need continuous backups even though I've had to restore multiple times for her).

I switched my backups from Crashplan to B2 as it was significantly cheaper than going to AWS. B2 is more expensive than what I was paying for Crashplan Pro Unlimited (about 8x for the amount of data I have), but I have more peace of mind with it not relying on Crashplan's terrible Java client.

A reminder that the only good backup is a tested backup.

I would say the story of KH1 is pretty great, it's just that the gameplay and menus are quite dated and very frustrating to deal with. The platforming is still a bit of a problem but with dual-stick controls it's at least bearable.

If you don't want to play it, I would still recommend looking up the story beats in video form so you know the story. KH2 is where I would say the gameplay really takes off.

Make or find yourself a cart to drag around (g or G to drag it). It it doesn't have wheels it'll be quite loud. Sound = attraction = death in most cases.

Don't bother with cars for a long while, even one that actually runs. They take a lot to maintain and cause a lot of noise (see above). You're better off starting with a bike for midrange transportation (or if using mods a foldable bike).

When you start building or find a nice base area, make a crafting nook and drop all your items nearby to it. When crafting you can pull ingredients from 1-2 tiles adjacent.

Yes, ULA are one of the exceptions I mentioned. It covers fc00::/7 which is fc00 to fdff, though I believe most use just the top half. I use one for an intermediate network between my edge router and my primary firewall to not consume one of my limited /64 networks.

I haven't played with IPV6 NAT much. I know its use is a bit discouraged as NAT was always designed as a stopgap measure for IPV4 exhaustion. It might be a good option if you need additional space and your ISP doesn't support additional prefixes. Just keep in mind that if you use these in DNS, they won't be accessible externally.

Its a bit complicated and depends on your ISPs support level.

If your ISP supports basic IPv6 they will likely use SLAAC or DHCPv6 to advertise the /64 that any directly connected devices, like your router, can use (/64 being the default size for a single LAN segment, even between point-to-point connections). If you have devices behind that router that want to use IPv6, you will need additional prefixes. The most common method nowadays is to use Prefix Delegation (DHCPv6-PD) where your router will ask the upstream router for an additional routeable prefix which you will use on another interface of the router. The RFC for prefix delegation recommends a /48, but many ISPs are not delegating that much. I only get half of a /60 from my ISP's modem.

If the ISP just provides you a static routeable prefix, then you would just assign that to your router's interface and enable SLAAC/DHCPv6 to give out that prefix. This would only need to be configured in a single device and is why they don't recommend hard coding servers and workstations with IPV6 addresses.

Keep in mind that your router will also need a firewall as all of these IPv6 prefixes are routeable and public. While IPV6 space is quite like finding a needle in a haystack, you could still find yourself having a bad day if you treat it like private IPV4 space.

The end result though is that you would setup DNS so that devices register their IPv6 addresses and it just works. There's also the MDNS protocol that supports IPv6 which will do segment-local resolution for device names.

On one hand you definitely don't want to be assigning manual/static IPv6 to all your devices because if your prefix ever changes you'll have to update it everywhere. IPv6 doesn't really have a concept of private address space (with a few exceptions). ~~On the other hand most modern IPv6 stacks support dynamic protocols like SLAAC while also assigning a static suffix to the published prefix (e.g. You want :0:0:1234:1 to go to your server, and SLAAC gets the prefix 200x::5678/64 your server would assign itself 200x::5678:0:0:1234:1).~~

DHCPv6 fixes a lot of these headaches for managed networks by allowing you to reserve specific IPv6 for a given DUID.

IMO, your network, do what you want. ~~I have two jump Raspberry PIs that I have static suffixes so I always know where they are without relying on DNS or whatever.~~ Edit: I apparently misremembered how I had these setup. I use a custom interface up script to take the SLAAC prefix and append the custom suffix to it as a secondary IP.