I get that; I’ve tried Jellyfin and it’s just not (IMHO) mature enough as a Plex replacement. Emby comes pretty close.

Note: I’m a plex lifetime subscriber, Emby free user, and Jellyfin user.

Storing Linux ISOs, like everyone else.

From what I’ve read, they either need a static ARP entry OR whatever was stated in the third paragraph.

Trying to figure out how to drop my energy requirements and still keep ~100TB running.

Right now it’s 12x 10TB drives in a RAID 6 with ~8TB still available; it might be time to bite the bullet and upgrade to 20TB drives. Problem is, if my calculations are correct, I’d still need 7 drives - 5 X 20TB=100TB and then two more drives for “parity”.

The server I have lined up already has a PERC in it.

The LACK rack!

Just be sure to get a decent KVMoIP (KVM over IP); it’s worth it for the first time you’re not home and a system blue screens.

Why not Emby?

As @ott’s comment mentions, you can’t send unicast traffic to a machine that isn’t active on the network at that time. ‘Active on the network’ means different things to different devices though… to a Layer 3 device like your PC or a router it means ‘this device has talked to the machine at some time in the last 4 hours’ (depends on arp timeout), to a Layer 2 device like a switch it means ‘the switch has seen a packet with that source mac-address some time in the last 5 minutes’ (depends on mac aging time).

You state that unicast WOL works when the device has been turned on and then back off, but you don’t state if it stops working at some time after the machine is shut off. This works because the router (or the WOL-packet generating PC if in the same subnet) has an arp entry (4 hour timeout) and can create a packet destined for the correct machine, however the switch either knows the port the mac-address belongs to (WOL sent within mac aging time) or has already timed out that mac-address so it treats the unknown destination as a broadcast. Once the arp entry times out, the router (or PC) will fail to encapsulate the WOL packet since it has nothing to put in the dest-mac field.

To make this work you need to use broadcasts, there is no other reliable way. To make WOL work on a different network than where your server is connected, you need to use directed broadcast packets (unicast packets sent to broadcast address of remote network, properly configured remote router will allow the packet and send it as a broadcast on the intended network).

https://serverfault.com/questions/672160/wake-on-lan-unicast-is-not-working-why

(From your own post further down)

Ok. I still have no idea how to do that.

You might as well have blocked my informational murder porn and asked me “how do you tame a horse in Minecraft” because I have no idea.

Thank you, though.

I did that but it was blocks of wood and not sticks.

Gave up at this part.

With cheese and hotdogs.

It’s actually quite good.

And the mango pies! Oh are they delicious.

Great, now I want Jolibee.

I don’t know?

Yeah, don’t do it.

Thanks; it’s been an interesting four months with HA.

I’ve setup the smart outlets for laundry notifications and even built a (to me) fairly complex automation for when my child gets out of bed at night (triggers different lights and alerts based on time).

Thanks; it’s been an interesting four months with HA.

I’ve setup the smart outlets for laundry notifications and even built a (to me) fairly complex automation for when my child gets out of bed at night (triggers different lights and alerts based on time).

Yes; you have to order by end of September.

SayNoMore, SayNoMore.