[Request For Testing] OPNsense on FreeBSD 10.1

[franco]

Hi folks,

first of all thank you all for giving us a fair chance. We appreciate all comments, feedback, worries and questions. Don’t hesitate to contact us here or in various other places (see below).

As most of you know FreeBSD 10.0 is approaching End Of Life at the end of this month. OPNsense is still based on FreeBSD 10.0, but the necessary custom patches have been forward-ported to FreeBSD 10.1 in the past week. We would love to push out our next stable release 15.1.6 on top of FreeBSD 10.1 including a new feature for base system upgrades which is one of our current weak points for delivering quick and easy security updates for your running installations.

In order to ship FreeBSD 10.1 we ask you to participate in this request for testing by trying the following snapshot for amd64:

https://pkg.opnsense.org/snapshots/

i386 snapshots can be produced based on demand.

Please let us know how the snapshot works for you (bad *and* good) right here in this thread, or use one of the following alternatives.

https://twitter.com/opnsense
#opnsense on Freenode IRC
project@opnsense.org


Thank you very much,
The OPNsense team

[erialor]

I installed OPNsense-201502140847-memstick-serial-amd64.img on my spare PCEngines APU1D4.
Installed fine and no problems with the initial setup - now I'm starting to configure it to replace my m0n0wall-installation.

I created some aliases and started creating Port Forward NAT-rules (Firewall->NAT) using said aliases. In the rules-list the alias gets prefixed with Array (ie. when I created a Port Forward NAT for my mailhost I see 'Arraymailports' as Dest. ports, 'Arraymailhost' as NAT IP, 'Arraymailports' as NAT Ports).

The rules auto-created in Firewall->Rules are not prefixed with Array.


Back to figuring out to migrate the rest of my m0n0wall-config

[SuperJC710E]

Tested this out quickly in my VirtualBox environment. It installs and runs well. No real stuff going on with it, so I cannot rest it heavily, however it appears to be running great!

Thanks,
J

[weust]

As a rather simplictic test I downloaded the ISO and created a VM in Hyper-V on Windows 8.1
2x CPU, 1GB static RAM, 10GB dynamic HDD, 2x NIC (WAN on private virtual switch, LAN on the external switch).

It stalled at 76% while installing, but eventually continued after a few minutes.

Executing Commands
if { -f /etc/installed_filesystem.mtree }; then /usr/sb...

But that might just being a lot that needed writing?

On first boot it gave a bunch of calcry messages. Runtime went backwards from blah usec to blah usec for pid blah on several processes.
But I think I saw that with pfSense as well on Hyper-V.

WAN it not hooked up. Will give that a go this weekend perhaps, but not on Hyper-V unless really wanted.
I have a Soekris net6501-30 I want to give a try next. Haven't configured anything special as of yet.
Memory wise it shouldn't be a problem. Top shows 794M free. The Soekris I own has 512MB.

One odd thing I noticed when checking Services on the webconfigurator, is when you click any of them the menu on the left stays open, except when you click on UPnP & NAT-PMP. Then the menu closes.

VHDX size is 1.75GB right now.

[erialor]

Selecting System -> Setup Wizard, Services -> UPnP & NAT-PMP or Status -> Traffic Graph the menu collapses - doesn't do that for any of the other entries... (dunno if that's intentional).

I feel the menu-entries should/could be a bit smaller - I don't like having to scroll through the menues, at least not when scrolling and hitting the bottom of the menu causes the main-page to scroll.

Otherwise I think I'm quite close to shutdown my m0n0wall and replace it with OPNsense - good work

[franco]

@erialor: Alias prefix issue has been added to the bugtracker https://github.com/opnsense/core/issues/41

It stalled at 76% while installing, but eventually continued after a few minutes.

Executing Commands
if { -f /etc/installed_filesystem.mtree }; then /usr/sb...

But that might just being a lot that needed writing?

Indeed, that is a lot of disk IO checking the full file system for consistency. That delay is the case when read performance is way down.

One odd thing I noticed when checking Services on the webconfigurator, is when you click any of them the menu on the left stays open, except when you click on UPnP & NAT-PMP. Then the menu closes.

Will take a closer look at this.

Thank you for testing. You guys rock!

[franco]

Alright, fixes have been applied for the menu collapse issues of UPnP, Traffic Graphs, Dashboard link and others. Will go into 15.1.6.

[weust]

Good to hear that.
One thing I just remembered, after added widgets on the dashboard it says, per added widget, loading or waiting for data (something like that) but it wouldn't return any value. Only after reloading the dashboard (switching between menu options in my case) it showed the values in the widgets.

Maybe it happened because I added several widgets at once, but that ought to be no problem?

[weust]

@erialor: Alias prefix issue has been added to the bugtracker https://github.com/opnsense/core/issues/41

It stalled at 76% while installing, but eventually continued after a few minutes.

Executing Commands
if { -f /etc/installed_filesystem.mtree }; then /usr/sb...

But that might just being a lot that needed writing?

Indeed, that is a lot of disk IO checking the full file system for consistency. That delay is the case when read performance is way down.

And using a Dynamically expanding VHDX on a not too fast 2.5" HDD isnt helping too then :-)

I got a new mSATA SSD coming in today so I can start testing on my Soekris net6501-30 coming weekend.

[franco]

Yes, some widgets need a full dashboard reload the way they are designed. Hopefully we can mop those up when work shifts to adding features and further GUI improvements, but we are not there yet.

[weust]

One of those things for a rainy Sunday afternoon.
Maybe for the time being a simple message mentioning the refresh of the Dashboard page.

[franco]

The snapshots have been removed and 15.1.6.1 is almost here. We have a couple of fixed and pending issues, but it went smoother than we could have hoped for.  Thank you all for testing.