Amplifi Router HD UPnP issues, error 10054 accessing rootDesc.xml


  • Hi, I'm having issues setting up port forwarding via UPnP. The initial discovery request succeeds:

    M-SEARCH * HTTP/1.1
    Host:239.255.255.250:1900
    ST:urn:schemas-upnp-org:device:InternetGatewayDevice:1
    Man:"ssdp:discover"
    MX:3
    

    Response:

    HTTP/1.1 200 OK
    CACHE-CONTROL: max-age=120
    ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
    USN: uuid:914644b1-e2c9-4d33-8b99-9807067a098e::urn:schemas-upnp-org:device:InternetGatewayDevice:1
    EXT:
    SERVER: AmpliFi/AmpliFi/ UPnP/1.1 MiniUPnPd/2.1
    LOCATION: http://169.254.65.228:5000/rootDesc.xml
    OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
    01-NLS: 1591444865
    BOOTID.UPNP.ORG: 1591444865
    CONFIGID.UPNP.ORG: 1337
    

    ... however, the subsequent HTTP request to http://169.254.65.228:5000/rootDesc.xml fails with 10054.

    Similar behavior is reproducible with upnpc:

    .\upnpc-static.exe -l
    upnpc : miniupnpc library test client, version 2.1.
     (c) 2005-2018 Thomas Bernard.
    Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/
    for more information.
    List of UPNP devices found on the network :
     desc: http://169.254.65.228:5000/rootDesc.xml
     st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
    
    Socket error: recv, 10054
    No valid UPNP Internet Gateway Device found.
    

    I am on Windows 10 (2004), using AmpliFi Router HD, Hardware ID 19, Firmware is 3.3.0 (0-g3035af3f69).


  • Update: rebooting the router has "fixed" the issue, however the fact that it happened in the first place does suggest that a bug may exist in the UPnP implementation somewhere.


  • @Yuriy-O-Donnell Thanks for the information! I will pass this to our dev team!


Log in to reply