FreeBSD-src VS pfSense

====>> Removing leftovers from git repo https://github.com/pfsense/freebsd-src.git (devel-12) ====>> Retrieving updates from git repo https://github.com/pfsense/freebsd-src.git (devel-12) ====>> Updating git repo https://github.com/pfsense/freebsd-src.git (devel-12)

https://github.com/pfsense/FreeBSD-src (devel-main branch, which it defaults to)

It's a niche use case involving tagging packets on sr-iov VFs. See https://github.com/pfsense/FreeBSD-src/commit/15873ac96fcc4e81a25d35e735a1fbae9d727360

I resolved the issue with OPNSense by recompiling OPNSense's dhclient with a patch submitted a while ago to pfsense: https://github.com/pfsense/FreeBSD-src/commit/15051bfd014b2c1e6972a55f58e25cd6907cac8e

FreeBSD source - the source code, with patches of the FreeBSD base.

But how are they supposed to know that people are running some modified FreeBSD version with pre-release patches? That is my point. It's not like pfSense is going out of their way to document what kind of changes they're including in their FreeBSD fork.

But the community edition is fully open source? As available on github: https://github.com/pfsense/pfsense https://github.com/pfsense/FreeBSD-src By core do you mean like the main kernel. I don't agree that a company should take someone else is work modify it and then pass it off as there own. to me that is just morally wrong. so in which this falls under false advertisement. Tbh I can see this as a good reason why people are moving away. looks like I have some labbing to do.

Here's the pfSense 2.4.5 branch

> This branch is 10723 commits ahead, 281789 commits behind devel-12.

https://github.com/pfsense/FreeBSD-src/commits/RELENG_2_4_5

One option is Firewalla Gold Plus, or you could buy a mini PC like it and run pfSense/OPNsense yourself.

Download and install pfsense as a virtual machine or partition: https://www.pfsense.org Configure it with the rules you want: https://youtu.be/VAGFGppSt74 Play with it, but be careful because it will block all traffic unless you check everything properly.

Another option is Firewalla, or buy a mini PC like it and run pfSense/OPNsense yourself. Two similar concepts, with the cost being either money or your DIY time. A lot of Firewalla users say that it's much easier for home use than pfSense/OPNsense, so you might find it worthwhile to spend a little more on it upfront and have to tinker less.

If you want firewall, I think you can use https://www.pfsense.org/ or https://opnsense.org/ , maybe running on an old PC or a Raspberry Pi. Not sure.

I've recently started using OPNsense. It's similar to pfSense, but seems to be considered a little more user-friendly.

For most router issues, I recommend people always put them in to dumb bridge mode and put a proper firewall like pfsense or opnsense as your gateway.

I have found that my historical average packet loss is about 0.02%. Something distinctly changed around 4/20 of this year, and now the average packet loss has gone up to 0.05% with spikes even higher, associated with periods of elevated ping times. It rarely did that before. Typically the IPv6 stack has more problems than v4 (especially an incident of packet loss on 4/28), and neither has been trouble-free since I started service in early 2020. My data comes from a pfSense installation.

I have done this using the Pfsense