On Mon, 2 May 2022 11:40:54 +0800 Yangfl <mmyan...@gmail.com> wrote:
> This does not help a lot. Please, consider filling at least the
> following information:
> * The hardware type and software version of the clients;
> * Network captures of IGD1 and IGD2 miniupnpds;
> * miniupnpd log, if any.
>
>
Hello,
I believe these Github issues have the information necessary to address
this problem:
https://github.com/miniupnp/miniupnp/issues/539
https://github.com/openwrt/packages/pull/14656
Older versions of miniupnpd do not catch the Microsoft browser
user-agent to format the rootDesc.xml and WANIPCn.xml properly. Using
the "force_igd_desc_v1=yes" configuration option on the Debian version
does not work properly as it does not omit the XML that is incompatible
with Microsoft's IGD service.
*What led up to the situation?
Using an open source router software named "VyOS" that depends on this
package for UPnP. NAT/UPnP was type "strict" on all the services tested
(Playstation Network, Xbox Live, Microsoft Gaming Hub). UPnP tester
programs reported also reported no ability to manipulate UPnP through
"WANIPConnection".
* What action was performed that was effective in addressing the problem?
Grabbed the source of the miniupnpd-2.2.1 package from the Debian
repository and re-compiled with default configure options which do NOT
enable IGDv2.
* What was the outcome of this action?
NAT/UPnP type changed to "open" which is the intended outcome, UPnP
testers reporting "WANIPConnection".
