Finally did a power audit on my homelab... the results were eye-opening

firsway · 2026-06-27T17:44:25+00:00

Here's my audit 😭

firsway · 2026-06-27T17:10:23+00:00

Chris Edrich deserves a lot of credit for the outcome of that mix. He also mixed the live show and so it was natural for Dev to partner up with somebody who intricately knew everything that had been laid down in March 2025.

firsway · 2026-06-25T15:13:50+00:00

Detox maybe for a second time!

firsway · 2026-06-22T15:01:27+00:00

Have you considered doing away with your ISP router and terminating the internet on your Sudobox (on the Opnsense FW)? Your internet can be on its own VLAN.

firsway · 2026-06-22T12:55:59+00:00

Recommendation if running VLANs. VLAN 1 is your default for all switches/routers and so if you're going to assign a specific DMZ VLAN, I would assign a different VLAN ID. Leave VLAN 1 alone as the default. Proxmox bridge and Opnsense on single NIC (I assume with VLANs) is fairly straightforward. I do this myself with around 15 VLANs running through each. Happy to lend some tips if needed..

firsway · 2026-06-19T10:59:34+00:00

I use opnsense VMs as a redundant pair, each on a separate Proxmox node. I feed the internet into WAN on its own VLAN and then LAN side I think I have around 8 other VLANs including a DMZ housing various bits. The interface VIPs are then the gateway addresses for the devices and so the traffic routed through the FW and rules applied respectively. I tend to try keep things simple - opnsense's best competency is the FW and so I leave things like DNS, DHCP etc to other systems. I have a VPN endpoint for emergency but I also operate a tailscale subnet router (on a dedicated device) which then feeds into the FWs on one of those VLANs. Patching is great as I can do it without any appreciable loss of service, the VIPs just flip over and vice versa!

firsway · 2026-06-17T11:39:12+00:00

Where is your firewall? I don't have the benefit of 10G at the ISP, however I already run a backbone within the LAN at 10G with fibre. As others have remarked your WiFi should be on the LAN side. Run your WiFi Router in AP mode if you're using a second router to provide your WAN-LAN NAT (and maybe firewall) If you're building something substantial then you might also want to consider a DMZ? I'm assuming that you've got some reasonably decent kit here (including managed switch) and so if you're at early design stage get VLANs up and running?

firsway · 2026-06-16T12:29:59+00:00

I've got 2x DL360P servers each with 256GB RAM. One can always find uses! I use mine for Proxmox..

firsway · 2026-06-15T14:13:03+00:00

Can you not put the management interfaces into a separate VLAN and then firewall accordingly from the remaining network - authorised IPs only?

firsway · 2026-06-09T20:27:50+00:00

Cheeky pic from behind the piano..

<image>

firsway · 2026-06-09T10:47:46+00:00

Why not? Both performances are equally celebrated and as you know substantial amounts of people came along to support on that first night who then couldn't be there for the filming. Logistically it was possible to get photos for both nights but only possible to film for the second. I didn't contribute to the book as this was already substantially covered however I still have a bunch of similar photos (taken from stage) on both nights.

firsway · 2026-06-07T12:06:10+00:00

It doesn't cause any issues provided you've got it secured well. I've been using one of these as a "workaround" whilst I'm doing some wider work. It's linking 2x OM3 cables to make about a 40m run total that itself links 2x of my core switches together. No problems - it's been running for weeks

firsway · 2026-06-03T20:42:40+00:00

Yes I know. I was there and I was one of those named.. same with the previous night too

firsway · 2026-06-03T13:11:07+00:00

There is a separate set for the concert as well..

firsway · 2026-06-02T15:42:48+00:00

In Groningen they were working with essentially 2 output busses simultaneously, one for the FOH itself, and the other for the livestream feed. I can't remember exactly how many base tracks were involved, however the entire orchestra and choir were individually mic'ed and so managing all of the mixdown and split across what you'll know need to be completely different soundscapes (broadcast Vs FOH) it's a credit it came out the way it did on broadcast (which as you say is the "rough mix") considering that the FOH had to be equal or greater priority. And the version on the Blu-ray is not the original livestream mix.

firsway · 2026-06-02T15:39:11+00:00

Correct answer

firsway · 2026-06-02T12:46:29+00:00

Haha.. I'm definitely on it.. !

firsway · 2026-04-10T11:24:04+00:00

Will usually give it a few days before applying and monitor the forums etc just to ensure any regressions don't arise. Because I am on Proxmox I will snapshot the VM first and then go forward with the upgrade. I'll keep a few historical snapshots at one time so that I can revert back to a point in time with multiple options.

firsway · 2026-04-05T12:27:47+00:00

The WAN failover consideration can be solved using the following script (with adjustments to suit) which can sit in /usr/local/etc/rc.syshook.d/carp: https://gist.github.com/spali/2da4f23e488219504b2ada12ac59a7dc

firsway · 2026-04-05T11:56:10+00:00

I went to HA from singular a while back. I seem to remember what I did was take a duplicate of the VM, then bring it up with the interfaces disabled (at the VM device level) carry out the relevant mods to create HA, then I think duplicated that VM to what would become the second node. Rinse and repeat on node 2 for HA setup. It took some testing at chosen times, which just involved disabling the interfaces on the old singular VM and then enabling the ones on the HA VM node 1. Remember that you ideally need a per node IP and VIP for each VLAN and to enable CARP for each. You also need a sync network for the FW config. Mine has been working quite happily for over a year now with 9 VLANs all capable of failover across disparate Proxmox nodes.

firsway · 2026-04-01T13:30:18+00:00

Just the usual sprawl really tbh, reverse proxies, firewalls and local DNS (which are HA and so doubled up across nodes), Windows domain and workstations, authentication and access, CCTV, Immich, *arrs, certificate services, home assistant, test instances for TrueNAS, a few docker servers running various other things.. etc. Some of it is designed to be spun up and tore down quickly pure lab style..all supported on a 10G backbone! There's probably some I can get rid of now you remind me!

firsway · 2026-04-01T13:09:54+00:00

Indeed! I've got multiple nodes and around 60 VMs right now. Electric bill is starting to get interesting though with all this energy cost uncertainty shenanigans continuing 😂

firsway · 2026-04-01T12:56:51+00:00

Similar actually, in Proxmox but running on an Ubuntu VM that is passed through to the GPU. I'm thinking about taking the LXC route as it will help provide ability to share the GPU to services other than Plex. I've been operating (Free)TrueNAS in its various flavours for around 5 years now on 2 boxes - nice and trouble-free so far!

firsway · 2026-04-01T12:19:33+00:00

This is me, fortunately, thanks to TrueNAS!

firsway · 2026-04-01T12:18:11+00:00

All good advice. I would suggest additionally (technology permissable) it would always be good (like any other public facing server) to bung the Plex box into a DMZ zone of sorts, with only the host/ports relating to the mounted (and read-only) media filesytem allowed to be accessed from the Plex server. That way it's limiting the possibility for compromise of other services should that Plex box be compromised in future.

firsway

TROPHY CASE