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

    UPnP support

    Scheduled Pinned Locked Moved Expired/Withdrawn Bounties
    363 Posts 28 Posters 402.2k 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

      @rsw686:

      @shokwave:

      There appears to be an update to miniupnpd which addresses the discover process searches for "InternetGatewayDevice" on XP, finally!

      Nice I noticed it just came out today. I don't know how to build the binary. Maybe one of the devs could give try this again. I know the last try to update broke miniupnpd. Maybe this will work better this time. Or if somebody could point me in the right direction on how to compile it with the changes for pfSense.

      I built the new version however I am still getting all the same subscrube command errors that repeat thousands of times

      Oct 21 13:28:41 last message repeated 4849 times
      Oct 21 13:28:35 miniupnpd[43672]: Unsupported HTTP Command SUBSCRIBE
      Oct 21 13:28:35 miniupnpd[43672]: recv (state0): Connection reset by peer

      Something is broken in the new version or the old version just didn't output all the errors. I will look into it.

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

        The update that was released on the 20th is for the client. Eventhough the client files are used when building the daemon, the files used do not differ from the previous version. The only difference is the daemon. I'm going to try and get the new daemon version to work.

        As a test I rebuilt the version used in the package by hand and mine is identical to the pacakage version.

        –-

        You know the new version doesn't have more issues, the error reporting was changing from the standard output to syslog. Also theres a list of supported commands now and it errors on unsupported. I am going to finish going through it, build an vew version with the errors sent back to the standard output vs syslog and try it out.

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

          Alright so heres the deal. The new version with its supported value lists disabled the internet connection (internet gateway) icon for upnp in my network connection on winxp. So we're loosing functionality as before you could add port maps through it.

          However it does have other improvements. So I merged the improvements into the older version and rebuilt it. They are minor and probably won't help anybody out. I also disabled the error logging for the unknown soap method. I will post the link later.

          1 Reply Last reply Reply Quote 0
          • B
            billm
            last edited by

            @rsw686:

            I finally figured out the bug!!! Its been there from the originial version and I just overlooked it.

            In status_upnp.php

            if(!is_array($config['installedpackages']['miniupnpd']['config'][0]['interface_array']))
            Header("Location: /pkg_edit.php?xml=miniupnpd.xml&id=0");

            the amp; shouldn't be there. Thus the pkg_edit.php file doesn't see the id number thinking it should add a new config section. This only happens when unselecting all the interfaces as you only get directed to the settings page from the status page if theres no interfaces selected.

            Hopefully we can commit this now?? Sorry for trying to make the bug in the pfsense code. I've just spent hours on this and I really couldn't see the cause. I will post all the files and diff -rub files up in a few.

            Commited, thanks.

            –Bill

            pfSense core developer
            blog - http://www.ucsecurity.com/
            twitter - billmarquette

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

              I'm working on a change for miniupnpd that will help winxp users trying to add port mappings. Its all done I just need to finish testing. In Network Connections -> Internet Connection -> Properties you can click settings and add port mappings. The issue is windows likes to convert the ip address to a hostname. Well miniupnpd needs an ip address and on the status page will show 0.0.0.0 for the mapping. I have corrected this in the code and will post the new binary and the diff -rub patches needed to compile probably tomorrow. Heres screenshot of what I'm talking about.

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

                I've temporarily removed the info on this post as I've beeing talking with the creator of miniupnpd and have resolved the issues with the new 20061018 release. I will post the new binary and diff -rub files when I get everything all created.

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

                  Here we go… I'm still using the old version on the client for simplicity on keeping track of the versions. The daemon uses 2 files form the client and they are identicial in the new version of the client.

                  miniupnpd20061018.tar.gz miniupnpc20060909.tar.gz

                  patch upnpdescgen.c upnpdescgen.c.patch
                      -rebrand for pfSense
                    patch upnpsoap.c upnpsoap.c.patch
                      -change syslog from notice to info for "Unknown soap method"
                      -if hostname given convert to ip address
                      -revert sendEvent yes:no to always no (20060924)

                  md5sum miniupnpd: B856DFF73836037D1F08CBA2C0F4F3EE

                  Binary http://wgnrs.dynalias.com:81/pfsense/miniupnpd/miniupnpd

                  For those who with to reflash.
                  http://wgnrs.dynalias.com:81/pfsense/pfSense-Embedded-1.0-RELEASE-Miniupnpd.img.gz

                  Otherwise on embedded you can use the command prompt under diagnostics in the webgui to upload the binary and the replace binary script.

                  script http://wgnrs.dynalias.com:81/pfsense/miniupnpd/sh-replace-binary.sh

                  Then on the serial console or by ssh select shell and do the following.

                  
