Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Miniupnpd installation.

    Scheduled Pinned Locked Moved Gaming
    13 Posts 4 Posters 13.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rsw686
      last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • X
        xtlosx
        last edited by

        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!

        1 Reply Last reply Reply Quote 0
        • N
          Nostradamus
          last edited by

          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… argggg

          
          Fatal error: Cannot redeclare upnp_action() (previously declared in /etc/inc/services.inc:1272) in /usr/local/pkg/miniupnpd.inc on line 13
          
          

          1.2-RELEASE
          built on Fri Mar 7 18:49:15 EST 2008
          Intel Celeron 1100 Mhz
          512MB PC-100
          Segate 20GB HD
          eth0: Intel 82801BA/BAM/CA/CAM 10/100 (WAN)
          eth1: 3Com 3c905C-TX/TX-M 10/100 (LAN)

          1 Reply Last reply Reply Quote 0
          • R
            rsw686
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • N
              Nostradamus
              last edited by

              @rsw686:

              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

              1.2-RELEASE
              built on Fri Mar 7 18:49:15 EST 2008
              Intel Celeron 1100 Mhz
              512MB PC-100
              Segate 20GB HD
              eth0: Intel 82801BA/BAM/CA/CAM 10/100 (WAN)
              eth1: 3Com 3c905C-TX/TX-M 10/100 (LAN)

              1 Reply Last reply Reply Quote 0
              • P
                PeeZee
                last edited by

                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" ?

                1 Reply Last reply Reply Quote 0
                • R
                  rsw686
                  last edited by

                  @PeeZee:

                  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>

                  1 Reply Last reply Reply Quote 0
                  • P
                    PeeZee
                    last edited by

                    @rsw686:

                    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 :-)

                    1 Reply Last reply Reply Quote 0
                    • N
                      Nostradamus
                      last edited by

                      @PeeZee:

                      @rsw686:

                      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

                      1.2-RELEASE
                      built on Fri Mar 7 18:49:15 EST 2008
                      Intel Celeron 1100 Mhz
                      512MB PC-100
                      Segate 20GB HD
                      eth0: Intel 82801BA/BAM/CA/CAM 10/100 (WAN)
                      eth1: 3Com 3c905C-TX/TX-M 10/100 (LAN)

                      1 Reply Last reply Reply Quote 0
                      • P
                        PeeZee
                        last edited by

                        @Nostradamus:

                        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 firmware

                        Anyway, 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.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.