Bug #15732
closed
miniupnpd stops responding after a few minutes
0%
Description
After restarting the UPnP service, I can type the following from my workstation `upnpc -r 1234 TCP` and I get the response:
List of UPNP devices found on the network :
desc: http://10.0.0.1:2189/rootDesc.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1Found valid IGD : http://10.0.0.1:2189/ctl/IPConn
Local LAN ip address : 10.0.0.93
ExternalIPAddress = [redacted]
InternalIP:Port = 10.0.0.93:1234
external [redacted]:1234 TCP is redirected to internal 10.0.0.93:1234 (duration=0)
I can do this as many times as I like, but after ~5 minutes it stops responding:
No IGD UPnP Device found on the network !
The miniupnpd process is still running, and there is nothing in the log files.
When it's responding, running tcpdump on pfsense shows the following:
00:41:29.931828 IP 10.0.0.93.62316 > 239.255.255.250.ssdp: UDP, length 137
00:41:29.985376 IP router.home.arpa.ssdp > 10.0.0.93.62316: UDP, length 433
When it's not responding, the only thing I see is the occasional:
00:48:59.585197 IP router.home.arpa.42061 > 239.255.255.250.ssdp: UDP, length 473
I tired running miniupnpd in debug mode. It displays debug output indicating it is responding to my upnpc commands. But after ~5 minutes there is no longer any reaction to my commands, and no error messages or indications that the process has hung or crashed.
Updated by Jim Pingle 7 months ago
- Status changed from New to Rejected
That looks more like a configuration issue (e.g. firewall rules not passing the traffic), and not a bug in the service. This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum .
See Reporting Issues with pfSense Software for more information.
Updated by Chris F 7 months ago
Jim Pingle wrote in #note-1:
That looks more like a configuration issue (e.g. firewall rules not passing the traffic), and not a bug in the service. This site is not for support or diagnostic discussion.
Sorry, Jim. This is not a configuration issue with the firewall. There is definitely a bug here.
Updated by Steve Wheeler 7 months ago
Not able to replicate that. Do you have more details to reproduce?
pfSense version and upnp config at least.
A forum thread to discuss would be more useful.
Updated by Chris F 7 months ago
Steve Wheeler wrote in #note-3:
Not able to replicate that. Do you have more details to reproduce?
pfSense version and upnp config at least.
A forum thread to discuss would be more useful.
I have all that information available here: https://superuser.com/questions/1856000/why-does-pfsense-upnp-service-only-work-for-a-few-minutes