How to test the development version

Started by franco, July 08, 2015, 03:32:07 PM

Previous topic - Next topic
July 08, 2015, 03:32:07 PM Last Edit: August 03, 2015, 10:42:24 AM by franco
Hi everyone,

quick note for 15.7.1 and up: you'll be able to test the development version snapshot which is being refreshed every time a stable update is released. In order to switch, drop to the console and type:

# pkg install -y opnsense-devel

DISCLAIMER: Helping to test the development version may cause OPNsense to get better faster. :)

We are going to add bleeding edge features to the development version whenever we're not sure it's working 100% yet and look for any type of feedback so that once it is merged to the stable version, it really is working as intended.

Some features may not work all the time, so be careful still.

If you choose to go back, type:

# pkg install -y opnsense

Cheers,
Franco

Quote from: franco on July 08, 2015, 03:32:07 PM
Hi everyone,

quick note for 15.7.1 and up: you'll be able to test the development version snapshot which is being refreshed every time a stable update is released. In order to switch, drop to the console and type:

# pkg install -y opnsense-devel

Disclaimer: THERE ARE NO GUARANTEES THE DEVELOPMENT VERSION IS IN A WORKING STATE. PLEASE DO NOT USE IT IN A PRODUCTION SETTING.

If you choose to go back, type:

# pkg install -y opnsense

Currently, only amd64 packages support this as an experimental feature in 15.7.1. If all works well, we'll keep this MO for all flavours of 15.7.2 and beyond.  :)


Cheers,
Franco

Franco,
will there be a announcement here each week (since thats what stable is on) on whats changed between development snapshots?

or do i need to track commits on github to see whats changed during the week?

thank you for what you guys do.

July 27, 2015, 07:06:10 AM #2 Last Edit: July 27, 2015, 07:08:33 AM by franco
After doing two of such releases it looks like opnsense-devel is a development / staging area for new features or fixes that do not directly apply to stable (or should not). There is no release engineering involved, we just take the latest development state. Running opnsense-devel may or may not work so for a production environment that likely is too much trouble.

We try to move the new features to stable as soon as we can now. It may change later or is decided on a case by case basis. The good thing about the extra package is that it can help to "try" certain features for interested users without the need for git or other development skills.

All in all, we will not have any associated release notes for opnsense-devel, but will ask for test coverage from time to time or give individuals a chance to try out specific bug fixes / features without sacrificing stability of the actual release track.

To help with the testing, do you recommend i use real hardware or can i use a virtual machine just as well?

VM is perfectly fine. Sometimes I find it harder to set up a proper VM routing though, but that heavily depends on hardware being available and available time.


If you use the VM directly connected to the internet that should never be a problem.
Unless you got a very funky VM Switch setup.
Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.

Thanks for the info! it is connected trough a dedicated networkcard directly on my production firewall :)
I should be covered! 8)

Ah, using the dedicated firewall as gateway, etc?

I only use OPNsense at home, and have a couple of VM's all with the same MAC addresses so switching is easy.
Without resetting the cable modem each time :-)
Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.


Setup a DMZ between the two and it's really awesome ;-)
Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.


Am I dropping to console to update every time?
Supermicro A1SAM-2558
8GB DDR3
80GB WD Velociraptor

HP ProCurve 2520-----> Asus RT-AC66U

You can safely upgrade into the next opnsense-devel using the GUI, too.

November 28, 2015, 10:21:55 PM #14 Last Edit: November 28, 2015, 10:24:31 PM by Solaris17
Before enabling IPS mode it is understood that I disable all offloading. 2 of the 3 are disabled by default on my setp at least. Am I correct in assuming I should also check (disable)  " Disable hardware checksum offload" before enabling?

also there is a bit of a typo in the informational regarding enabling IPS

Quote
enable protection mode (block traffic). before enabling, please disable all hardware oFFloading first.
in advanced network