What's new

miniupnpd[5545]: No allowed eport for NAT-PMP 37370 udp

  • 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!

Asus 1967

Occasional Visitor
Hello,

I have rt-ac88u 384.5 and have noticed I am getting this entry in the log file very frequently

miniupnpd[5545]: No allowed eport for NAT-PMP 37370 udp

I am not sure what this means. I have tried to search this and would appreciate any info

Thank You
 
The last part of the error message appears to be missing. It gives an IP address and port number. Knowing that will tell use the problem.
 
Thank you

Jun 27 22:51:28 miniupnpd[5545]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9
Jun 27 23:06:31 miniupnpd[5545]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9
Jun 27 23:21:34 miniupnpd[5545]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9
Jun 27 23:36:37 miniupnpd[5545]: No allowed eport for NAT-PMP 37370 udp->19
 
What is the device at 192.168.1.137? Something is trying to setup a port forward to that device but the router is not allowing it because the port is <1024. My guess is it is something trying to do wake-on-lan.
 
It's trying to forward port 9, however by default only ports 1024-65535 are allowed.
 
Appreciate the help. Is there a process I can follow to tell me which device and app is making the request.

Thank You
 
Do you have any software installed (either on the PC or any other device) that provides a WoL function?
 
Thanks Colin, I'm not sure, the request repeats every 15 minutes.

Jul 7 21:48:03 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.230:9
Jul 7 21:53:28 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9
Jul 7 22:03:06 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.230:9
Jul 7 22:08:31 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9
Jul 7 22:18:09 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.230:9
Jul 7 22:23:34 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9
Jul 7 22:33:13 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.230:9
Jul 7 22:38:37 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9
Jul 7 22:48:16 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.230:9
Jul 7 22:53:40 miniupnpd[3049]: No allowed eport for NAT-PMP 37370 udp->192.168.1.137:9

the address .137 is a desktop and .230 is my laptop. Could this be coming from my network printer?
 
Could you issue the following command on the desktop and laptop. It will show us whether there is actually something listening on port 9.
Code:
C:\Users\Colin>netstat -ap udp

Active Connections

  Proto  Local Address          Foreign Address        State
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5353           *:*
  UDP    0.0.0.0:5353           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:53202          *:*
  UDP    0.0.0.0:59906          *:*
  UDP    0.0.0.0:59908          *:*
  UDP    0.0.0.0:59910          *:*
  UDP    0.0.0.0:62190          *:*
  UDP    0.0.0.0:63125          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:53674        *:*
  UDP    192.168.1.238:137      *:*
  UDP    192.168.1.238:138      *:*
  UDP    192.168.1.238:1900     *:*
  UDP    192.168.1.238:53673    *:*
 
this is what came back:

Proto Local Address Foreign Address State
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5004 *:*
UDP 0.0.0.0:5004 *:*
UDP 0.0.0.0:5005 *:*
UDP 0.0.0.0:5005 *:*
UDP 0.0.0.0:5050 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:6783 *:*
UDP 0.0.0.0:49954 *:*
UDP 0.0.0.0:49955 *:*
UDP 0.0.0.0:49956 *:*
UDP 0.0.0.0:49957 *:*
UDP 0.0.0.0:49958 *:*
UDP 0.0.0.0:49959 *:*
UDP 0.0.0.0:50538 *:*
UDP 0.0.0.0:52820 *:*
UDP 0.0.0.0:53966 *:*
UDP 0.0.0.0:53967 *:*
UDP 0.0.0.0:53968 *:*
UDP 0.0.0.0:53969 *:*
UDP 0.0.0.0:53970 *:*
UDP 0.0.0.0:53971 *:*
UDP 0.0.0.0:57249 *:*
UDP 0.0.0.0:57255 *:*
UDP 0.0.0.0:57256 *:*
UDP 0.0.0.0:57257 *:*
UDP 0.0.0.0:57258 *:*
UDP 0.0.0.0:57259 *:*
UDP 0.0.0.0:57260 *:*
UDP 0.0.0.0:60857 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49666 *:*
UDP 127.0.0.1:51311 *:*
UDP 127.0.0.1:51312 *:*
UDP 127.0.0.1:53424 *:*
UDP 127.0.0.1:53425 *:*
UDP 127.0.0.1:57251 *:*
UDP 127.0.0.1:57252 *:*
UDP 127.0.0.1:57253 *:*
UDP 127.0.0.1:58537 *:*
UDP 127.0.0.1:58538 *:*
UDP 127.0.0.1:61705 *:*
UDP 127.0.0.1:61706 *:*
UDP 127.0.0.1:63031 *:*
UDP 127.0.0.1:63032 *:*
UDP 127.0.0.1:64200 *:*
UDP 127.0.0.1:64201 *:*
UDP 192.168.1.137:137 *:*
UDP 192.168.1.137:138 *:*
UDP 192.168.1.137:1900 *:*
UDP 192.168.1.137:5353 *:*
UDP 192.168.1.137:49665 *:*
 
@Asus 1967 I've just had a conversation with @Blaine07 about this error message as he was getting exactly the same thing in his syslog. He has confirmed that the device referenced by the IP address was 'a “bridged” connection on my MacBook Pro that was running a Parallels Virtual Machine'.

So it looks like @john9527's post #11 is correct. Can you confirm this?
 

Sign Up For SNBForums Daily Digest

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