Do any of these log messages matter? indayn / miniupnpd

[BikeHelmet]

I gather that some of these (like the DDNS ones) are just something that you have to live with. For whatever reason they show up constantly even when DDNS updates properly. But what about the UPnP stuff? I think I've got UPnP turned off in Windows, network set Public, and only manually forward ports through my firewall. Not sure why it's showing up over and over, thousands of times. Does anyone know an easy way to squish these? I found a couple threads, but Merlin replied to them saying intermittent issues are hard to track down.

Aug 26 03:53:03 RT-AC3200 watchdog: start ddns.
Aug 26 03:53:03 RT-AC3200 rc_service: watchdog 279:notify_rc start_ddns
Aug 26 03:53:03 RT-AC3200 custom_script: Running /jffs/scripts/service-event (args: start ddns)
Aug 26 03:53:03 RT-AC3200 start_ddns: update FREEDNS.AFRAID.ORG default@freedns.afraid.org, wan_unit 0
Aug 26 03:53:03 RT-AC3200 custom_script: Running /jffs/scripts/service-event-end (args: start ddns)
Aug 26 03:53:05 RT-AC3200 inadyn[10912]: In-a-dyn version 2.5 -- Dynamic DNS update client.
Aug 26 03:53:08 RT-AC3200 inadyn[10912]: Update forced for alias xxxxx.xxxxx.com, new IP# xxx.xx.xx.194
Aug 26 03:53:09 RT-AC3200 inadyn[10912]: HTTP(S) Transaction failed, error 36: Temporary network error (HTTPS send)
Aug 26 03:53:29 RT-AC3200 rc_service: httpd 275:notify_rc restart_ddns
Aug 26 03:53:29 RT-AC3200 custom_script: Running /jffs/scripts/service-event (args: restart ddns)
Aug 26 03:53:29 RT-AC3200 Mastiff: Got AAE_SIG_REMOTE_CONNECTION_TURNED_ON
Aug 26 03:53:30 RT-AC3200 custom_script: Running /jffs/scripts/service-event-end (args: restart ddns)
Aug 26 03:55:26 RT-AC3200 miniupnpd[9123]: upnp_event_process_notify: connect(192.168.0.102:2869): Connection timed out
Aug 26 03:55:26 RT-AC3200 miniupnpd[9123]: upnp_event_process_notify: connect(192.168.0.102:2869): Connection timed out
Aug 26 03:55:26 RT-AC3200 miniupnpd[9123]: upnp_event_process_notify: connect(192.168.0.102:2869): Connection timed out
Aug 26 03:56:26 RT-AC3200 miniupnpd[9123]: upnp_event_process_notify: connect(192.168.0.102:2869): Connection timed out
Aug 26 03:56:26 RT-AC3200 miniupnpd[9123]: upnp_event_process_notify: connect(192.168.0.102:2869): Connection timed out
Aug 26 03:56:26 RT-AC3200 miniupnpd[9123]: upnpevents_processfds: 0x2c4a8, remove subscriber uuid:53a8be1a-xxxx-4598-bb93-00f867e53191 after an ERROR cb: http://192.168.0.102:2869/upnp/eventing/brpeluqegt

The log file is almost entirely this stuff and basically nothing else.

I have an RT-AC3200 running Merlin 384.13_10 with AMTM and various mods/scripts.

 

[Deleted member 51572]

re the UPnP events:

Network Location type might be set to PUBLIC on a Windows client (with IP address 192.168.0.102); a Public network profile disables UPnP / Network Discovery and sets the Windows Firewall to block File Sharing ports, SSDP event notifications on port 2869, etc.

Check that Network Location (for your network) is set to HOME on Windows clients, which will automatically enable network discovery (SSDP) whenever they are connected at Home. Basically, if Windows Firewall is set to allow communication on port 2869 (aka Network Discovery in Windows), then the UPnP connection timeouts should stop. Alternatively, you can disable UPnP on the router.

Network Discovery can also be allowed (or disallowed) manually in the Windows Firewall management console, for both Home and Public networks.

 

[BikeHelmet]

Oh, I see - it's on the router that it needs to be turned off to stop it? Got it. I had assumed it was being initiated from elsewhere. Yes, I have network discovery off intentionally. Thanks for clarifying.