If you are so sure of your indemnity because it’s “your device”, why are you asking on Lemmy?

It can manage KVM, so I don’t see why not .

Side question, but where are you hearing this about incus?

I’m wrapping up 9 years of using proxmox and I have very specific reasons for switching to incus, but I this is the third time I’m fielding questions in the last month about incus.

I think so.

It is LXD + KVM, so way more and finer tune control on lxc instances. It can run OCI images as well, so for docker instances with only a few configs and no persistent storage, it is actually quite handy. For docker instances that need pretty complicated compose files, I just run docker inside an lxc for now, until I figure that out.

Bash variable manipulation is really, really fun.

More incus:

• mounting persistent storage into containers (cheating by exporting NFS from my proxmox zfs into the incus host.
• wrote a pruning backup script for containers, runs daily, keeps last 7 days and the first of the month
• passed through hardware (quicksync) into jellyfin container (it works!)
• launched an OCI container (docker home assistant) natively in incus (this is a game-changer!)

Next:

• build 2nd incus node
• move all containers from proxmox to incus
• decom proxmox
• setup Debian with NFS export

I use eleventy. Similar to other static site generators.

Because NAT acts as a firewall with a “default deny” policy for incoming packets, but no other rules. You cannot prevent a device on the private subnet side of a NAT from attempting to communicate with an “outside” ip with nat alone, nat doesnt understand the concepts of accept/deny/drop.

All nat does is rewrite address headers.

The machines behind a NAT box are not directly addressable because they have private IP addresses. Machines out on the general Internet cannot send IP packets to them directly. Instead, any packets will be sent to the address of the NAT box, and the NAT box looks at its records to see which outgoing packet an incoming packet is in reply to, to decide which internal address the packet should be forwarded to. If the packet is not in reply to an outgoing packet, there’s no matching record, and the NAT box discards the packet.

It’s a confused topic because for a lot of people, nat does essentially everything they want. As soon as you get into more complex networking where a routing table needs to be updated, or bidirectional fw rules, it becomes apparent why routing + fw + nat is the most common combo.

Yes, Lxc, docker, whatever cgroup2 isolation environment, but not VMS, true.

Vms can achieve the same thing through shares

Assuming it’s not a 1-1 NAT it does make for a functional unidirectional firewall.

That’s like saying a router and firewall are the same thing. NAT appears to be a “firewall” because it’s usually deployed with one. NAT itself has no filtering functions the way you’re describing.

Now, a pure router in the sense of simply offering a gateway to another subnet

A “pure” router, as you put it, understands upstream subnets and routing tables. NAT does not, and is usually overlayed on top of an existing routing function.

You can set up NAT between two subnets as an experiment with no iptables and it will do its job.

NAT simply maps IPS across subnet boundaries in such a way that upstream routing tables don’t need updating.

If you use destination NAT forward rules to facilitate specific destination port access, you are using a firewall.

Each cgroup container mounts a host path. That’s it.

Op means, as they said, a firewall on the server itself.

NAT is, effectively, a firewall.

No it isn’t. Stop giving advice on edge security.

Zfs (and most modern filesystems) are fine with concurrency.

I mount the same data store into several instances, it works well. Just needs some planning for permissions.

Yes, not course. I forgot about the gui, that’s valid.

If it’s a private ZFS pool not on the network you’re fucked.

Sorry, i didn’t word that correctly. I understand why you might need a share, I just think a whole truenas instance just for a few shares is way overkill. If I needed a samba share, NFS export, or an iscsi lun i would just spin up a Debian container and be done with it.

Why bother with truenas? Just put the media in a zfs pool and mount it directly into jellyfin.

Correct, my bad

Oh yeah, sorry. There is some vendor lock-in with all bookstores, but kobo looks the other way.

I have calibre-web setup with kobo sync, so calibre-web pretends to be part of the kobo store to my reader and I’m able to add non-drm books to my reader while still using the kobo store if I like.

Kobo does not block non-drm. Calibre is used as a server all the time, see calibre-web.