So I really can’t say I recommend their hardware…
- they’re shit at accepting contributions
- they’re shit at providing attribution
- they’re shit at providing any support whatsoever to anyone who prefers other hardware (even with their paid software).
In addition to pfSense (which is what I think you're criticizing) and all of its open source, we're upstreaming things to FreeBSD and fd.io VPP
Try this on a fresh copy of FreeBSD 'src':
% git log --first-parent --since="1 year" | sed -E 's/\^.*Sponsored.\[Bb\]y:\[\[:space:\]\]*//p' | grep -i Sponsored | sed -E 's/.*\[Ss\]ponsored\ \[Bb\]y://' | awk '{$1=$1};1' | sort | uniq -c | sort -rn | head
or for VPP, look here:
https://www.stackalytics.io/unaffiliated?module=github.com/f...
https://arstechnica.com/gadgets/2021/03/buffer-overruns-lice...
that "client" (every wireguard implementation is both client and server, but I'll use your label) is still in-use, and still bears our copyright (which Jason tried to strip, but I guess his father the lawyer might have explained the law to him.)
Not seeing where this supports any of the assertions upthread.
Looked at your CV (it's in your profile), you don't seem to last very long in any job. https://cursedsilicon.net/resume.pdf
Funny how you didn't complain about his current employment at AWS, or his previous work at iX Systems (trueNAS, primarily responsible for the port of ZFS on Linux to FreeBSD) or the fact that the whole epoch based reclamation in the FreeBSD kernel is based on his work.
Also you should stop editing your comments after they're replied to. It makes it awfully confusing
Bringing that tech stack to a firewall is a logical move.