Messages

The wizard will rewrite your settings made via the console. Please skip the wizard by clicking on the OPNsense logo in the top left corner.

There is a test kernel build to address the panics, which aren't present in FreeBSD 10.1-RELEASE. To install this version go to a root shell and run:

# opnsense-update -kr 15.1.10_altq && reboot

Glad to hear that. The blacklist patters are quite arbitrary and prone to false-positives like any good blocker or security product out there ;)

Will use tunnelblick's version beginning with OPNsense 15.1.10.2 or 15.1.11, whichever comes first:

https://code.google.com/p/tunnelblick/wiki/cOpenvpn_xorpatch

Commits:

https://github.com/opnsense/ports/commit/ecab736b62f33189a549235434b04498daaffd7c
https://github.com/opnsense/tools/commit/f87635ed524beedebe827953f8b24f5e51627805

Will open a FreeBSD ports PR to see if they will merge it upstream.

Thanks again for mentioning this. :)

Hi pierrefrancois,

thanks for the suggestion and step-by-step guide. I'll push that into the ports tree as a separate OpenVPN option with the proper FreeBSD port style so that we may be able to push it into the FreeBSD ports tree. :)

Keeping track of this via: https://github.com/opnsense/ports/issues/9


Cheers,
Franco

o try loading  https://yourip/graph.php -- it should show an empty but visible graph.
o try upgrading to 15.1.10.1 (or at least try the live image)
o try disable all plugins, delete caches and cookies

Do you have a different user added or changed access permissions?

[squidguard]

I'm adding squidguard and e2guardian as optional packages, but there is no immediate plan to implement GUI code for easy use and integration. Rebuilding the plugin collection takes time and a supportive community and more infrastructure work which we are about to start now that the MVC GUI is almost ready for its prime.

tinyproxy we also have as a package, I am not completely sure about fail2ban at this point though.

I could not reproduce both of these reports.

The DHCP range for LAN is set up correctly.
The Gateway was created for LAN and properly added to interface configuration.
The DHCP setting for WAN works.
The static IP setting for WAN including setting the gateway works.

If the error persists please provide accurate steps to reproduce this.

Hi everyone,

here comes a quick hotfix for a pressing VLAN regression we've been hearing about today plus 3 more minor additions. These are the patch notes:

o interfaces: fix interface rename regression that prevented VLANs from being set up
o firmware: clean up downloaded packages after installation
o logging: prevent spurious pgrep-related messages from being logged
o config: fix Google Drive backup accounting off-by-two

The update available via the GUI or console firmware upgrade. No restarts necessary, except for those being affected by the VLAN regression. Let us know whether this brings you back to normal.

Both LibreSSL and OpenSSL are available as of now!


Stay safe,
Your OPNsense team

Really horrible typo from my part--I am sorry. 15.1.10.1 will be out later today.

FYI: https://github.com/opnsense/core/commit/4b197af1eef2020bf12a9cf1cd634287548bbce8

Maybe an AdBlocker or another plugin preventing the graph from showing up. I don't know how else to debug this if the graph does work in general...

Glad to hear this was easy to fix on your side. apinger doesn't do IPv6, at least the support hasn't been enabled, but I can take a look if that is fixable... :)

Hi Lukas, looks like interfaces are not renamed properly. Does a restart of the box remove this issue? I have replaced a couple of function calls regarding ifconfig handling and this is likely related. I'll take a look.

It would be helpful to know what kind of input triggered this or how to reproduce. In general, the error tells you the configuration went wrong in the user-specified settings.

Yes, exactly.