Thanks, I was wondering why I was't seeing new builds.

Seems so - But not to fear.  We can start a new thread and nag the devs incessantly about things we want in 2.2

To see what is the latest commit contained in the build:

[2.1-BETA1][admin@xxx]/etc(15): cat /etc/version.lastcommit 990fa101b6a2ce09e813a8d58f0f43178e54fc45

Then use this number to display the commit in GitHub:
https://github.com/pfsense/pfsense/commit/990fa101b6a2ce09e813a8d58f0f43178e54fc45
Other interesting data about the build state is in these files:

[2.1-BETA1][admin@xxx]/etc(18): ls -l /etc/version* -rw-r--r--  1 root  wheel  10 Feb  3 08:52 /etc/version -rw-r--r--  1 root  wheel  29 Feb  3 09:08 /etc/version.buildtime -rw-r--r--  1 root  wheel  41 Feb  3 09:08 /etc/version.lastcommit -rw-r--r--  1 root  wheel   4 Feb  3 08:52 /etc/version_base -rw-r--r--  1 root  wheel   4 Feb  3 08:52 /etc/version_kernel

Dont know if this has been reported.

Trying to create a new Internal-CA
Key Length 4096
Hash SHA512
Days 3650
CountryCode: Mil

Fill in the rest of the fields and you will get this error message.
The following input errors were detected:

openssl library returns: error:0D07A097:asn1 encoding routines:ASN1_mbstring_ncopy:string too long

If you dont choose Mil you can create an internal CA.

FWIW.

@WetWilly:

Is "Multiple DHCP pools outside of subnet"

Anywhere on the roadmap?

Or is there any smooth way to a DHCP-range outside of LAN interface subnet?

It's closer to being possible, but not going to happen any time soon (maybe 2.2, if someone has the time or funding for it).

There is no way to do DHCP for another subnet on an interface currently. That's a question for another thread, though.

Locking this thread for now, separate threads are better from here on.

The purpose of this thread was for problems specific to 2.1 – meaning, package X worked on 2.0.x, but not 2.1. Most of those have been fixed, but packages that were broken on 2.0.x are also likely broken on 2.1 (e.g. stunnel, vhosts, freeswitch) and that's beyond the scope of what this thread is meant to deal with.

I was originally doing triage trying to fix what I could on things to get things in decent shape, but we're at the point now where the package maintainers for items with remaining issues need to step up and fix what few things are left. In the cases where there are no active package maintainers for certain packages, someone with the time/knowledge may have to take them on.

dont work anymore with OpenVPN gateway still getting Gathering Data…

Yes, the GUI version only does so after a firmware update.

The CLI version can be done at any time.

Please start new, separate, threads for issues, rather than trying to pile on this old thread.

@johnpoz:

Curious should maybe the ipv6 be a sub section of this?

Actually, no, there were some rudimentary ipv6 functions outside of 2.1, and there will continue to be ipv6-specific issues even after 2.1 is released and this board goes into lockdown.