Messages

Hello,

I'm creating a custom package and have run into an issue with the package installation process.

My package directory is:

/usr/plugins/devel/my_package

The directory contains the following:

+POST_INSTALL.post
Makefile
pkg-descr
src/ — containing the required application files, including the MVC structure, etc, and other directories.

From the /usr/plugins/devel/my_package directory, I run:

make package

The package is created successfully, and I then upload it to a private package repository.

I have also added the repository configuration under pkg/repos/myConf, allowing me to install the package using:

pkg install my_package

The problem is that when I install the package from the repository, it gets extracted successfully, but the post-installation script is not run and neither is the package present in the db. [Running pkg info my_package doesn't return the package ]

Additionally, after installation, I find files with names similar to the following throughout the installation directories:

.pkgtemp.actions_xxx.conf.nLalueg1gdd2

Has anyone encountered this issue before?

Could this be related to how the package is being built?

Hello,

I'm creating a custom package and have run into an issue with the package installation process.

My package directory is:

/usr/plugins/devel/my_package

The directory contains the following:

+POST_INSTALL.post
Makefile
pkg-descr
src/ — containing the required application files, including the MVC structure, etc, and other directories.

From the /usr/plugins/devel/my_package directory, I run:

make package

The package is created successfully, and I then upload it to a private package repository.

I have also added the repository configuration under pkg/repos/myConf, allowing me to install the package using:

pkg install my_package

The problem is that when I install the package from the repository, the +POST_INSTALL.post script does not appear to be executed. The package is installed and extracted successfully, but the post-installation script is not run.

Additionally, after installation, I find files with names similar to the following throughout the ../conf/action.d directory:

.pkgtemp.actions_xxx.conf.nLalueg1gdd2

Has anyone encountered this issue before?

Could this be related to how the package is being built, specifically the location or naming of the +POST_INSTALL.post script? Or is there something additional that needs to be configured in the Makefile for the post-install script to be included and executed when the package is installed from a repository?

Any guidance would be appreciated.

Hello everyone,

I have a primary zone in BIND but I can't ping any value of that zone.

I edited the /etc/resolve.conf file to include the domain + cross checked the named.conf file and the zone is included as expected, but the name still does not resolve. I'm new to DNS, any insight is appreciated.

My zone looks like:

Code Select Expand

$TTL 86400
@       IN      SOA    opnsense.localdomain. mail.opnsense.localdomain. ( 2412101547 21600 3600 3542400 3600 )
                NS epcns
@                A 192.168.xx.xx
epcns                A 192.168.xx.xx
pcrf                A 127.0.0.5

ping epcns does not resolve. Is there an extra step I'm missing or

Hello all,
What version of Font Awesome is OPNsense using?
For context,
I want to develop a simple plugin and I'm just curious the version of Font Awesome currently being used.
Thanks

Thank you for your help. I didn't know I could manually add it like that. Everything is working as expected now.

Cheers,
- Prim

Hello all,

I have a custom package, os-myPackage-devel-0.2.pkg which successfully installs on any fresh machine running OPNsense v24.1. But I have an issue with the rc scripts. They don't appear ship into /usr/local/etc/rc.d/  of the new machine, as expected. I presumed that having them referenced in the conf file under actions.d directory was enough. Was I wrong?

Do i need extra steps during packaging to reference the scripts or something similar?

Thanks for your help.

Hello,

I appear to have hit another snag. After successfully running make plugins-<my plugin> I can't seem to find the plugin anywhere on my system. I ran pkg update and that  did not yield any results, as did rebooting the system.

In addition, upon doing some research, I realized I can't state the plugin dependencies in the Makefile. My plugin requires a couple of packages like gcc, mongodb. If I can't put these in the POST_INSTALL.pre/post file, how best can I handle installation of those dependencies?

Hey Maurice, sorry for the late response.

This has been very helpful. I have successfully packaged my plugin. Thank you

Cheers,
- Prim

Hello all,

I'm an OPNsense newbie I apologize for my limited knowledge. I have been following the HelloWorld plugin development documentation and I appear to have hit a roadblock. When I run the make plugins command, the command runs for a notoriously long time -6+ hours( it is still running as I type this, which is my concern )

My query is 1)- Is this normal behavior or is it my architecture in question?
2) - Is there a way of simply building only the plugin I have created, as opposed to re-building all available plugins on the system?

I will greatly appreciate  any help and guidance on how to make an installable plugin for OPNsense.