Good news, everyone! This Friday the 21st of August, 2015 marks a great day for open source and the longevity of pfSense: the current FreeBSD source code and ports tree including modifications have been made available by the team over the last two days.
It’s not often that I come across people that regularly use the word “lies” to address others. They do all kinds of dirty tricks, turn their narratives into truth and label all derivation thereof a blatant and offending lie. Gaping holes in their reasoning exist, but you’ll get a personal brush-off if you dare to go there. Opinions are not valued. Ideas and competition are bad. Discrediting others is a key element. They’ll point out simple flaws to show you they’re better, but missing the bigger picture: they messed up hard, and refuse to deal with their own inevitable undoing.
I have to say that’s not my statement, but it’s very much true. Today we released OPNsense 15.1 including all of its source code. It has been the accumulation of work of the better half of a year for most of us and I think it is the right step at the right time. The lovely BSD community (FreeBSD in particular) deserves a project that listens to its users and adapts no matter the cost, no matter the hardship. Hard choices will have to be made along the road, but for now all that matters is that we are finally on this road together. I feel privileged to be a part of it. That’s all I have to say. :)
Just to get it out of the way: the simplicity and effectiveness of netmap(4) is an achievement in itself. I’ve had the opportunity to work on similar proprietary code in my past, but we faced ever new complications and bottlenecks. There are no immediate problems with netmap(4). I’m especially intrigued by the zero-copy feature, which boosts both latency and throughput considerably.
Happy DPI release day, everyone! Three months ago we were talking about how DPI technology could be improved further. Essentially, we were not satisfied with the current state of things. And there is no viable BSD-licensed code that’s fit for use with high load and mission critical networking infrastructure. Then we read a lot of papers floating around regarding the topic and started hacking. Now we proudly present our Lightweight Inspection to the public.
Our key requirements were as follows:
Hey folks, as promised earlier, I released a bunch of code dubbed ‘peak’, which mainly features nuts and bolts for C projects. What’s so special? There are memory allocation wrappers checking consistency in your C code so you’ll always get a sensitive error message with file and line attached. This helps you to better trace buffer overflow/underflow issues. It also features a preallocated memory pool, print wrappers and byte access macros for little and big endian architectures alike. Mind you, this is still work in progress. Comments and contributions welcome.