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

    UPnP support

    Scheduled Pinned Locked Moved Expired/Withdrawn Bounties
    363 Posts 28 Posters 418.1k 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.
    • D
      databeestje
      last edited by

      package updated. it should install again.

      Cheers,

      Seth

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

        @databeestje:

        package updated. it should install again.

        Cheers,

        Seth

        Thanks for all the hard work on this package. I finally got around to making a custom image with the miniupnpd files and my config so I could just write it to the compact flash card and start the box up.

        Happy to say that the miniupnpd package is outstanding. Azereus maps/unmaps ports correctly. I was even surprised that the Internet Connection Advaced Services tab in WinXP Network Connections is able to map/unmap ports as well. Really satisified.

        Only minor thing I see is in the system logs

        miniupnpd[787]: Unknown soap method

        Also clicking on the miniupnpd on the pfsense admin pages shows the settings, would perfer it to show the status first as that will be used more than the settings for which interface its configured on. Also the tabs are missing on the status page.

        Both those are minor issues.

        –---

        Note: I used the words attached files in writing the below. Well I can't attach files with extensions sh, xml, tar.gz. So instead I provided links to them at the end of the text. I would've renamed the extensions to txt but I thought that might get confusing.


        For anybody else wanting to make a custom image to flash for the embedded platform its quite simple.

        I use FreeSBIE in VMware. However you can use any freebsd platform of your choice.

        Either use the attached miniupnpd.tar.gz file or follow the steps below to create one with the newest version of the files.


        Grab the latest files from http://www.pfsense.com/packages/config/miniupnpd/. This should include miniupnpd, miniupnpd.inc, miniupnpd.xml, status_upnp.php.

        Put the files above and the miniupnpd.sh file attached in a directory you create named miniupnpd. Tar the directory using

        "tar cfz miniupnpd.tar.gz miniupnpd/"


        Now use the attached script sh-add-miniupnpd.sh to add the miniupnpd files to the pfSense.img file (successfully used on snapshot 9-27-06). The script uses the miniupnpd.tar.gz file to extract and add those to the pfSense.img file. You will need to chmod +x sh-add-miniupnpd.sh to give it execute permissions.

        Yes, you could modify the script so you wouldn't have to tar the files and just stick them all in the script directory. However, since I use this in VMware I find its easier to keep track of fewer files when copying them back and forth. Plus I can name the miniupnpd tar file so I know which one is the working version and which is the one containing the new files I just grabbed from the web.  ;)

        "chmod +x sh-add-miniupnpd.sh"
        "./sh-add-miniupnpd.sh miniupnpd.tar.gz pfSense.img"

        Replace the <installedpackages>section in your personalized config you downloaded from your current pfsense box with the supplied <installedpackages>section in the attached cfg-add-miniupnpd.xml file.

        Use the attached script sh-replace-config.sh to replace the default config in the pfSense.img file with the config you just created.

        "chmod +x sh-replace-config.sh"
        "./sh-replace-config.sh yourconfig.xml pfSense.img"

        Your image is ready. Flash it to the device and enjoy.

        Thanks to Seth for helping me out getting this to work. He gave me the <installedpackages>section of the config along answering multiple questions I had about miniupnpd.


        Files:

        http://wgnrs.dynalias.com:81/pfsense/cfg-add-miniupnpd.xml
        http://wgnrs.dynalias.com:81/pfsense/miniupnpd.sh
        http://wgnrs.dynalias.com:81/pfsense/miniupnpd.tar.gz
        http://wgnrs.dynalias.com:81/pfsense/sh-add-miniupnpd.sh
        http://wgnrs.dynalias.com:81/pfsense/sh-replace-config.sh</installedpackages></installedpackages></installedpackages>

        1 Reply Last reply Reply Quote 0
        • S
          sullrich
          last edited by

          I have just commited these changes.

          • Added -o WAN override option

          • Now defaults to status page

          • If not setup prior, redirects to settings tab

          • Removed Status entry.  Now defaults to Services -> Miniupnpd

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

            @sullrich:

            I have just commited these changes.

            • Added -o WAN override option

            • Now defaults to status page

            • If not setup prior, redirects to settings tab

            What flags the page to know if its setup prior or not. I just grabbed the latest files again and reflashed my device. Now on the status page it shows the tabs and on the settings page I have the wan override box. However it still shows the settings page when clicking miniupnpd, even hitting change on the settings page.

            I see this line

            ['installedpackages']['miniupnpd']['config']

            Does that point to the config xml file? I'm almost positive it does. I just did a backup of the config file from the webgui and I have the miniupnpd config section sepcifing the interface_arry.

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              Go to System -> Packages -> Installed -> Click reinstall for miniupnpd.

              I just commited something a few minutes ago.

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

                Okay will do that. Is there a way to kill the firewall log entries for the upnp mapped ports. Azereus fills up the log real quick.

                1 Reply Last reply Reply Quote 0
                • S
                  sullrich
                  last edited by

                  Looks like the logging flag is being enabled in the rule.  It should be trivial to turn off but the binary will need to be recompiled, etc.

                  pass in log quick on fxp0 inet proto udp from any to any port = 30492 keep state label "Azureus UPnP 30492 UDP"

                  Seth, is this something you want to handle?

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

                    @sullrich:

                    Looks like the logging flag is being enabled in the rule.  It should be trivial to turn off but the binary will need to be recompiled, etc.

                    pass in log quick on fxp0 inet proto udp from any to any port = 30492 keep state label "Azureus UPnP 30492 UDP"

                    Seth, is this something you want to handle?

                    While your recompiling the binary the other issue is that no nat reflection rules are being created eventhough i have the disable nat reflection box unchecked. This would be really nice to have fixed. As with Azereus if I want to host trackers I can't check them from my house. It also makes Azereus think its behind a "firewall" due to it not being able to see itself.

                    1 Reply Last reply Reply Quote 0
                    • S
                      sullrich
                      last edited by

                      @rsw686:

                      While your recompiling the binary the other issue is that no nat reflection rules are being created eventhough i have the disable nat reflection box unchecked. This would be really nice to have fixed. As with Azereus if I want to host trackers I can't check them from my house. It also makes Azereus think its behind a "firewall" due to it not being able to see itself.

                      Really sorry but this will not be fixed.  Reflection is a mess as it is and I am not adding that complexity to something like this since we are on the road to being released.

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

                        @sullrich:

                        @rsw686:

                        While your recompiling the binary the other issue is that no nat reflection rules are being created eventhough i have the disable nat reflection box unchecked. This would be really nice to have fixed. As with Azereus if I want to host trackers I can't check them from my house. It also makes Azereus think its behind a "firewall" due to it not being able to see itself.

                        Really sorry but this will not be fixed.  Reflection is a mess as it is and I am not adding that complexity to something like this since we are on the road to being released.

                        I understand the focus is on clearing up whatever bugs are left. Let me ask this though, if nat reflection was to be added to upnp it would be in the miniupnpd binary, correct? Since I have some free time (college student) I would like to attempt to make the modifications my self for my own learning. Is the source available for this binary and where? Thanks for your help.

                        1 Reply Last reply Reply Quote 0
                        • S
                          sullrich
                          last edited by

                          No, that would be in the pfSense code which is frozen.  The only reason your even seeing this package is because its a package and doesnt touch the main code besides a simple table.

                          1 Reply Last reply Reply Quote 0
                          • D
                            databeestje
                            last edited by

                            That's weird. Cause it works for me.

                            1 Reply Last reply Reply Quote 0
                            • S
                              sullrich
                              last edited by

                              There definately is some race conditions present in miniupnpd:

                              82817 root          1 130    0  1892K  416K RUN    544:53 44.78% miniupnpd

                              I should note that nothing is even using it right now!

                              1 Reply Last reply Reply Quote 0
                              • S
                                Superman
                                last edited by

                                I just happened to be quickly browsing the miniupnpd homepage, and noticed that this updated source is now available: miniupnpd20060930.tar.gz.

                                Here's the changelog since 20060919:

                                2006/09/29:
                                  Improved compliance of the XML Descriptions
                                  pretty print for testupnpdescgen
                                
                                2006/09/25:
                                  improved the Error 404 response.
                                  Better serviceType and serviceId for dummy service...
                                
                                2006/09/24:
                                  updating the XML description generator
                                
                                

                                Just in case anyone needed this info.

                                I would like to compile the binary and try it out myself, but not being a developer I don't know exactly how to go about it. I tried the few things I know but I couldn't get it to compile properly.

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

                                  Well miniupnpd is broken in RC3 now. I installed it clean and the package and I get this error in the log.

                                  Oct 2 22:11:51 miniupnpd[977]: Failed to open socket for SSDP. EXITING
                                  Oct 2 22:11:51 miniupnpd[977]: bind(udp): Address already in use
                                  Oct 2 22:11:49 php: : Resyncing configuration for all packages.

                                  Anything changed that would affect this between the 09-27-06 snapshot and RC3. It worked then just fine.

                                  1 Reply Last reply Reply Quote 0
                                  • O
                                    ollopa
                                    last edited by

                                    @rsw686:

                                    Oct 2 22:11:51 miniupnpd[977]: Failed to open socket for SSDP. EXITING
                                    Oct 2 22:11:51 miniupnpd[977]: bind(udp): Address already in use
                                    Oct 2 22:11:49 php: : Resyncing configuration for all packages.

                                    That looks like you still had a copy of miniupnpd running in memory when you installed the package.

                                    Did you try rebooting the router yet?

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      sullrich
                                      last edited by

                                      @rsw686:

                                      Oct 2 22:11:51    miniupnpd[977]: bind(udp): Address already in use

                                      It's already running, I bet.  Kill it before starting it again.

                                      Either that or our code is not killing it correctly.

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

                                        @sullrich:

                                        @rsw686:

                                        Oct 2 22:11:51    miniupnpd[977]: bind(udp): Address already in use

                                        It's already running, I bet.  Kill it before starting it again.

                                        Either that or our code is not killing it correctly.

                                        I tried rebooting the system. Played around with this some more in VMware installing RC3 and then the package. Same thing happens. Only thing that comes to mind is that it runs the rc.d startup script before it syncs the package and then runs it again.

                                        Not only that but now when I run Azereus it still talks to miniupnpd and sets up the port forwarding but it doesn't actually open them up in the firewall. Azereus shows DHT firewalled and before the firewall logs would fill with accepted packets and now it doesn't.

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

                                          When I run

                                          pfctl -aminiupnpd -sn
                                          rdr on fxp1 inet proto udp from any to any port = 6881 label "Azureus UPnP 6881 UDP" -> 10.10.1.150 port 6881
                                          rdr on fxp1 inet proto tcp from any to any port = 6881 label "Azureus UPnP 6881 TCP" -> 10.10.1.150 port 6881

                                          pfctl -aminiupnpd -sr
                                          pass in log quick on fxp1 inet proto udp from any to any port = 6881 keep state label "Azureus UPnP 6881 UDP"
                                          pass in log quick on fxp1 inet proto tcp from any to any port = 6881 keep state label "Azureus UPnP 6881 TCP"

                                          However status.php only shows

                                          pfctl -sn
                                          rdr-anchor "miniupnpd" all

                                          pfctl -sr
                                          anchor "miniupnpd" all
                                          block drop in quick all label "Default block all just to be sure."
                                          block drop out quick all label "Default block all just to be sure."

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            Jonb
                                            last edited by

                                            I did have this problem with RC3 as well but I did an uninstall reboot and install then a reboot and that has seemed to wrok

                                            Hosted desktops and servers with support without complication.
                                            www.blueskysystems.co.uk

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