Messages

Did you manage to fix this? In the lastest version of OPNSense I am having the same issue with one plugin (check_procs) it executes fine locally, but when I try and run it over NRPE from my Nagios server, I get unable to read output.
Thanks

Well that took about 2 mins to get working! Thank you very much!

That sounds interesting. I'll take a look. Thanks!

Hi,

This was working until recently, I thought I'd found an issue with a cert, but turns out it wasn't the issue. I am trying to authenticate against Windows AD (functional level 2016). Everything looks ok, certs and config, but when I use the tester, I get the following error:

LDAP bind error [error:0A000086:SSL routines::certificate verify failed (CA signature digest algorithm too weak); Can't contact LDAP server]

I don't really know where to look. For now I have set our VPN to use local users but I'd like to go back to AD if possible. Any ideas?

Thanks!

Weird. I could have sworn I'd removed that! It had worked previously, but you're right there was a space in both lists. That has fixed my issue.

Thank you!

Hi Franco,
I believe he may have stumbled on a bug I am having with 21.7.2.

I have the following in my IPv4 Local Network for my OPNVPN Server 192.168.1.0/24, 192.168.3.0/24,192.168.4.0/24,192.168.8.0/24

When I click save changes I get the following error:
The following input errors were detected:

'192.168.1.0/24, 192.168.3.0/24,192.168.4.0/24,192.168.8.0/24' in 'IPv4 Local Network' may only contain valid ipv4 CIDR range(s) separated by commas.

I also have the same issue on another firewall this time it is the OPNVPN Client:

IPv4 Remote network 192.168.1.0/24,192.168.3.0/24,192.168.8.0/24

And get the error:
The following input errors were detected:

'192.168.1.0/24, 192.168.3.0/24,192.168.8.0/24' in 'IPv4 Remote Network' may only contain valid ipv4 CIDR range(s) separated by commas.

Hi,
Firstly thank you to the OPNSense developers and the ARM port developer for all the work so far.

I have successfully installed 21.1.5 from the image provided on to a Pi 3+.

I was wondering if anyone had tried to add a 4G/LTE connection? I guess there would need to be hardware support in the ARM/BSD build as well as OPNSense? I have been looking at the Waveshare hat (https://www.waveshare.com/wiki/SIM7600G-H_4G_HAT). I don't think this will work "out of the box" but I just wanted to see if anyone had tried? If not has anyone tried a 4G USB dongle? Was thinking the OPNSense Pi would make a great "road warrior" router / firewall.
Thanks!

Michael

Hi,
With the announce mailing list being discontinued, what is the best way to find out about releases? I do use twitter and follow you on there, but I found the emails useful to "flag" so I didn't forget to do the updates :)

Thanks for such a great product!

M

Just done my first fresh install on hyper-v and had no issues - Just as a comment :)

Thanks that fixed it!

Awesome. I'll give that a shot.

Thanks

I had this issue to. I fixed it by changing:

Translation / target in the outbound NAT from interface address to WAN address.

I hadn't experienced this issue before the 18.1 upgrade.

Hi All,

I run a dedicated server. I have a slight issue in that my WAN gateway is not on the same subnet as my public IPs.

I used shellcmd in pfSense and understand that doesn't exist in OPNSense which is fine.

Can I simple add the following to my /etc/rc file? Is it persistent (i.e. upgrades & updates)?

Code Select Expand


route add -net GWIP -iface em0
route add default GWIP


Is there somewhere I should put it instead?

Thanks

Michael

Hi,

I am a relative new comer to OPNSense, I have managed to upgrade 2 without issue, they are relatively simple firewalls though (NAT and VPN)

M

I fixed this with a bit of help from DUO.

Firstly in the LDAP connection make sure you are using the DN rather than the domain\user. Then in your DUO proxy config you need to add the following lines:

[ldap_server_auto]
...
exempt_primary_bind=false
exempt_ou_1=DN of service account

Hope this helps someone!