Great question, I’ve asked myself the same thing.
First, in my opinion they serve to achieve different things. While openwrt is a firewall, it’d a simple zone based firewall and it designed primarily as router firmware, not firewall software.
Opnsense is BSD based, openwrt is Linux based. Those both haves pros and cons. BSD has serious pedigree in the networking world. Juniper switches are still based on BSD even. Openwrt gets the Linux traffic shaping goodies like cake though.
I chose openwrt because it’s more suited to my environment, where I have 10 VLANs, a 10G fiber core, and want IDS/IPS. Openwrt is meant to be lighter weight, but is less feature-full.
I’m not sure you understand what “objectively” actually means… Care to provide your data in support of your objective conclusion?
Ah it’s fine, we know they’ll be totally fine on their own. I mean, they have their own totally reliable, independent electric grid, right?
It’s just an NTP pool. The device is trying to update it’s time. Likely it made many other requests to other servers when this one didn’t work.
Maintaining up to date lists of anything is a game of whack a mole, so you’re always going to get weird results.
If you’re actually unsure, pcap the traffic on your pfsense box and see for yourself. NTP is an unencrypted protocol, so tshark or Wireshark will have no problem telling you all about it.
That said, I’d still agree with the other poster about local integration with home assistant and just block that sucker from the Internet.
Ran into a similar conundrum. We use mealie for recipe management and occasionally meal planning, but the shopping list is clunky. We resorted to just making a list on a card in Planks. Not purpose-built, but it has worked rather well for us.
I don’t know how you got a picture of me, but I demand it is removed!
That all sounds correct to me. The random port you’re seeing in the logs is a high port, often referred to as an ephemeral port, and it is common for source ports. All good there.
That sort of configuration after the fact would be a fantastic addition, if not already in place.
You don’t need haproxy on the vps at all, unless I’m misunderstanding you. Just route the traffic using iptables hooks in your wireguard config. This is exactly how I manage my email server and it’s entirely transparent.
😆 God the judiciary is fucked up…
Firefox recently passed chrome on the speedometer benchmark
I would love to if I had them! Haha. I’m working on the dashboard right now, which will be part two.
I don’t have a great answer on the IOPS requirement, but I imagine it’s less than something based on elasticsearch/open search based on the reindexing. I’ll try and benchmark it if possible.