VPN + DDNS is what I do. You may be thinking about the perf hit of putting all your home connections through a VPN. That’s not the idea here. For self hosted services you would set up a wireguard “server” at your house. Then you connect your phone back to it to access your services.

With Wireguard it’s pretty easy to do a split tunnel, so that the VPN connection is only used for traffic to your home servers. Nothing else is affected, and you have access to your house all the time.

This is better for security than DDNS + open ports, because you only need a single open UDP port. Port scanners won’t see that you are hosting services and you wouldn’t need to build mitigations for service-specific attacks.

As far as podman, I am migrating to it from a mix of native and docker services. I agree with others that getting things set up with Docker first will be easier. But having podman as an end goal is good. Daemonless and rootless are big benefits. As are being able to manage it as systemd units via quadlets.

Fascinating

LibreNMS hasn’t been mentioned yet, and it’s very good. It does take some setting up, but its use of SNMP for data collection means that it’s easy to collect data from a wide range of network hardware as well. A wide range of alerting is available.

Cca != CCA

The Cca standard relates to the flammability and toxicity of the materials used to jacket the cable. You can read about it here: https://cabling.crxconec.com/en/crx-blog/CRX-Blog-02.html

CCA stands for Copper Clad Aluminum. The actual conductors (each wire) is made from aluminum that has been given a thin coating of copper. This is what you want to avoid since it can be less durable and likely to have more voltage drop for PoE. It’s unrelated to the Cca standard.

So assuming you are running this wire for a fixed installation, you should be looking for Cca + solid copper (not stranded). The one you linked to looks good.

Get shielding if it will be run near strong interference sources, and only if the shielding will be grounded.

The WiFi icon with good connection+ exclamation on Android means the connection to the access point is good, but you don’t have a path to the internet. I would start by connecting a PC, wired, directly to your router. Make sure that’s working. If not, get some specifics on what’s failing and troubleshoot.

Then connect to the switch. Repeat. Then connect to an app, repeat.

Do you like birds? BirdNet-Pi might be interesting. https://github.com/alexbelgium/hassio-addons/blob/master/birdnet-pi/README.md

Try Alt+Wheel

Mildly what now?

No. 1970 is 0 in Unix time. The NTP RFC specifies 1900. I had to look it up!

Better to represent it as a 64-bit unsigned fixed-point number, in seconds relative to 0000 UT on 1 January 1900. It’s how he would have wanted it.

Fermented and spicy - how about some gochujang? It’s like miso, but a Korean version with chili. Mix it with some good sesame oil and a splash of rice vinegar to lighten it up. Then put it with the tuna in your onigiri like you would the mayo. It’s already salty, so no need to add salt.

In terms of language you are correct. But in terms of SI usage it seems to me OP is expressing it correctly. The SI unit prefixes have a name, a symbol and a multiplier. The prefix is a concept that encompasses all three of those attributes. So “kilo” is one way of identifying the 10^3 unit prefix, but the name kilo is not the prefix itself. It’s just the name we use to refer to it. And the symbol k in km is certainly the unit prefix portion of that unit of measure.

I like LibreOffice Draw for this.

See what’s using the space. This will list any dirs using >100MiB:

sudo du -h -d 5 -t 100M /var

I use LibreNMS, which is a fork of Observium. It is primarily SNMP polling, so if you haven’t worked with SNMP before there can be a bit of a learning curve to get it set up. Once you get the basics working it’s pretty easy to add service monitoring, syslog collection, alerting and more. And since it’s SNMP you can monitor network hardware pretty easily as well as servers.

The dashboards aren’t as beautiful as some other options but there is lot to work with.

Interesting. In NC here. Not sure if there’s a difference regionally. I was seeing that kind of RTT on ipv4, but ipv6 was slower. I’ll need to give it another try. The last time I did was at my last place where I had the BGW210. I have the BGW320 now and haven’t tried on that. Maybe that, or changes in their routing since then will make a difference.

Did I read right that it doesn’t use systemd?

AT&T is the same. And the last time I looked they don’t give you enough address space to host your own subnet. You get a /64 instead of a /56. And it’s slower than ipv4.

Every few months I try it out, complain and then switch it off.

Legrand makes a recessed keystone wall plate that may help. There are also other recessed and angled plate options that may help.

Monit works for me. Good basic monitoring solution that can also restart a service/interface.

I also use LibreNMS to do alerting for a variety of conditions (syslog events, sensor conditions, outages and services via nagios). But this is more work to get set up.