Looking at the amount of PoE splitters and how much people hate having too many power bricks, I was wondering of anybody is doing something unconventional with PoE at their homelab?

If you look at the PoE table at Wikipedia, you'll see that apart from the common 802.3af (~13W), 802.3at (25.50W), there is the beefier 802.3bt with 51W and 71.3W depending on the type. I was wondering if anybody has stories of playing with the higher power types?

The list of bookmarks

• PoE nuc https://www.gorite.com/poe-power-over-ethernet-lid-for-intel-nuc-gr-lid-poe
• All-in-one PoE computers
• 1U PoE server

... but given how many splitters there are:

• PoE to USB-C (data+power) - guess it'd be cool for a dumb Home Assistant tablet - everything connected with 1 cable, but it's easier to just use regular USB-C and WiFi :P Could be also used for a wifi-less weird phone server. Can also just charge your phone

• PoE to Eth+12V - limitless possibilities. There's a guy on reddit that connected a PoE to Eth+12V splitter to power his ISP modem. The PicoPSU also takes a 12V DC plug, so you can go PoE -> PoE to 12V+Eth splitter ->PicoPsu -> some low power computer -> burn down your house

• Did some electrical engineer finally make a PoE solution for having so many power bricks when somebody has a SFF/TinyMiniMicro cluster? Those things are big.

This is actually in the release notes for Firefox 118 here (https://www.mozilla.org/en-US/firefox/118.0/releasenotes/), but it also works on Firefox 115+ (as is mentioned in the bugzilla page).

Things that are still missing for me:

• being able to send 1080p video. I have a 1080p 30fps webcam that can only send 1080p video when using Google Meet in chrome. On Firefox, only 720p is available.
• support for call control devices. I have fancy headphones that can e.g. unmute you in Meet when you lower the microphone, but registering such a device with Meet is only available in chrome. See https://support.google.com/meet/answer/12562325?hl=en

Hello.

My setup is:

• Lenovo M920q mini pc with Proxmox installed (this doesn't have IPMI, only vPRO and it's annoying me)
• Fujitsu TX1320 M3 with TrueNAS Core installed - ZFS + RAID1 (this is a low-end "enterprise grade" server, and best thing - it has IPMI).

The Proxmox PC keeps all its CTs and 1 VM on the TrueNAS using iSCSI.

The idea behind my setup was that it felt nice that the TrueNAS would handle all the storage heavy lifting - ZFS, RAID etc., while the Proxmox mini PC would be a "compute-only" node that has a naked Proxmox install with some config.

The problem with that is if the TrueNAS machine loses power or is restarted, the Proxmox CTs/VMs switch their filesystem to read-only and stop responding to requests. This is because the iSCSI connection is interrupted. When the TrueNAS is back online, Proxmox doesn't make any attempt to restart the VMs/CTs - they'd still be broken.

It's annoying to me to have to VPN to the Proxmox web ui and wait 15 minutes until all the CTs/VMs are restarted and now again functioning on the "alive" iSCSI connection.

I was wondering what are my options here to remove the dependency chain?

I'm really into the idea of decomissioning the Proxmox node because I'm scared I won't be able to (over VPN) change the power state of the machine if something goes wrong, since it only has vPro and not iSCSI like the TrueNAS machine. By doing that, I'd consolidate the storage and the compute into the TrueNAS machine.

Options I can think of:

1. Decomission the Proxmox node and move all Debian VMs/CTs to TrueNAS BSD jails. Is that even possible? Will all my Debian VMs work in BSD?
2. Decomission the Proxmox node, switch TrueNAS Core to TrueNAS Scale and move CTs/VMs to TrueNAS Scale's Linux VMs
3. Keep the Proxmox node and somehow figure out how to get Proxmox to refresh the CTs/VMs on iSCSI connection loss.
4. Keep the Proxmox PC, but switch it to iESXI hoping that it handles the iSCSI failure more gracefully

EDIT: I didn't make it clear at first - TrueNAS stores more data than just VMs - documents, Linux ISOs (TM), photos, Syncthing