- I'm not lying.
From the URL
---
The Complainant is the owner of the European Union trademark registration Nos. 012771457 for OPNSENSE (figurative mark), filed on April 8, 2014 and registered on August 20, 2014, for goods in class 9, and 016287716 for OPNSENSE (word mark), filed on January 26, 2017 and registered on May 9, 2017, for goods in class 9.
The Complainant also owns the domain name <opnsense.org>, registered on September 4, 2014, at which it promotes and enables users to download its open-source OPNSENSE firewall.
The disputed domain name <opnsense.com> was registered on April 8, 2014, and is not pointed to an active website.
---
I want you to look closely at the date April 8, 2014, and then I want you to look for anything that occurred before that date, vs. all that occurred after.
- We already have a linux-based product (TNSR).
Bringing that tech stack to a firewall is a logical move.
- yes, I'm sure that FreeBSD actually does enjoy all of his work on OpenZFS and epoch-based reclamation.
- the routers were based on the Vyatta stack.
The WiFi APs were not
- nobody stole anything.
- yes, I contracted with Matt Macy, and I'd do it again, but he's well-employed now.
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.
- I ask that you provide evidence of your assertions:
- 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...
- this is why TNSR was API first with a CLI. https://docs.netgate.com/tnsr/en/latest/basics/config-databa...
We have a lot of requests for a GUI, so one is in development.
- the entire desktop line from Netgate is fanless.
- > They hired the original author of pfsense to build them a firewall based on Debian from scratch when they realized vyatta wasn't going to meet their needs. The UDM kernel is very much not OpenWRT
You're (perhaps unintentionally) also spreading bad information here.
The original 'author' of pfSense was Scott Ullrich, not Chris Buechler. While they were partners in the project, Scott was technical, and Chris did a lot of work back then on documentation, by by his own admission back then, "I am not a developer", and this, even though he was CTO.
http://freesoftwaremagazine.com/articles/interview_with_jeff...
Ubiquiti originally hired two of the devs out of Vyatta to maintain their fork of the Vyatta codebase. These two were known on the Ubiquiti forum as 'stig' and 'An Chen'. Both left in the first half of 2016, and then (and only then) did Ubiquiti hire Chris Buechler, in an attempt to maintain and extend the Ubiquiti firmware. Chris has since left Ubiquiti and is now at Alta Labs.
- > I'd love to see OpenWRT take a (deserved) bite out of the "SMB firewall vendors" like Netgate
I'll just leave this here: https://www.netgate.com/blog/pfsense-software-embraces-chang...
OPNsense are unlikely to be able to make this transition, as they can't even reliably work on the FreeBSD kernel.
- ASICs require years to develop and aren’t flexible once deployed
- When originally published they wouldn’t even ack Patrick Kelsey, the author of libuinet or that they had forked libuinet.
Now they say this: “Thanks to libplebnet and libuinet this work became a lot easier.”
F-stack is literally forked libuinet using DPDK instead of netmap.
The net-net is that Kelsey took his work private and tencent isn’t advancing the work.
Back in the day I was sponsoring work on libuinet in order to move enough of the kernel needed for a security appliance to libuinet to underpin a performance improvement for pfsense.
Then Tencent did what they did, Patrick reacted as he did and that was over.
We pivoted to VPP. But back in 2016 it also needed a lot of work.
- Didn’t Cutler design Mach?
- The auto bailouts were started by Bush
- Scrubbed
- We had that in 2020
- And the current administration is unlikely to help Taiwan in the event of said invasion.
- And how will not having semi-reliable data affect Wall St?
- Born and raised in Vegas. My father was also born and lived his entire life in Vegas.
You’re not wrong.
- By this logic, Sprint is now in a pickle.
- Who is to say that Sprint won't get acquired by AT&T?
- The license of glibc is a red herring. The issue is google's copying of GPL headers.
- perhaps when I get my cupcake fully assembled.
(I'm the guy who made the Lego case for iPhone 4, so I've got the dimensionally down.)
- yes
- Left out of all of this is that Sam Leffler found this bug when he was incorporating the OCF into FreeBSD.
Yet the team at OpenBSD has never credited him.
Why?
- Rob probably just wanted into the kid's pants.
- I live in Hawaii.
How does bad faith exist when the domain "opnsense.com" was registered a full 8 months prior to the January 2, 2015 OPNsense announcement?
Point in fact, we published nothing. That website was not ours. We pointed the domain at it.
you also are ignoring this bit: ---
However, in contesting the Complainant’s supplemental submissions made by the Complainant to substantiate the asserted use of the trademark before the registration date of the disputed domain name, the Respondent introduces new elements which, in the Panel’s view, are relevant for the assessment of the Respondent’s position in this case and will thus be taken into consideration.
Indeed, in its Supplemental Filing, the Respondent states that a document submitted by the Complainant in its Supplemental Filing (as Annex 17) does not demonstrate the Complainant’s use of the trademark OPNSENSE but provides, instead, evidence of use of a trademark PFSENSE in which the Respondent has rights. The Respondent also informs the Panel that it is the manager of Electric Sheep Fencing LLC, a United States company which owns the United States trademark registration No. 3571276 for the trademark PFSENSE, registered on February 10, 2009 claiming first use as of February 19, 2005, for services in International class 42 relating to technical support services, maintenance and development of computer software; and of the International trademark registration No. 1176766 for the trademark PFSENSE, registered on August 28, 2013, for goods in class 9, including computer security software. The Respondent also states that its company Electric Sheep Fencing LLC has rights in a book referenced on the document submitted by the Complainant entitled “pfsense.org The Definitive Guide to the Open Source Firewall and Router Distribution”.
---
OPNsense were using the pfSense mark, and we were taking legal action to stop them.