garycnew
Senior Member
I'm not aware of any direct link between miniupnpd and dcd. I think the most likely solution to dcd problems is to install the latest firmware and/or not create custom network interfaces.
The only idea I can think of regarding miniupnpd is to strace it and see if there's something obvious that it's looping on.
@ColinTaylor
The following are the listening connections and logs for the
service stop_upnp
and service start_upnp
of the miniupnpd daemon.
Code:
# netstat -anp | grep -i upnp
tcp 0 0 0.0.0.0:30467 0.0.0.0:* LISTEN 1533/miniupnpd
Code:
Aug 29 20:26:23 router rc_service: service 1067:notify_rc stop_upnp
Aug 29 20:26:23 router custom_script: Running /jffs/scripts/service-event (args: stop upnp)
Aug 29 20:26:24 router miniupnpd[32710]: shutting down MiniUPnPd
Aug 29 20:26:24 router custom_script: Running /jffs/scripts/service-event-end (args: stop upnp)
Code:
# netstat -anp | grep -i upnp
tcp 0 0 0.0.0.0:63138 0.0.0.0:* LISTEN 32710/miniupnpd
Code:
# ps w | grep -i upnp
32710 admin 888 S miniupnpd -f /etc/upnp/config
Code:
Aug 29 20:21:15 router rc_service: service 32693:notify_rc start_upnp
Aug 29 20:21:15 router custom_script: Running /jffs/scripts/service-event (args: start upnp)
Aug 29 20:21:15 router custom_script: Running /jffs/scripts/service-event-end (args: start upnp)
Aug 29 20:21:15 router miniupnpd[32710]: HTTP listening on port 63138
Aug 29 20:21:15 router miniupnpd[32710]: Listening for NAT-PMP/PCP traffic on port 5351
As for DCD... I would rather not use DCD to avoid upgrading the firmware on all my Asuswrt nodes and router.
Thanks, again.
Gary
Last edited: