Messages

We're finalising our internal meta-discussion on the roadmap and we've come to the conclusion that we are going to provide the following:

(1) Reachable goals for 16.1
(2) Vision and wishlist for 16.7+

This allows us to remain flexible by not locking in on 16.7 just yet while staying transparent on the matter of what happens after 16.1.

Wonderful, exactly what I intended: a list of development goals, transparency and an outlook on possible interesting things with a little overhead of futuristic aims that might or might not be achieveable, but could make the project interesting and lively in the eyes of users, testers, developers and enthusiasts, new and supporting ones.

We need a thank you button on the forum :D

You can applaud. Its on the left side under the forum ID.

What Franco is trying to say is, OpenSSL became a headache for maintainers after a sudden burst of several critical vulnerabilities . So the apparent long term fix was forking and coming up with LibreSSL . :)

This is not wrong but also not the exact truth!

As the LibreSSL guys pointed out over and over, they did the fork prior to the Heartbleed security bug, see: [https://wiki.opnsense.org/index.php/LibreSSL LibreSSL & Heartbleed].

The Moschip MCS7840 with USB 2.0 specification and RS-232 DB9 standard specification compliant device is worth a try (20Eur)

http://www.amazon.de/Adapter-Converter-Controller-Moschip-MCS7840/dp/B00CP21YCO

O.K.

I would like to add

* Unattended / Automated update/upgrade both kernel and ports/plugins
* possible a web content filter

(even thinking about 16.7 now feels a little weird, but good)

Suggested just because since now we had development branch 15.7 and future branch 16.1, so I thought this would continue..

 Lol - yes exactly, I put it in because of the little spicy element that comes with it, in an ironic undertone : and Jim made my day!

I like this new section in the forum!

Chol, apparently it's not written by Zedestructor. Thought he was someone else on the pfsense forums, but on IRC last night he said he didn't write it.
No clue how I got the link then, I know it's from IRC though.

Anyway, https://forum.pfsense.org/index.php?topic=78062.0

Well, actually, thank you for the link!

[15.7]

We have reached the first milestone Production Release of OPNsense, namely 15.7, which left development branch just today (July 2, 2015)!

16.1 is in the development branch of OPNsense as of July 215 , also!
From the roadmap on opnsense.org one can look up  these 4 aims for 16.1 so far:

• Package / Plugin implementation
• Security updates
• Replace ACL
• Unattended / Automated installation

Oppinion: Would be good if we had a list of far away topics for 16.7 also.

I would like to start a list if it was appropriate. If not just say so. We could agree and try to get in contact with possible developers, or get developers interested, which would be interested in (long-term/short-term) cooperation!?

ROADMAP for 16.7

• NanoBSD image w/ 2 working slices
  
• BIND alternatives ?: NSD, Unbound (DNS server)
  
• ALt. hardwareplatforms : MIPS64^)  , ARM$)
  
• IPv6-style forms etc. pp. in the GUI %)
  
• ext2*)
  

Notes:
^)  FreeBSD 10.x on MIPS64 - Ubiquiti EdgeRouter Lite
$)   FreeBSD/ARM
%)  OpenWRT würfelt IPv6-Präfixe (german, "OpenWRT casts random IPv6-prefixes")
*)   just kidding ;)

To be fair, here is what pfSense has to say. https://blog.pfsense.org/?p=1815

The timing is impeccable; if I didn't know any better it would look like they did not want 15.7 to have the fix. A day earlier and we would have picked it up gladly. :)

2.2 .. 2.2.1 .. 2.2.2  they seem to try to get close to our (weekly) bug fix cycle  ???   ;D

Features and status of FreeBSD's Ext2 implementation - BSDCan 2014

Ad and me are happy about this in a way you can't imagine. :D

O.k. I admit it , I am not really sure, if I got the funny part here, but I do not take the following statement to seriously, that's for sure:
"Some free advice: If you don't understand the system, don't attempt to disguise your lack of knowledge with infantile rambling, and anyone who thinks ext2 is an appropriate primary filesystem for FreeBSD has questionable motives and poor taste." (pfSense Digest - filesystem corruption: closed, by Jim Thompson July 2, 2015) -- Actually this statement got me tears in my eyes .. from laughing !

The timing is impeccable; if I didn't know any better it would look like they did not want 15.7 to have the fix. A day earlier and we would have picked it up gladly. :)

Can't agree more..it is a pitty that the whole a idea seemed to be to wait until 15.7 was released.

Its so absurd, this realy doesn't need more words...  8)

There is a nice topic from Zedestructor over at pfsense forums I've been meaning to give a proper go.
Which requires suricata :-)

Weust, would you mind giving the hyperlink?

We are testing the final images now. Hopefully in two hours. We have the doubled amount of testing because we are also releasing official LibreSSL images. :)

Thumbs up, Franco! Brave!

[Hipp hipp huray!]

as promised, here are the achievements of the last 6 months of work, ever since we've released 15.1 in January

Thank you very much, and "Hipp hipp huray!"

Do you have scheduled a release date so far?

[Re: UFS SU+J sync]

Re: UFS SU+J sync

Data loss due to vfs buffering


FreeBSD 10.1 - Deadlock on reboot with UFS tuned with SU+J


Hang on shutdown/root unmount after FreeBSD 10.1R


Features and status of FreeBSD's Ext2 implementation - BSDCan 2014

[OPNsense 15.7]

 :) Like that:

In all that we do, we try to avoid adding kernel/base patches or reboots or changing the behaviour away from FreeBSD defaults.

OPNsense 15.7 .. steady as she goes!

[config.xml format]

Out of this:

Import from 2.1.5 works like a charm, but constant changes in the config.xml format since then leading up to 2.2.2 prevents a fully functional import. We decided not to support the import due to licensing issues,

CMB makes:

Either all of OPNsense's code has "licensing issues", or you can continue to pull in code changes.

Seems to me like a misunderstanding!


In regard to fight for one's own company:

I hate politics, and we all have much better things to do with our time. But if I'm forced to defend my company and project, I'll do so.

... be it as it may, politics and all, but how will CMB defend against "Freedom Speech", exactly.
If I was to say the product 'CMBsense' or the distribution 'pfCMB' had-in my view- licensing issues, who on earth would "fight" that - even go on and threaten me?

I've never heard a peep from anyone claiming we were going closed source until you guys started putting out garbage, and now it's something I have to defend against routinely.

As CMB stated, "us guys" did not say so, either! The only garbage I can see here is the misconduct in use of language.

However, the historical record has some rather erratic and possible offending in nature licensing decisions made by ESF - and that is a fact.


IN CONCLUSION:
In light of this statement:

I do find it very unfortunate that it seems we have become adversaries as that is not what we want at all.
The fact is that we have forked the code from an earlier version and only a few files came from a binary distribution that you had put out with the same 2-clause BSD license. We have made a full list of all files and their origin just to defend our case if ever needed.

...the issue  seems to be a very personal problem of the pseudonym CMB.

Hallo Thagor,

dazu nur kurz:
#1 es gibt WiFi Karten, die koennens parrallel, und welche die koennens nicht. 
# deine Karte koennet defekt sein (oder die Antenne)
#2 deine Karte koennet eine Miskonfiguration haben
#3 du koenntest den falschen Treiber geladen haben
etc. pp. .........

Ohne weitere, spezifische, Problem erhellende Angaben deinerseits, kann Dir wohl nicht geholfen werden.

Ich wuerde nach der genauen Bezeichnung der WiFi Karte schauen (d.h. evtl. Ausbauen)  und dann im WWW recherchieren.

computer hardware wiki

Ich hoffe dies hilft Dir erstmal :)