Is there an actual miniupnpd log spam solution?

inferno480

So I've been looking around for solutions to this miniupnpd log spam issue I've had on at least two systems now and I'm curious if this has ever truly been resolved?

I see indications in redmine that the issue has been around before, but I'm experiencing it now. I tried to recommended fix from this thread, and while I no longer get the errors, I get indications that UPnP is
not going to work for these networks. These are all client interfaces for UPnP to use according to my config.

Aug 31 15:38:01 miniupnpd 59068 HTTP peer 192.168.50.5:40852 is not from a LAN, closing the connection
Aug 31 15:38:01 miniupnpd 59068 HTTP peer 192.168.50.5:40850 is not from a LAN, closing the connection
Aug 31 15:38:01 miniupnpd 59068 HTTP peer 192.168.50.5:40842 is not from a LAN, closing the connection
Aug 31 15:38:01 miniupnpd 59068 HTTP peer 192.168.50.5:40840 is not from a LAN, closing the connection
Aug 31 15:37:44 miniupnpd 59068 SSDP packet sender 192.168.30.18:53291 (if_index=17) not from a LAN, ignoring
Aug 31 15:37:42 miniupnpd 59068 SSDP packet sender 192.168.30.17:39323 (if_index=17) not from a LAN, ignoring
Aug 31 15:37:42 miniupnpd 59068 SSDP packet sender 192.168.30.17:39323 (if_index=17) not from a LAN, ignoring
Aug 31 15:37:42 miniupnpd 59068 SSDP packet sender 192.168.30.17:39323 (if_index=17) not from a LAN, ignoring
Aug 31 15:37:31 miniupnpd 59068 HTTP peer 192.168.50.5:60036 is not from a LAN, closing the connection
Aug 31 15:37:31 miniupnpd 59068 HTTP peer 192.168.50.5:60026 is not from a LAN, closing the connection
Aug 31 15:37:31 miniupnpd 59068 HTTP peer 192.168.50.5:60016 is not from a LAN, closing the connection
Aug 31 15:37:31 miniupnpd 59068 HTTP peer 192.168.50.5:60000 is not from a LAN, closing the connection

If I don't modify the miniupnpd.conf file manually to put the interfaces all on the same line separated by spaces, I get oodles of log spam (sometimes dozens of messages per minute).

johnpoz

@inferno480 said in Is there an actual miniupnpd log spam solution?:

Aug 31 15:38:01 miniupnpd 59068 HTTP peer 192.168.50.5:40852 is not from a LAN, closing the connection

So I don't use UPnP.. But what is your lan network 192.168.50/24 ? Or is this some other network, and UPnP is only on lan? Or you have UPnP running on multiple interfaces?

If lan is seeing traffic from an IP that is not lan, I would expect for there to be barking about it.. You should not see traffic from IPs on lan that are not on the lan network..

What is the 192.168.30.x IPs - your also seeing those on the lan network?

inferno480

@johnpoz said in Is there an actual miniupnpd log spam solution?:

@inferno480 said in Is there an actual miniupnpd log spam solution?:

Aug 31 15:38:01 miniupnpd 59068 HTTP peer 192.168.50.5:40852 is not from a LAN, closing the connection

So I don't use UPnP.. But what is your lan network 192.168.50/24 ? Or is this some other network, and UPnP is only on lan? Or you have UPnP running on multiple interfaces?

If lan is seeing traffic from an IP that is not lan, I would expect for there to be barking about it.. You should not see traffic from IPs on lan that are not on the lan network..

What is the 192.168.30.x IPs - your also seeing those on the lan network?

Thanks for the quick reply -- I have several, separate LAN networks that need UPnP -- they are on different dot1q VLANs (e.g. ix0.30, ix0.50) represented as different OPT interfaces in pfSense as well (renamed to SONOS, and CAM respectively). They're all selected as UPnP client interfaces in the GUI. My actual 'LAN' is ix0.10 w/192.168.10.x/23.