Messages

No, just check the updated help texts for masks in pipe and queue, they are explaining it very well.

I saw the updated explanations after updating OPNsense to 18.1.6. Thanks

I'm not sure why it's called destination/source for mask, maybe a placeholder, cause it means something different like intuitively you would expect.
Mask defines how a given bandwith will affect clients and not their direction.

Destination means share the total bandwidth of this pipe among all connected clients.
Source means provide all connected clients up to a maximum of this pipe configured bandwidth

I was always wondering this myself.
So to be clear @Ladeschale , masks on both download and upload pipes should be set to "Destination" if we want to evenly share the available bandwidth among connected devices within each pipe?

I have been trying to get this to work for a while too, no luck. I plan on spending sometime this weekend investigatng.

Has there been any progress on routing selective traffic over OpenVPN on v18.1.4? I haven't been had a chance to update and test the routing on v18.1.3 nor v18.1.4. Still on 18.1.2_2.

I did fresh install of opensense and everything is working for me now :), dont ask me how. The only change I did in first try is to select LibreSSL under firmware settings..now I just use default OpenSSL.

Anyway..VPN works, policy routing works, I only need to do additional testing regarding DNS leaks..

So what you are saying is that if one uses OpenSSL rather than LibreSSL, VPN NAT routing works on v 18.1.2_2?

Sorry about that, there should be no spaces. That was a mistake on my part. I have fixed my post. Glad you got it to work.

For first booting into OPNsense, hold down the <ESC> key when you see the OPNsense menu come up. This will automatically bring up the loader prompt or you can just choose "Option #3" from the menu.

Step #1) when you see the "OK" prompt type the following:

set hint.ahci.0.msi=2 <press Enter afterwards>
boot <press Enter afterwards>

it should boot up fine now

Step #2) Once you have installed OPNsense, reboot without the USB installer, repeat STEP #1. Once you're at the main OPNsense menu, open a shell and add add the settings to /boot/loader.conf.local:

hint.ahci.0.msi=2

Hi Andrea,

Well, I'm a little stuck too... I wrote the original HOW-TO for getting this going under 17.x but this new version is not playing nice.

I've been trying a combination of settings but no luck so far, fingers crosses, this could just be a bug that gets corrected in the next update.

Will keep everyone posted on here if i find a work-around.

Cheers :)

Hi @M4DM4NZ have you been able to make any progress on this issue?

Hi,
I'm using a fitlet 2 with an m.2 ssd card (64GB). I have an installation running with the following versions:

OPNsense 17.7.12_1-amd64
FreeBSD 11.0-RELEASE-p17
OpenSSL 1.0.2n 7 Dec 2017

I tried to install the new version. First I tried with the console UI option. Starting was not possible anymore. I had to downgrade again - which fortunately worked without any problems. Now I tried to do a clean install, but the problem is, that the installer does not detect my ssd. Still, the installed version is booting and working.

I was able to boot OPNsense v18.1 on my filet2 by doing the following:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Boot filet2 into its BIOS with USB installer plugged in.
1) Go to the boot options and make sure the USB installer is set to boot first.
2) Go to chipset > then i believe the last option, I think it is "South-something". There, go to SCC options, and disable the SD Card.
3) Save edits and exit. Computer will reboot.

For first booting into OPNsense, hold down the <ESC> key when you see the OPNsense menu come up. This will automatically bring up the loader prompt or you can just choose "Option #3" from the menu.

Step #1) when you see the "OK" prompt type the following:

set hint.hpet.0.clock=0 <press Enter afterwards>
set hint.sdhci_pci.0.disabled=1 <press Enter afterwards>
set hint.sdhci_pci.1.disabled=1 <press Enter afterwards>
set hint.ahci.0.msi=2 <press Enter afterwards>
boot <press Enter afterwards>

it should boot up fine now

Step #2) Once you have installed OPNsense, reboot without the USB installer, repeat STEP #1. Once you're at the main OPNsense menu, open a shell and add add the settings to /boot/loader.conf.local:

hint.hpet.0.clock=0
hint.ahci.0.msi=2
hint.sdhci_pci.0.disabled=1
hint.sdhci_pci.1.disabled=1

This will allow you to boot the filet2 in the future without having to go through step #1 everytime. Good luck.
Edit: Typos

I am having the exact same issue on OPNsense v18.1.1_2. I have been trying to migrate to OPNsense, but I cannot get OPENVPN to route traffic correctly which I need, and this forces me to restore my pfSense setup in the interim.
I have tried setting up OPENVPN like I have numerous times on pfSense using the same steps on a clean install of OPNsense to no avail. I can connect to my VPN provider (via client mode), but traffic does not route through the VPN even with the correct NAT and firewall rules in place.