cd /tmp
chmod +x sh-replace-binary.sh
./sh-replace-binary.sh miniupnpd

                  It will print out the md5sum which should match above. Enjoy!

                  20061018.upnpsoap.c.patch.txt
                  20061018.upnpdescgen.c.patch.txt

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

                    @rsw686:

                    Here we go… I'm still using the old version on the client for simplicity on keeping track of the versions. The daemon uses 2 files form the client and they are identicial in the new version of the client.

                    miniupnpd20061018.tar.gz miniupnpc20060909.tar.gz

                    patch upnpdescgen.c upnpdescgen.c.patch
                        -rebrand for pfSense
                      patch upnpsoap.c upnpsoap.c.patch
                        -change syslog from notice to info for "Unknown soap method"
                        -if hostname given convert to ip address
                        -revert sendEvent yes:no to always no (20060924)

                    md5sum miniupnpd: B856DFF73836037D1F08CBA2C0F4F3EE

                    Binary http://wgnrs.dynalias.com:81/pfsense/miniupnpd/miniupnpd

                    For those who with to reflash.
                    http://wgnrs.dynalias.com:81/pfsense/pfSense-Embedded-1.0-RELEASE-Miniupnpd.img.gz

                    Otherwise on embedded you can use the command prompt under diagnostics in the webgui to upload the binary and the replace binary script.

                    script http://wgnrs.dynalias.com:81/pfsense/miniupnpd/sh-replace-binary.sh

                    Then on the serial console or by ssh select shell and do the following.

                    
