Topics

Hi all,

I finally made the move to OPNsense from having using a plain Linux system for decades. So while not new in the field, I¨m still learning about the OPNsense (and BSD) way of doing things. Many thanks to all that have contributed to this over the years.

The OPNsense router/firewall has multiple WAN's. All traffic via one of those WANs needs to go via an OpenVPN tunnel, so that OpenVPN's tunnel is taking part in my gateway groups, not the WAN itself. This all works reasonably well, except for the fact that when that WAN goes down, the VPN reroutes via another WAN despite me trying to restrict that to one specific WAN only. This is not a big issue though, just not as tidy was I would like it.

What is of more concern is that when the WAN comes back online, OPNsense doesn´t see that. When the WAN is offline, OPNsense shows RTT=0.0ms, RTTD=0.0ms, loss=100%. This remains so when the WAN comes back onilne (the requested IP address, by DHCP in this case) is shown and the WAN surely is online. A restart of the dpinger process for that particular gateway  resolves the issue (ie. signals that the WAN is back online).

In this particular case, the physical ethernet link stays up (as OPNsense is connected to a switch) when the WAN is down.

It looks to me like a bug in/around dpinger. While I put that forward for your consideration, is there a way to restart the dpinger process, preferably only for a specific gateway, via the commandline / cron? I'm looking for ways to have this work fully automatically and reliably, ie. if this particular WAN disappears, the OpenVPN tunnel should go down (not reroute via another WAN). When this particular WAN reappears, the OpenVPN tunnel should be re-established. If that is difficult to implement with OPNsense, then it's fine if the OpenVPN tunnel reroutes via another WAN as long as it goes back to the WAN it is supposed to go through when that reappears.

It very simple for me to reproduce, so will happily test potential fixes.

Any ideas / suggestions are most welcome.

Regards,
Jan

Hi all,

The upgrade of an OPNsense firewall from 19 -> 20 just failed. I am running OPNsense as VM on a Xen host, which has worked beautifully since 17.x or so. I initiated the upgrade in the evening and noticed the firewall was unresponsive in the morning after which I virtually powercycled the VM.

The boot process crashes with a Fatal Error:
Uncaught Error: Call to undefined function OPNsense\Core\ctype_digit() in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Config.php:82.  Line 82 contains:

return ctype_digit(implode('', array_keys($arrayData)));

See attached screenshot.

Any suggestions how I can pull OPNsense off the ground?

kind regards,
Jan

Hi all,

I've having consistent (ie. on different hardware) trouble running OPNsense as Xen (open source) guest with more than one network interface. With one interface, OPNsense boots fine but as soon as I add another network interface, OPNsense get's stuck during the boot process and remains unresponsive (presumably because the network interface has not been brought up yet). Any suggestions?

Jan

Hi,

First of all thanks for 18.1!

I've started to use OPNsense to manage a whole bunch of Certificate Authorities and Certificate/Key pairs. It would be great if it would be possible to enter a filter that only shows names matching that filter. Sorting / grouping on issuer would also be very useful.

thanks,
Jan

Hi,

OPNsense 17.7.10-i386
FreeBSD 11.0-RELEASE-p17
OpenSSL 1.0.2n 7 Dec 2017

I found this post https://forum.opnsense.org/index.php?topic=5308.msg21559#msg21559

but the patch mentioned in there is no longer available (dead link). Also the post was related to 17.1 Legacy - I guess the patch has since made it into OPNsense?

configd.py: [8b5c1824-7d7e-486c-8960-c47ba994b321] Inline action failed with OPNsense/Netflow OPNsense/Netflow/rc.conf.d 'collections.OrderedDict object' has no attribute 'targets' at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 507, in execute return ph_inline_actions.execute(self, inline_act_parameters) File "/usr/local/opnsense/service/modules/ph_inline_actions.py", line 50, in execute filenames = tmpl.generate(parameters) File "/usr/local/opnsense/service/modules/template.py", line 321, in generate raise render_exception Exception: OPNsense/Netflow OPNsense/Netflow/rc.conf.d 'collections.OrderedDict object' has no attribute 'targets'
Dec 20 09:10:08    

kind regards,
Jan

Hi,

I'm new to OPNsense, have looked at pfSense in the past and until now have been happily rolling my own.
I've installed 17.1 running under Xen (open source) and got a hard crash, see attached screen shot of the console.
Xen in this case is running on a PCengines APU2, happily running production of a number of Linux VMs, but not OPNsense unfortunately. Any suggestions?

Jan