Miniupnpd installation.
-
What version of pfSense are you using. If you downloaded if in the past couple of months it already has UPnP (miniupnpd). You can configure it through the services -> upnp menu.
-
I actually get that same message when going to status -> uPNP….
which is why I am so confused.....
-
Right that would happen if you installed the package when upnp was already in the base install. The package and base install use the same menu locations and files. Although the code was moved around some to make it work with the livecd thus the redeclaration errors. You could try uninstalling the package then updating your pfsense install to restore the files. You might just have to backup your config and reinstall pfsense.
-
ya, I don't care about upnp that much, I just used the static ports option for NAT, and xbox live sees it as open!
-
Hi.
Hmm.. can somebody please remover miniupnpd package from Package Manager?
I tried to install that, and now i have to install hole pfSense again… arggggFatal error: Cannot redeclare upnp_action() (previously declared in /etc/inc/services.inc:1272) in /usr/local/pkg/miniupnpd.inc on line 13 -
My thought was it was going to be removed when 1.2 was officially released since 1.0.1 doesn't include UPnP. I'm just not sure why you would install it since it is already in the base install.
-
My thought was it was going to be removed when 1.2 was officially released since 1.0.1 doesn't include UPnP. I'm just not sure why you would install it since it is already in the base install.
Hi.
hehe, you know… noobs always try everything :D :D But i'm back in business now... Fast install, hehe
I learn one more thing today, hehe -
Hmm, I seem to have the same problem, only worse.
I was running a 1.0.1 install (very stable for quite a while) and today decided to upgrade to 1.2-RC2.
Unfortunately I had miniupnp installed on the 1.0.1 install.The upgrade went very smooth, but since uPnP is included in the 1.2 release I now had 2 (!) entries in the web gui about upnp (one said upnp from the base install and the other miniupnp from the package)
Ok, tried removing the package, went smooth, no errors, only the problem now got worse since I still have the 2 web gui entries but now they both point to an error 404…
Shouldn't there be a big warning somewhere "Remove miniupnp package before upgrading to 1.2" ?
-
Hmm, I seem to have the same problem, only worse.
I was running a 1.0.1 install (very stable for quite a while) and today decided to upgrade to 1.2-RC2.
Unfortunately I had miniupnp installed on the 1.0.1 install.The upgrade went very smooth, but since uPnP is included in the 1.2 release I now had 2 (!) entries in the web gui about upnp (one said upnp from the base install and the other miniupnp from the package)
Ok, tried removing the package, went smooth, no errors, only the problem now got worse since I still have the 2 web gui entries but now they both point to an error 404…
Shouldn't there be a big warning somewhere "Remove miniupnp package before upgrading to 1.2" ?
Backup your config and remove the miniupnpd menu section from the <installedpackages>section. Restore your config. Then reinstall the upgrade to restore the miniupnpd files.</installedpackages>
-
Backup your config and remove the miniupnpd menu section from the <installedpackages>section. Restore your config. Then reinstall the upgrade to restore the miniupnpd files.</installedpackages>
Thanks, that worked
But I still think there should be a warning somewhere :-)
-
Backup your config and remove the miniupnpd menu section from the <installedpackages>section. Restore your config. Then reinstall the upgrade to restore the miniupnpd files.</installedpackages>
Thanks, that worked
But I still think there should be a warning somewhere :-)
Hi.
Here : http://forum.pfsense.org/index.php/topic,6047.0.html
-
Hi.
Here : http://forum.pfsense.org/index.php/topic,6047.0.html
I understand the fact that I shouldn't try to install the miniupnp package in a 1.2 branch release.
But I didn't see any warning whatsoever that I should not perform a firmware upgrade when I have the miniupnp package installed because it will mess things up.
You have to first manually remove the miniupnp package before upgrading the firmwareAnyway, it's solved for me now, but I can imagine that in the future there will be a lot of users that upgrade to 1.2-RC2 or later and will hit the same problem.