16.7 development milestones

[franco]

Hi everyone,

It's time to start the list of things we've done since 16.1 was released:

o SSL fingerprinting / blacklisting in the IDS/IPS
o Firewall rules category tags for easy filtering
o CPU temperature graph in system health
o Custom mirror support for firmware upgrades
o OpenVPN client-specific overrides can now be bound to selected servers
o Added RFC 4638 support (MTU > 1492 in PPPoE)
o NTP can now be disabled if required
o New category-based remote ACL support in proxy server
o ICAP configuration aded to proxy server
o Pluggable service infrastructure
o Pluggable syslog infrastructure
o Finished a full sweep of visible GUI pages for improved look and feel
o HTTPS proxy support
o Russian translations 100% completed
o NetFlow export to multiple remote destinations
o NetFlow local reporting frontend
o PPTP, L2TP and PPPoE Servers ported to MPD5
o HAProxy plugin
o Traffic shaping with CoDel / FQ-CoDel
o Firewall alias geolocation support
o Cron GUI and API
o Japanese translations 100% completed
o Dashboard revamp with multi-column support, drag and drop and mini API
o RFC 6238 (TOTP) support for two-factor authentication
o HardenedBSD's ASLR implementation
o High availability page for remote service status and start/stop/restart
o API commands for remote reboot and power off
o Firmware page resume support and cron-based "nightly" updates
o opnsense-patch, the tremendously nifty patching tool
o Traffic graphs frontend has been replaced by a modern alternative
o PPTP, L2TP and PPPoE Servers are now individual plugins no longer found in the default installation
o Pluggable interface infrastructure
o New firewall page for custom scrubbing rules
o No more custom PHP modules
o FreeBSD 10.3
o UEFI/GPT boot media / install
o Suricata 3.1 with Hyperscan support


Cheers,
Franco

[Solaris17]

I actually really appreciate the CPU temp graph. I actually do alot of hardware work in real life and its a huge hobby at home. seeing temp changes over time help me modify the router for better operation. Especially when I deploy the same machine to higher test environments. Temperature is a huge issue since some of the environments are not forgiving. CPU Temp over time really tells me the overall effectiveness of a cooling solution I have employed and is far more beneficial than simply seeing the CPU temp at any given time.

[franco]

We've reached BETA state now, I've updated the list with the latest goodies.

[none]

Hi franco,

I tested opnsense a long time ago, and saw now from roadmap for 16.7 that traffic accounting is to be born

I am now downloading 16.1 to upgrade it for 16.7 and give it a try.

is there a plan for 16.7 to be released?

thanks,

none

[franco]

Hi none,

Schedule for 16.7 is the same as it ever was: 16.7 in July (07) 2016. However, the NetFlow export/report bits will already be available with 16.1.14 this week. We've tested them a lot longer than usual, and now they are ready for general use.


Cheers,
Franco

[none]

franco,

good news. Really. The traffic accounting comes as well? My issue is just to tell how much bytes I got from and to the internet. ISP here may charge and is really good to have the info.

My main issue was this and the dns that I think is fixed. I am running OPNsense 16.1.8-i386 for almost 10 days and is fine here. Can't wait to test this 16.1.14

thanks for the usual polite and quick responses (from all on this forum),

none

[franco]

Hey none,

Yes, I think this is what you're looking for:

https://docs.opnsense.org/manual/how-tos/insight.html

There is talk elsewhere in the forum now to have these number used for periodic reporting, so you can see the past periods month by month or week by week. I think the database is capable of that, but GUI parts for this extension have no ETA at this point.

You can, however, export or browse the data and extract the info from there if necessary. If there are any issues or hiccups a report would be nice to have the current parts tweaked rather than waiting for the next major iteration.


Cheers,
Franco

[qishang013]

I am now using FreeBSD 10.3 in tools make time error

# cd /usr/core
# git checkout stable/16.1 && git pull
# cd /usr/src
# git checkout stable/16.1 && git pull
Then back to:

# cd /usr/tools
# make clean-base,kernel,packages
# make prefetch-base,kernel VERSION=16.1.16
# make ports   ／／  error  code1
# make plugins ／／  error  code1
# make core ／／  error  code1
# make cdrom ／／  error  code1 

[franco]

Can you crop that screen a little less, can't see the last command that failed

Maybe your disk is full, I really don't know...

[shade73]

Is there a way to upgrade a exsisting 16.1 install to a 16.7-rc? So I can help testing.

[phoenix]

Is there a way to upgrade a exsisting 16.1 install to a 16.7-rc? So I can help testing.

You can start the installer from the iso and choose to import a current config backup, that worked a treat for me.

[franco]

Instructions are here... https://forum.opnsense.org/index.php?topic=917.msg10577#msg10577

[calakan]

Hello Franco,
First of all thank you for your awesome work on opnsense. I would like to ask you some question regarding new opnsense 16.7 RC. Last week, i installed opnsense 16.7 via usb drive and still found haproxy in plugin/packages and today, when i installed the same version via cdroom i m not found haproxy on plugin/packages. I wonder what happen to haproxy plugin/packages, is it going disappear from haproxy or.. ?

[franco]

Hi calakan,

The mirrors are currently in maintenance mode. That means the mirror location "16.7" is not reachable. This was done because 16.1.20 and 16.7-RC both point to the same location, which would have made it possible for 16.1.20 users to upgrade to 16.7-RC, because 16.7 wasn't out yet.

We will handle this differently for 17.1 and we're sorry for the inconvenience. The mirrors (and therefore plugins) will be back on Thursday. 16.7-RC will be able to upgrade to 16.7 too by then.


Cheers,
Franco