FreeBSD-src VS pfatt

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

See https://github.com/MonkWho/pfatt/blob/faa80d09f9c00e4a67bc3cacf2eab5a1631ec3f9/bin/pfatt.sh#L142-L151https://github.com/MonkWho/pfatt/blob/supplicant/bin/pfatt.sh .

I read through the PFATT Guide by MonkWho, but this setup was different. Setting up PFSense as a man in the middle to the gateway. I only have 2 Ethernet ports on my PFSense box, so this physical setup wouldn't work too well. I couldn't find mention of the supplicant method anywhere.

pfSense/OPNsense: https://github.com/MonkWho/pfatt

The bypass methods you are referring to were for prior models of the att router. My understanding is your model is not compatible. See the GitHub repo.

For ATT there is a wonky workaround for their gateway (used it for a while, not sure if it was me or pfatt but it reduced speeds): https://github.com/MonkWho/pfatt

I then used this pfatt.sh script and followed the instructions here: https://github.com/MonkWho/pfatt/tree/supplicant

Word of advice... Don't bother yourself with supplicant mode. It supposedly broke around 2.45. spent many of hours trying to get it to work again but it was a no go. Also ng_etf should be preloaded so you shouldn't have to bother with that. See the defacto replacement GitHub for this and other issues.