cd /tmp
chmod +x sh-replace-binary.sh
./sh-replace-binary.sh miniupnpd

                    It will print out the md5sum which should match above. Enjoy!

                    Great work!

                    Feel free to commit away now that your CVS account is ready to rock.

                    1 Reply Last reply Reply Quote 0
                    • L
                      lawe
                      last edited by

                      Hello, I've flashed my cf card with your image. After the restore from my config the Menue miniupnp isnt here. :)

                      sorry for my bad englisch

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

                        @lawe:

                        Hello, I've flashed my cf card with your image. After the restore from my config the Menue miniupnp isnt here. :)

                        sorry for my bad englisch

                        You need to add the required section to the installed packages section in your config file.

                        http://wgnrs.dynalias.com:81/pfsense/cfg-add-miniupnpd.xml

                        for an example

                        http://wgnrs.dynalias.com:81/pfsense/cfg-default-miniupnpd.xml

                        1 Reply Last reply Reply Quote 0
                        • L
                          lawe
                          last edited by

                          THX for the fast help. It works :-)

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

                            I updated the binary to 20061023. This has been comitted so full installs you can just reinstall the package per the webgui.

                            Embedded the above instructions are still valid. However there are no difference between the 20061018 and 20061023 binaries in function. The author included the changes I made so I rebuilt the binary based on that source to keep the versions in order.

                            md5sum: 33B3568E957E900CA4540C4B744D2573

                            1 Reply Last reply Reply Quote 0
                            • A
                              auwts
                              last edited by

                              Hi, I found this thread using google in my quest to get my new xbox 360 working behind my freebsd pf firewall/nat.
                              I'm running the miniupnpd from miniupnpd20061023.tar.gz as found on http://miniupnp.free.fr/files/
                              uTorrent recognizes the upnp, and pf opens the required port. However the xbox still sees my NAT config as 'strict'.

                              I have added a little debug prints to miniupnpd, and it only receives the following packets:

                              Oct 26 01:44:22 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST:239.255.255.250:1900^M NT:urn:schemas-microsoft-com:nhed:presence:1^M NTS:ssdp:alive^M LOCATION:*^M AL:<urn:schemas-microsoft-com:nhed:attributes?type=x02&firmwarever=2858.0&udn=uuid:10000000-0000-0000-0200-00125abaa1ac>^M CACHE-CONTROL:max-age=4^M USN:uuid:00000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:22 fasdu miniupnpd[60923]: Unknown udp packet received from 0.0.0.0:1025
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: upnp:rootdevice^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::upnp:rootdevice^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M N:uuid:00000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: upnp:rootdevice^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::upnp:rootdevice^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M N:uuid:00000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: uuid:52840456-1705-2000-0000-00125abaa1ac^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M 000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: uuid:52840456-1705-2000-0000-00125abaa1ac^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M 000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:device:MediaRenderer:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:device:MediaRenderer:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:device:MediaRenderer:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:device:MediaRenderer:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:ConnectionManager:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:ConnectionManager:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:ConnectionManager:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:ConnectionManager:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:RenderingControl:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:RenderingControl:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:RenderingControl:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:RenderingControl:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605</urn:schemas-microsoft-com:nhed:attributes?type=x02&firmwarever=2858.0&udn=uuid:10000000-0000-0000-0200-00125abaa1ac>

                              Am i'm doing something wrong? Since some people posted in this thread that it worked for them, i'm guessing i am :-)

                              Any help is appreciated.

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

                                @auwts:

                                Hi, I found this thread using google in my quest to get my new xbox 360 working behind my freebsd pf firewall/nat.
                                I'm running the miniupnpd from miniupnpd20061023.tar.gz as found on http://miniupnp.free.fr/files/
                                uTorrent recognizes the upnp, and pf opens the required port. However the xbox still sees my NAT config as 'strict'.

                                I have added a little debug prints to miniupnpd, and it only receives the following packets:

                                Oct 26 01:44:22 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST:239.255.255.250:1900^M NT:urn:schemas-microsoft-com:nhed:presence:1^M NTS:ssdp:alive^M LOCATION:*^M AL:<urn:schemas-microsoft-com:nhed:attributes?type=x02&firmwarever=2858.0&udn=uuid:10000000-0000-0000-0200-00125abaa1ac>^M CACHE-CONTROL:max-age=4^M USN:uuid:00000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:22 fasdu miniupnpd[60923]: Unknown udp packet received from 0.0.0.0:1025
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: upnp:rootdevice^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::upnp:rootdevice^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M N:uuid:00000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: upnp:rootdevice^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::upnp:rootdevice^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M N:uuid:00000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: uuid:52840456-1705-2000-0000-00125abaa1ac^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M 000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: uuid:52840456-1705-2000-0000-00125abaa1ac^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M 000000-0000-0000-0200-00125ABAA1AC::urn:schemas-microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:device:MediaRenderer:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:device:MediaRenderer:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:device:MediaRenderer:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:device:MediaRenderer:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -microsoft-com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:ConnectionManager:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:ConnectionManager:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:ConnectionManager:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:ConnectionManager:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:RenderingControl:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:RenderingControl:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605
Oct 26 01:44:24 fasdu miniupnpd[60923]: UDP Packet received: NOTIFY * HTTP/1.1^M HOST: 239.255.255.250:1900^M NT: urn:schemas-upnp-org:service:RenderingControl:1^M NTS: ssdp:alive^M LOCATION: http://192.168.1.110:1026/^M USN: uuid:52840456-1705-2000-0000-00125abaa1ac::urn:schemas-upnp-org:service:RenderingControl:1^M CACHE-CONTROL: max-age=1800^M SERVER: Xbox/2.0.2858.0 UPnP/1.0 Xbox/2.0.2858.0^M ^M ^M -com:nhed:presence:1^M SERVER:dashboard/1.0 UpnP/1.0 xbox/2.0^M ^M
Oct 26 01:44:24 fasdu miniupnpd[60923]: Unknown udp packet received from 192.168.1.110:21605</urn:schemas-microsoft-com:nhed:attributes?type=x02&firmwarever=2858.0&udn=uuid:10000000-0000-0000-0200-00125abaa1ac>

                                Am i'm doing something wrong? Since some people posted in this thread that it worked for them, i'm guessing i am :-)

                                Any help is appreciated.

                                Do a search on here for xbox 360. I looked through the posts and I don't think anybody has got it working with the 360 yet. I don't own an xbox or a xbox 360 so I really can't help you out. Also the log you posted is hard to read. Might try contacting the author of mininupnpd. I worked out with winxp SUBSCRIBE issue with him.

                                1 Reply Last reply Reply Quote 0
                                • A
                                  auwts
                                  last edited by

                                  Thanks for your reply, I just ( ::)) figured out what my problem was. I had my xbox configured with a manual IP address, and then it doesn't seem to send a M-SEARCH broadcast. When using automatic it does. So now the xbox live test utility sees my NAT as open. Thanks for all the work! (BTW: Any plans to submit it as a FreeBSD port?)

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

                                    Updated to miniupnpd version 20061017. Full installs you just need to reinstall the package. Embeddeds I will get to you soon.

                                    From the miniupnpd20061027.tar.gz changelog

                                    2006/10/27:
                                      Thanks to a patch sent by Michael van Tellingen, miniupnpd is
                                      now ignoring NOTIFY packets sent by other devices and is
                                      writing is own pid to /var/run/miniupnpd.pi

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

                                      This package is really coming together!  Nice work!

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

                                        Embedded users here are the update instructions. Upload the following file using the command prompt page under diagnostics on the webgui.

                                        http://wgnrs.dynalias.com:81/pfsense/miniupnpd/sh-update-miniupnpd.sh

                                        Afterwards either use the console terminal or ssh into the box. Select option 8 shell. Enter the following commands

                                        
