I have two OPNsense VM's configured, but for some reason, on none of them does miniupnpd start automatically.
In the config file, the only mention of it is this section:
<installedpackages>
<miniupnpd>
<config>
<enable>1</enable>
<enable_upnp>1</enable_upnp>
<enable_natpmp>1</enable_natpmp>
<ext_iface>wan</ext_iface>
<download/>
<upload/>
<overridewanip/>
<permuser1/>
<permuser2/>
<permuser3/>
<permuser4/>
<iface_array>lan</iface_array>
</config>
</miniupnpd>
</installedpackages>
Am I missing something, or how do I get it to autostart?
Did you.... install the plugin? It's in the notes. ;)
Cheers,
Franco
Indeed I did - it starts fine if I click the play button.
But on every restart, it is back in the stopped state :D
Ok, odd, let me check that real quick.
On second thought I know why.
Something related to it being moved to a module, and therefor not registering correctly as a boot service?
Or the order of things, so modules is loaded after boot services has run?
This: https://github.com/opnsense/plugins/commit/a0742c37
Applies from the console...
# opnsense-patch -c plugins a0742c37
We removed the backwards-compat for the plugin_configure() calls, which left a few stranded on boot. Many thanks for the report!
Cheers,
Franco
That seems to fix it :)
Hooray, and just in time for 17.1. 8)