Check out Lawrence Systems on YouTube. He just released a video that talks about this very subject.

Home Assistant comes with a weather app that you can use for scripting.

Get a better cooler?

100% sure.

LAN: 192.168.69.0/24

Fiber: 10.42.69.0/24

Also: yeah, yeah. I know…

I did run a daemon-reload. I’m directly referencing the IP address in my fstab. On my desktop I have DNS turned off for the Mellanox interface.

I’ll have to look into the nfs exports file. I’m using OMV, and I just have my exports wide open. But, I guess I could solve this by limiting the connection to the mounts by client IP.

Marry way out of your league 😉

That’s what I did at least

There’s so many…

No problem.

I actually just learned this lesson recently (in the last week). I have a NAS that I use for my PCs, and it also stores my media collection for Plex, it was natively sitting on the same network as my PCs, as that’s where I was most concerned about network speed. I was having it cross VLANs for the Plex stuff, and it was only when I got a Ubiquiti switch that I noticed that traffic was hitting the router when crossing the VLANs but not when the two subnets were the same.

I’m happy that my hard knock lesson can help someone avoid that same mistake.

Just as a heads up, running your own email server is rife with pitfalls. Even if you set everything up perfectly (which is unlikely for a first timer), you will still run into issues with your mail not being delivered because the big email providers will assume your stuff is spam.

There are guides for doing that, but it really isn’t worth the hassle.

Also, getting a domain name and using dynamic DNS has worked fine for me for years, and I’ve had no reason to pay extra for a static IP.

I do worry that if I do get them I might hammer my router since the traffic streams will have to be routed between VLANs.

The key here is to not route traffic across VLANs. Choose one VLAN to host all your network video content (IP cameras and NVR). This way, since all traffic is on the same subnet, all the network traversal can happen on the switch (even layer 2 switches) and not need to ever touch the router.

Also, if you suspect there will be a decent amount of network traffic that needs to cross VLANs, it’s usually best to add an additional network interface that’s connected to the correct subnet. That way traffic can avoid the router.

I agree. The Unifi firewall leaves a lot to be desired, but their switches and access points are great!

I’m currently running pfSense on one of these, and I have that connected to Unifi PoE switch with two Unifi APs connected to it, as well as several PoE IP cameras. It runs great, and I have no complaints.

If I were redoing it today, I would grab a more modern version of my firewall hardware, preferably with 2.5g nics, but pretty much everything else is great!

If you’re using pfSense anyway, pfBlockerNG provides the same AD related DNS sinkhole functionality of pi-hole without the need for a whole separate machine/VM to manage.

This is definitely something I want to follow too!