cd /tmp
chmod +x sh-update-miniupnpd.sh
./sh-update-miniupnpd.sh

                                        The results should like similar to below.

                                        
rules cleared
nat cleared
/usr/local/sbin/miniupnpd                     100% of   45 kB  344 kBps
/usr/local/pkg/miniupnpd.inc                  100% of 3285  B  413 kBps
/usr/local/pkg/miniupnpd.xml                  100% of 2081  B  647 kBps
/usr/local/www/status_upnp.php                100% of 4185  B 1018 kBps
Syncing packages: miniupnpd.

                                        Otherwise if you want to reflash the image is

                                        http://wgnrs.dynalias.com:81/pfsense/pfSense-Embedded-1.0-RELEASE-Miniupnpd.img.gz

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

                                          I just commited version 20061028. I found a memory leak in all the previous versions so its highly recommend that you upgrade.

                                          WinXP now shows connected for the Internet Connection Gateway and you can double-click on it and view the status. Although only the uptime is correct, the bytes sent and received are fixed currently.

                                          Full installs just reinstall the package, embedded the above post has the instructions for you. I updated the sh-update-miniupnpd.sh script to show the md5sum after the update. That way you're sure you have the correct version.

                                          md5sum miniupnpd: B47F17A416847945F1BBCFA9C2A45052

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

                                            This thread has gotten relatively quiet. I'm almost done adding the ability to enable/disable logging of packets passed by miniupnpd rules. That way if your running bittorent or another app which fills the firewall log you can stop that and see packets being passed by other rules. I just need to see if Thomas will include it in the official miniupnpd source and release a new version or not?

                                            Any other suggestions or complaints?

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