Announce: new OPNsense community repository

[Patrick M. Hausen]

Making Docker run on FreeBSD is an endless game of catch-up and I hope the foundation invests in improving the tooling of FreeBSD native containers (jails) instead. No matter how good your "Linux emulation" is - any day someone will come up with a new edge case and complain that this and that Docker image does not work. It's not a productive use of developer resources. If you need Docker, run Linux.

[fernat]

Using your OPN-arp plugin @mimugmail. Thanks again for the effort.

Running OPNsense 23.1.5_4-amd64 and since the recent upgrade the "opnarp daemon" service on my dashboard shows stopped. Initiating a restart generates a crash report with the progress bar hanging but nothing in the logs. Opnarp service appears to be working, I'm getting alerts via monit and I can start, restart the service w/o issue.

I've tried removing and reinstalling, same issue.

Any suggestions? Thanks

[mimugmail]

Reinstall the plugin should help

[fernat]

I tired removing the plugin, rebooting, and reinstalling. Still seeing the same issue with the opnarp daemon on the dashboard services page failing to start and creating a crash report when I try to start.

Any other suggestions?

[fernat]

Reinstall the plugin should help

Any other suggestions? I upgraded to 23.1.6, tried removing and reinstalling and having the same issue. Thanks

[mimugmail]

Do you filter for interfaces in opnarp config?

[fernat]

No i've left it blank to cover all interfaces.

[fernat]

A few more details. I've updated the opn-arp settings to include specific interfaces (igb0, lagg0). Still seeing the issue. I've tried clearing it out as well. In the Opn-arp setting I'm able to start, stop, restart the service w/o issue. I'm getting monit alert so I'm pretty sure the opn-arp service is running fine. 

The issue maybe specific to the services dashboard widget. I don't see any indication of the opn-arp service not starting or throwing any errors in the logs. In the services dashboard widget the service field is missing, there is description "opnarp daemon". I tried excluding the service from the services widget using the opnarp, opnarp daemon, or opn-arp names, the service isn't excluded from the dashboard.

It appears the dashboard widget isn't populating the service name causing it to not be able to report status nor start,stop, w/o crashing.

[mimugmail]

What happens when you start it via CLI?

[fernat]

Haven't tried that @mimugmail, whats the command? I'll give it a try later this afternoon.

I have restarted from the opn-arp setting tab in the UI, it start's, stops, restarts fine.

[sammyke007]

Haven't tried that @mimugmail, whats the command? I'll give it a try later this afternoon.

I have restarted from the opn-arp setting tab in the UI, it start's, stops, restarts fine.

Is it possible that this still isn't fixed? the deamon keeps on stopping over here.

[mimugmail]

Haven't tried that @mimugmail, whats the command? I'll give it a try later this afternoon.

I have restarted from the opn-arp setting tab in the UI, it start's, stops, restarts fine.

Is it possible that this still isn't fixed? the deamon keeps on stopping over here.

Can you start via CLI?

[fernat]

Whats the CLI command to start opn-arp?

[mimugmail]

I found the error, will push an update

[fernat]

Awesome thanks, looks to have fixed the issue in that the daemon shows green and started.

The service column is still missing a value and if I restart the service from the dashboard widget I'm still seeing a crash.