Uploaded image for project: 'MediaPortal 2'
  1. MediaPortal 2
  2. MP2-419

UPnP stack fails to detect UPnP devices with M-SEARCH

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 2.0.0-Anniversary Edition
    • 2.0.0-alpha.1, 2.0.0-alpha.2, 2.0.0-alpha.3, 2.0.0-alpha.4
    • None
    • MediaPortal 1 + CableCARD tuner
      MediaPortal 2 Device Spy Tool + SAT>IP tuner

    Description

      <p>The MediaPortal 2 UPnP stack sometimes fails to detect UPnP devices with M-SEARCH.</p><p>The problem appears to affect some devices more than others - in particular, devices with many sub-devices and/or services - and/or network environments where many UPnP devices are present.</p><p>The cause of the problem seems to be that the stack is not capable of handling high or even moderate numbers of UDP packets simultaneously. Using Wireshark you can observe that devices are responding to the M-SEARCH query; however the corresponding packets don't always seem to propagate the stack. In other words, packets are getting lost somewhere.</p><p>This issue has been observed with CableCARD tuner support in MP1, and on occasion when testing/debugging with the MP2 Device Spy tool. There is no sure way to reproduce but some PCs/environments seem to be particularly prone to the issue. If you can find such an environment, the issue should be consistent and obvious. Simply run the device spy tool repeatedly and note that it doesn't pick up all devices consistently or in a timely fashion (ie. it falls back to NOTIFY based detection).<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /></p><div class="jeditor-sign" style="display:none;"><br /></div>

      Attachments

        Activity

          People

            mm1352000 mm1352000 (Inactive)
            mm1352000 mm1352000 (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: