What's new

RT-AC66U - Odd system log entries

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

xleanone

New Around Here
Yesterday I installed Merlin's 3.0.0.4_376_49_5 firmware. I run the router in AP mode off my Verizon box to get better wireless performance. Everything seemed to operate just fine. This morning I went ahead and cleared NVRAM, restored factory defaults and reset all my settings (I used the NVRAM Save/Restore script that someone so graciously provided). All still worked fine.

Just now happened to go back in to see if the NTP had reset the system time, and it had. Looked at the the system log and found a string of messages:

Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: sendto(udp_notify=6, 192.168.1.1): Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=443, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=443, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=441, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=459, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=388, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=427, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=388, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=447, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=388, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=451, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto(sock=6, len=379, dest=239.255.255.250:1900): sendto: Invalid argument
Feb 5 15:43:34 miniupnpd[663]: try_sendto failed to send 11 packets
[/SIZE]

These repeat every 60 seconds and have since the router was re-booted. Can anyone tell me what's going on? I am not an expert by a long shot.

Thanks.

xleanone:eek:
 
Resolution without solution

I went back in a few minutes ago and disabled TELNET (which I had enabled for the NVRAM Save/Restore script). The log entries stopped and have not re-appeared so I conclude that something in the TELNET enablement caused the errant messages that resulted in the log entries.

Process of elimination used to work when I was writing IBM 360 ALC, and I guess it still does.

Regards.

xleanone
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top