Messages

Problem is solved, I had to add a manual VPN: IPsec: Security Policy Database entry. After this and a restart of the IPSec service it worked as intended.

We have a OpenVPN server setup The clients can access resources through a IPSec VPN tunnel. We are trying to create the same setup with the new OpenVPN intance option but it does not work. The traffic is not routed through the IPSec tunnel. All firewall and the one-to-one BINAT rules are created similar.

The OPNsense version is 25.10.2 (Business).

I have read somewhere that there was a problem with the "Redirect gateway" option with the new instance. I assume the "default" option should be the right one but I have selected every possible option but it does not work.

While upgrading from OPNsense 23,7 to 23.7.1_3 the following error did appear:

An API exception occurred:

/usr/local/opnsense/mvc/app/controllers/OPNsense/Core/Api/FirmwareController.php:41: Class "OPNsense\Base\ApiMutableModelControllerBase" not found

The upgrade process did continue and OPNsense seems to work just fine after the reboot

So no idea what this message means but just mentioned it.

The most-watched technology channel on YouTube, Linus Tech Tips, has switched for their main router from pfSense to OPNsense.

Start from 23:48: https://www.youtube.com/watch?v=pnv87pW6d-U

Since the upgrade to OPNsense 22.1.9 I have this problem:

In the LAN DHCP server there are a couple of static mappings with a hostname set. Before I could ping the hostname and get the internal IP address back. Some of these hostnames also exist on the internet. I have set my OPNsense as DNS server for my clients but when I now ping a hostname that also exists on the internet I get the internet IP address back and not the local IP address. If I ping a hostname that only exists on the OPNsense and not on the internet I get the local IP address back. What has changed in version 22.1.9 that causes this behaviour and how can it be fixed?

SOLVED:
Restarting my PC did not resolve the issue but a IPCONFIG /FLUSHDNS did. I still do not understand how this could happen but for now it has been solved!

Does OPNsense have support for IPoE WAN connections. In particular for KPN Corporate Internet through IP over Ethernet (IPoE) (also known as Numbered Link)?

Today I finally was able to migrate from pfSense to OPNsense on my Fitlet2 mini PC. With the version 19.1 which is based on FreeBSD 11.2 I could overcome the previous problems with the Intel Celeron J3455 CPU (Apollo Lake series). Everything looks good, the down- and upload speeds are about the same as with pfSense > 800Mbit DL and > 900Mbit UL.