Modify

Opened 5 years ago

Closed 2 years ago

#12997 closed defect (moved_to_github)

Miniupnpd is flooding the log since update to 1.8 using ipv6

Reported by: duvi Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: miniupnpd flood Cc:

Description

Every 3 seconds:

Feb 15 01:03:05 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::817:b5b1:9a18:dc7b]:51492 not from a LAN, ignoring
Feb 15 01:03:05 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::b53f:f532:26e1:c9b2]:51491 not from a LAN, ignoring
Feb 15 01:03:08 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::817:b5b1:9a18:dc7b]:51492 not from a LAN, ignoring
Feb 15 01:03:08 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::b53f:f532:26e1:c9b2]:51491 not from a LAN, ignoring
Feb 15 01:03:12 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::817:b5b1:9a18:dc7b]:51492 not from a LAN, ignoring
Feb 15 01:03:12 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::b53f:f532:26e1:c9b2]:51491 not from a LAN, ignoring
Feb 15 01:03:15 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::817:b5b1:9a18:dc7b]:51492 not from a LAN, ignoring
Feb 15 01:03:15 OpenWrt daemon.warn miniupnpd[2819]: SSDP packet sender [fe80::b53f:f532:26e1:c9b2]:51491 not from a LAN, ignoring

/etc/config/upnp is default.

root@OpenWrt:/# cat /var/etc/miniupnpd.conf
ext_ifname=pppoe-wan
listening_ip=192.168.1.1/24
port=5000
enable_natpmp=yes
enable_upnp=yes
secure_mode=yes
system_uptime=yes
lease_file=/var/upnp.leases
bitrate_down=8388608
bitrate_up=4194304
uuid=db7dc7a5-9a2c-446b-8b0d-5d8552f04a00
allow 1024-65535 0.0.0.0/0 1024-65535
deny 0-65535 0.0.0.0/0 0-65535

The problem might be that miniupnpd is listening on ipv6 also, and Windows 7 computers send SSDP packets there, but miniupnpd doesn't recognize the link local address as "LAN".

root@OpenWrt:/# netstat -nlp | grep miniupnpd
tcp        0      0 :::5000                 :::*                    LISTEN      2819/miniupnpd
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           2819/miniupnpd
udp        0      0 192.168.1.1:48098       0.0.0.0:*                           2819/miniupnpd
udp        0      0 192.168.1.1:5351        0.0.0.0:*                           2819/miniupnpd
udp        0      0 :::1900                 :::*                                2819/miniupnpd
udp        0      0 :::47075                :::*                                2819/miniupnpd
root@OpenWrt:/# cat /etc/config/network
...
config interface lan
        option ifname   'eth1'
        option type     'bridge'
        option proto    'static'
        option ipaddr   '192.168.1.1'
        option netmask  '255.255.255.0'
        option ip6addr  '2a01:dead:beef::1/64'
root@OpenWrt:/# ifconfig br-lan
br-lan    Link encap:Ethernet  HWaddr 00:0C:42:43:9F:26
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2a01:dead:beef::1/64 Scope:Global
          inet6 addr: fe80::20c:42ff:fe43:9f26/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:765982 errors:0 dropped:0 overruns:0 frame:0
          TX packets:890719 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:266910568 (254.5 MiB)  TX bytes:762415340 (727.0 MiB)

I guess this is not an error of miniupnpd, but shouldn't there be a config parameter to also ipv6 networks to known 'LAN'?
This makes using the log impossible.

Attachments (1)

101-ssdp-fix.patch (766 bytes) - added by duvi 5 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 5 years ago by anonymous

I reported the issue upstream: https://github.com/miniupnp/miniupnp/issues/32

error seems to be in 'upnputils.c' with funktion: get_lan_for_peer
one could use IN6_IS_ADDR_LINKLOCAL there

from upstream report:
Windows7 sends SSDP Messages from fe80:: Protocol was PNRP (Peer Name Resolution Protocol)

Apr 19 17:45:42 OpenWrt daemon.warn miniupnpd[1704]: SSDP packet sender [fe80::]:65424 not from a LAN, ignoring

with debug:
miniupnpd[7058]: Received UDP Packet (IPv6)
miniupnpd[7058]: get_src_for_route_to ([fe80::]:65424)
miniupnpd[7058]: get_lan_for_peer() looking for LAN interface index=2
miniupnpd[7058]: ifname= index=0 str=192.168.3.1 addr=c0a80301 mask=ffffff00
miniupnpd[7058]: get_lan_for_peer(): not found !
miniupnpd[7058]: SSDP packet sender [fe80::]:65424 not from a LAN, ignoring

comment:2 Changed 5 years ago by duvi

Here's the solution.

  1. Put 101-ssdp-fix.patch to package/feeds/packages/miniupnpd/patches
  2. Edit package/feeds/packages/miniupnpd/files/miniupnpd.init in line 110, and replace network_get_subnet with network_get_device
  3. Rebuild and reinstall miniupnpd

Changed 5 years ago by duvi

comment:3 Changed 5 years ago by jow

  • Resolution set to fixed
  • Status changed from new to closed

Fixed with r36488

comment:4 Changed 4 years ago by philip.petev@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

After upgrade to r39132 trunk I see a lots of these in the log:

Fri Dec 27 07:13:41 2013 daemon.warn miniupnpd[1907]: SSDP packet sender [fe80::5c99:ef2a:b77:6ac6]:58313 not from a LAN, ignoring

I thought this was fixed !!!

comment:5 Changed 4 years ago by tyrel@…

I just installed miniupnpd (and OpenWrt as a whole) for the first time and I'm seeing this message. What's the best way for me to proceed to get these to go away?

Looks like I'm running miniupnpd version 1.8-1

comment:6 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:7 Changed 2 years ago by nbd

  • Resolution set to moved_to_github
  • Status changed from reopened to closed

miniupnpd is maintained here: ​https://github.com/openwrt-routing/packages

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.