Messages

Hello OPNsense Team,

I have successfully built a custom OPNsense ISO from the official source code using the tools repository. The ISO installs correctly, and the system boots without any issues.

However, I've noticed that the Plugins section in the Web UI is missing, and I am unable to install any plugins using the graphical interface.

For comparison, I also downloaded and installed the official OPNsense ISO, and the plugin system works there as expected — even though the folder /usr/local/opnsense/mvc/app/controllers/OPNsense/Firmware is not present.

In my custom-built system, it appears that the required components for plugin management (such as API endpoints, models, or frontend elements) may not be included or properly built.

I followed this build process:

bash
Copy
Edit
make update
make base
make kernel
make core
make plugins
make dvd
Can you please clarify:

Are there any additional steps needed to ensure plugin functionality is fully included in custom ISO builds?

Which files or services are responsible for enabling the plugin system in the new architecture?

Any guidance would be greatly appreciated.

Best regards,
Raushan Patel

I'm not understand what you talking the process i follow, i ask you tell me the steps and how can i add set by default advanced themes because by default set themes opnsense

This is the config.xml.sample file. Now tell me what i can add on this theme section example I choose Advanced themes so what i can edit and add here text, because opnsense by default add only 2 themse opnsense opnsense-dark in path .if any other step to do by default this please tell me know about

<?xml version="1.0"?>
<opnsense>
  <trigger_initial_wizard/>
  <theme>opnsense</theme>
  <sysctl/>
  <system>
    <optimization>normal</optimization>
    <hostname>OPNsense</hostname>
    <domain>internal</domain>
    <dnsallowoverride>1</dnsallowoverride>
    <dnsallowoverride_exclude/>
    <group>
      <name>admins</name>
      <description><![CDATA[System Administrators]]></description>
      <scope>system</scope>
      <gid>1999</gid>
      <member>0</member>
      <priv>page-all</priv>
    </group>

Hi OPNsense Team,

Can you please tell me the correct process to add the AdvancedTomato theme (from misc/theme-advanced) into the OPNsense source code and Set advanced Theme as Default in OPNsense, so it gets included when I build the ISO?

I want to make sure the theme is properly built, installed, and visible in the web interface after installation.

Thank you.

Best regards,
Raushan Patel

Hi OPNsense Team,

Can you please tell me the correct process to add the AdvancedTomato theme (from misc/theme-advanced) into the OPNsense source code and Set advanced Theme as Default in OPNsense, so it gets included when I build the ISO?

I want to make sure the theme is properly built, installed, and visible in the web interface after installation.

Thank you.

Best regards,
Raushan Patel

Thank You Everybody Now Build Succeed

FreeBSD 14.2

Yes i follow this steps https://github.com/opnsense/tools/blob/master/README.md#setting-up-a-build-system
 this is my cmd history.

pkg install git
git clone https://github.com/opnsense/tools
cd tools/
make update
ls
cd /usr/local/opnsense/build/25.1/amd64/sets/
ls
cd /usr/ports/ports-mgmt/pkg
pkg -v
make reinstall
make deinstall
pkg -v
make reinstall
pkg -v
 pkg versio is 1.9..
cd /usr/tools/
make dvd -j20 . and then this error show

Hello OPNSENSE family,


i am just building a opnsense iso. face this issue onn when i make kernel.
.

ERROR: ctfconvert: bwiphy.o doesn't have type data to con

ERROR: ctfconvert: ichss.o doesn't have type data to conv ERROR: ctfconvert: pnphy.o doesn't have type data to conv

ERROR: ctfconvert: efidev.o doesn't have type data to com

ERROR: ctfconvert: dcphy.o doesn't have type data to conv

ERROR: ctfconvert: efirtc.o doesn't have type data to com

ERROR: ctfconvert: bwirf.o doesn't have type data to conv ERROR: ctfconvert

: efirt.o doesn't have type data to conv ERROR: ctfconvert: if_bwi.o doesn't have type data to con

^C*** Error code 2