Miniupnpd SSD log entries

[venusalsa]

Hey guys,

I am using 374.42 on my N66U, which works great for me.

Since the last three days I've been getting entries in my log as following:

Aug 4 13:47:19 miniupnpd[443]: SSDP packet sender 184.105.139.69:56078 not from a LAN, ignoring
Aug 4 14:06:02 miniupnpd[443]: SSDP packet sender 71.6.135.131:40000 not from a LAN, ignoring
Aug 4 14:35:05 dnsmasq-dhcp[491]: DHCPNAK(br0) 100.82.162.223 f0:cb:a1:a4:04:95 wrong address
Aug 5 03:31:52 miniupnpd[443]: SSDP packet sender 89.248.160.175:55336 not from a LAN, ignoring
Aug 5 10:29:09 miniupnpd[443]: SSDP packet sender 184.105.139.69:44804 not from a LAN, ignoring
Aug 6 10:32:17 miniupnpd[443]: SSDP packet sender 71.6.216.39:51401 not from a LAN, ignoring
Aug 6 11:12:01 miniupnpd[443]: SSDP packet sender 184.105.139.113:58002 not from a LAN, ignoring


The changes I have done lately is add a Chromecast to the network and set up a DNS filter for the Chromecast for my Unblock DNS subscription.

This change has been a few days before these error entries started though. The log entries did not show up parallel with the change.
I just wouldn't know what else could cause it, since I haven't changed anything else.

Does anyone recognize this? Thanks

 

[Adamm]

Hey guys,

I am using 374.42 on my N66U, which works great for me.

Since the last three days I've been getting entries in my log as following:

Aug 4 13:47:19 miniupnpd[443]: SSDP packet sender 184.105.139.69:56078 not from a LAN, ignoring
Aug 4 14:06:02 miniupnpd[443]: SSDP packet sender 71.6.135.131:40000 not from a LAN, ignoring
Aug 4 14:35:05 dnsmasq-dhcp[491]: DHCPNAK(br0) 100.82.162.223 f0:cb:a1:a4:04:95 wrong address
Aug 5 03:31:52 miniupnpd[443]: SSDP packet sender 89.248.160.175:55336 not from a LAN, ignoring
Aug 5 10:29:09 miniupnpd[443]: SSDP packet sender 184.105.139.69:44804 not from a LAN, ignoring
Aug 6 10:32:17 miniupnpd[443]: SSDP packet sender 71.6.216.39:51401 not from a LAN, ignoring
Aug 6 11:12:01 miniupnpd[443]: SSDP packet sender 184.105.139.113:58002 not from a LAN, ignoring


The changes I have done lately is add a Chromecast to the network and set up a DNS filter for the Chromecast for my Unblock DNS subscription.

This change has been a few days before these error entries started though. The log entries did not show up parallel with the change.
I just wouldn't know what else could cause it, since I haven't changed anything else.

Does anyone recognize this? Thanks

374.42 on my N66U

If you want support update to the latest version as there have been major updates to Miniupnp amung other things since.

 

[RMerlin]

Hey guys,

I am using 374.42 on my N66U, which works great for me.

Since the last three days I've been getting entries in my log as following:

Aug 4 13:47:19 miniupnpd[443]: SSDP packet sender 184.105.139.69:56078 not from a LAN, ignoring
Aug 4 14:06:02 miniupnpd[443]: SSDP packet sender 71.6.135.131:40000 not from a LAN, ignoring
Aug 4 14:35:05 dnsmasq-dhcp[491]: DHCPNAK(br0) 100.82.162.223 f0:cb:a1:a4:04:95 wrong address
Aug 5 03:31:52 miniupnpd[443]: SSDP packet sender 89.248.160.175:55336 not from a LAN, ignoring
Aug 5 10:29:09 miniupnpd[443]: SSDP packet sender 184.105.139.69:44804 not from a LAN, ignoring
Aug 6 10:32:17 miniupnpd[443]: SSDP packet sender 71.6.216.39:51401 not from a LAN, ignoring
Aug 6 11:12:01 miniupnpd[443]: SSDP packet sender 184.105.139.113:58002 not from a LAN, ignoring


The changes I have done lately is add a Chromecast to the network and set up a DNS filter for the Chromecast for my Unblock DNS subscription.

This change has been a few days before these error entries started though. The log entries did not show up parallel with the change.
I just wouldn't know what else could cause it, since I haven't changed anything else.

Does anyone recognize this? Thanks

These IPs are all public. Are you sure your network isn't wide open to the world for some reason? Miniupnpd shouldn't be receiving any traffic from the WAN side.

 

[venusalsa]

374.42 on my N66U

If you want support update to the latest version as there have been major updates to Miniupnp amung other things since.

Hi Adamm, thanks, I understand that. Thing is, this build has been very stable and well performing for me so far (still is, these are entries but not interfering with performance) and I am kinda anxious to change from something that works for me. It took me a while to get to this point
But you are right, the latest version might aswell take care of these entries (or its source).
I just thought to ask, you never know if this is something that I can do something about regardless of version #.

These IPs are all public. Are you sure your network isn't wide open to the world for some reason? Miniupnpd shouldn't be receiving any traffic from the WAN side.

Hi Merlin, I was noticing the same regarding the public addresses. When I googled the error I never seen it with non-local addresses. The firewall on the router isn't enabled, but I have understood from somewhere else on the forum that the firewall only works for outgoing packets so that might not be the way anyway to prevent this...
Is there an option to control this or is this as Adamm says, something that might be dealt with in an update?
Or is it actually already being dealt with, with the router ignoring the packets?

I just checked at Shields Up which let me know that my N66U didn't respond to UPnP probes.. a good thing!
And with the same SSDP entries. Makes me feel like it's just informing me that I actually am 'safe'? I
I'm not an expert on the subject. Do I see this totally wrong and am I actually really exposed?

 

[RMerlin]

Hi Merlin, I was noticing the same regarding the public addresses. When I googled the error I never seen it with non-local addresses. The firewall on the router isn't enabled, but I have understood from somewhere else on the forum that the firewall only works for outgoing packets so that might not be the way anyway to prevent this...

There's your problem. If you disable the firewall, then your router is completely exposed to the Internet.

You should never disable the firewall unless having a particular usage scenario requiring it to be disabled (for instance if you were just routing things internally at home rather than fronting the Internet).

 

[venusalsa]

There's your problem. If you disable the firewall, then your router is completely exposed to the Internet.

You should never disable the firewall unless having a particular usage scenario requiring it to be disabled (for instance if you were just routing things internally at home rather than fronting the Internet).

I enabled the firewall and tested it by running the Shields Up UPNP Exposure test again. I didn't get a log entry this time!
Ill keep an eye on it, but that seems to have done it. Thanks!

Funny thing is, I didn't disable the firewall myself, it was disabled by default for me. Perhaps that happens after changing from AP mode to Router mode.

Thanks again!