Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - jbakuwel

#1
Hi Franco,

pkg check -da

shows missing dependencies
hostapd is missing a required shared library: libssl.so.9
hostapd is missing a required shared library: libcrypto.so.9
pkg: No packages available to install matching 'openssl102' have been found in the repositories

pkg check -sa

shows heaps of checksum mismatches.

I have a few plugins from the OPNsense repositories. No self-built ports or customisation; everything is out of the standard box. After:

pkg update
pkg upgrade

I got OPNsense back up & running.

Then I ran the update from the webinterface once again and am now running 20.1.5. As far as I can tell the configuration of the system has been retained successfully.

Not sure what went on here though...!

Thanks for your help!

regards,
Jan
#2
19.7 Legacy Series / Re: Upgrade 19 -> 20 fails
April 27, 2020, 11:48:25 PM
Hi Franco,

Thanks for the quick response :-)

After bringing OPNsense online, I did:
# opnsense-bootstrap
# reboot

and I end up with the same Fatal Error. In other words opnsense-bootstrap completed very quickly (didn't appear to download anything from the internet or did it with the speed of light).

What could be the reason for not retaining all files during the upgrade? The system surely has stable power.

Jan

#3
19.7 Legacy Series / Upgrade 19 -> 20 fails
April 27, 2020, 03:44:27 AM
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
#4
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
#5
Hi Franco, Mimu,

Thanks for your reply!

kind regards,
Jan
#6
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
#7
17.7 Legacy Series / Issue with NetFlow
December 19, 2017, 09:19:32 PM
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
#8
17.1 Legacy Series / Re: Fatal trap 12
April 25, 2017, 07:44:59 AM
Hi Franco,

Would you be able to give me a rough estimate when you think this bug might be resolved?
I'm evaluating various systems and would very much like to keep OpnSense on the list...
Please let me know if I can help with this.

kind regards,
Jan
#9
17.1 Legacy Series / Re: Fatal trap 12
April 06, 2017, 02:41:31 AM
Hi Franco,

Many thanks, looking forward to hearing from you. It's quite easy for me to reproduce (just clicking around in the web interface seems to be sufficient); let me know if I can help beta test a new kernel.

Jan


#10
17.1 Legacy Series / Re: Fatal trap 12
April 05, 2017, 06:15:27 AM
Hi Franco,

Hope the "bt" output helps to close in on the problem?
Please let me know if there's anything I can do to help,
At this stage the trap is a show stopper for me...

kind regards,
Jan
#11
17.1 Legacy Series / Re: Fatal trap 12
April 01, 2017, 09:43:49 AM
Hi Franco, ngo,

Sorry for the delay in my answer. Please see the output of "bt" attached. I've left the VM sitting at the debugger prompt, just in case you need more info. Happy to help debug this further with a debug kernel. I have many years of experience with Linux but unfortunately not much with FreeBSD. Am a reasonably quick learner - well at least I like to think I am ;-)

Jan
#12
17.1 Legacy Series / Re: Fatal trap 12
March 27, 2017, 10:18:05 PM
Hi all,

A Google search for "xen freebsd trap 12" has many results... it seems I'm not the only one having that problem. When OPNsense boots I see that it realises it's running on a hypervisor and subsequent is disabling TCP offloading. My gut feeling is that this is a problem in the FreeBSD Xen drivers. I'll keep digging - I like what I've seen so far from OPNsense and would like to make it work.

Jan


#13
17.1 Legacy Series / Re: Fatal trap 12
March 27, 2017, 10:15:22 PM
Hey rgo,

I think it makes no sense to state that the only use case for virtualisation is using machines with 100+ GB of RAM and more than 32 cores. Let's agree to disagree.

Jan

#14
17.1 Legacy Series / Re: Fatal trap 12
March 27, 2017, 11:07:06 AM
Hi rgo,

Thanks for your reply.

I have very good reasons to run VMs instead of directly on the board which go beyond the topic of this post.

Also please note that the APU2 is not exactly "low-end" hardware - at least not for my purposes. It's running 5 (Linux) VMs at very pleasant speeds, some of which would be equally taxing on the hardware as a fully configured OPNsense would be. In fact OPNsense (in a default post install config, ie. without doing anything at all really), currently has a whopping 1GB of RAM, 4 times as much as the current VPN concentrator.

I very much doubt it's a matter of (lack of) resources. This looks like a bug to me.

Jan
#15
17.1 Legacy Series / Fatal trap 12
March 27, 2017, 09:26:58 AM
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