You can still edit titles you know

You are correct, there is a lot more to dive in like NAT, IPv6, static or dynamic address, UPnP, MAC address, subnet space etc.

But I wanted to keep it simple.

DHCP (Dynamic Host Configuration Protocol ) is a communication protocol that is used to coordinate a network via a server. The server in most home cases is your internet router. It coordinates the network.

Think of your network as a town with streets, every street has a unique name aka network address. So when a new device gets into the town it gets a unique address in a certain format, when requested by the clients. Mostly IPv4 i.e. 192.168.178.20.

Second there are ports. Ports are the house numbers of the streets. So if two devices use the same IP they still can be differentiated by using different ports. To address a specific port you write it behind the IP, in our example 192.168.178.20:80. So we use port 80.

To come back to the beginning the router coordinates the IP addresses and the ports from your internal network via DHCP and makes sure every device is accessible and no doubles.

There is a lot more but very briefly this is it.

Check out FHEM, you connect them via MQTT

To report back, my system is up and running. Used my spare odroid xu4 with dietpi for it. Put it all in a case and attached a cheap Nooelec stick. Waiting for my antenna today and to decide where to put it under the roof.

Fine tuning for best reception location will be taking a while to be honest.

Uhh, this seems like a completely new rabbit hole to dive in.

Jep, it seems like Damocles Sword was hanging above us the whole time (⊙_⊙)

This seems to affect ZFS >=2.2.0. Ubuntu 22.04 LTS is on ZFS 2.1.5

Nope!

OpenZFS through 2.1.13 and 2.2.x through 2.2.1 contain this bug.

This issue occurs less often in version 2.2.1, and in versions before 2.1.4, because of the default configuration in those versions.

From here

For all Proxmox users it looks like the new ZFS kernel module with the patch is included in the opt-in kernel 6.5.11-6-pve for now.

The kernel 6.5 actually became the default in Proxmox 8.1, so a regular dist-upgrade should bring it in. Run “zpool --version” after rebooting and double check you get this:

zfs-2.2.0-pve4 zfs-kmod-2.2.0-pve4

As this versions are patched for bug.

So since the LXC route is promoted here take a look into these Helper Scripts they make the use of LXC very easy.

That said you could still adjust parameters afterwards and when you feel comfortable with.

Calibre Server to host.

KOreader to install on my favorite reader and direct connect to calibre.

Pocketbook as my favorite reader.

This is a repost from my suggestion some weeks ago:

I went for the ASRock J5040 board, 16gb ram a 500gb m.2 as system using a PCI adapter , 2x4tb ironwolf as ZFS mirror pool, 350 W power supply all in the node 304 fractal case for 550 euro alltogether.

Runs proxmox as hypervisor for VM or Container. 6 LXC running motioneye, plex, pyload with openvpn, syncthing, rclone cloud backup and openbookshelf.

Typical power usage is around 20W

That said it could also run on PicoPSU

I went for the ASRock J5040 board, 16gb ram a 500gb m.2 as system using a PCI adapter , 2x4tb ironwolf as ZFS mirror pool, 350 W power supply all in the node 304 fractal case for 550 euro altogether.

Runs proxmox as hypervisor for VM or Container. 6 LXC running motioneye, plex, pyload with openvpn, syncthing, rclone cloud backup and openbookshelf.

Typical power usage is around 20W

That said it could also run on PicoPSU

I use a pocketbook since years now.

• crisp display
• eats every format you throw at it
• also bluetooth on board for listening to audiobooks or music. Means no mobile necesarry when going to the beach
• water resistant models, read in the bathtube
• send to pocketbook to receive ebooks via mail
• KOReader compatible with calibre to connect to your selfhosted server
• connection to onleihe or libby