FreeBSD-ports VS FreeBSD-src

Currently running pfSense 2.6 and pfBlocker 3.2.0_4

I see that the package system_patches 2.2.2 and its installed but I see here https://github.com/pfsense/FreeBSD-ports/commit/de76acb1d15fdff5587739ffdf6bb92eeb6b6e22 that 2.2.3 is apparently there but not able to see it as an update.

Running 23.05, why is suricata still on 6.0.10 version while 6.0.11 brings some netmap fixes and was committed to devel branch almost a month ago ? Update Suricata GUI package to support version 6.0.11 of the binary. · pfsense/FreeBSD-ports@7b3e46e (github.com)

The latest WG package version in pfSense+ 23.05-devel is currently 0.2.0_1, and the details of the commits on GitHub say "WireGuard support is now included in base."

I have installed PFBlocker Devel 3.2.0_3 on PFSense+ 23.01 and it works perfectly! I was able to install and do a basic configuration. I also added a feed or two for blocking ads, adult content etc. When I click on Update or Reload, I'm unable to use the internet until it is done reloading or updating and everything is back to normal after. It doesn't take very long and this is a home office so I'm not super worried about it. However, some of our clients made some changes without knowing this and caused some minor outages.

After upgrading to 3.2.0_2 there seems that there are no longer custom options which used to include pfblockerng inc is that regression or correct? thanks.

I suppose what I am expecting is for the following files to be in '/var/unbound': https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfb_dnsbl.safesearch.conf https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfb_dnsbl.youtube_restrictmoderate.conf

====>> 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