Re: [Astlinux-devel] Miniupnpd version bump causing problems

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Fixed in:
https://github.com/astlinux-project/astlinux/commit/a5f4e362ee1e5c2f6b337e727ab62d42654526f1


On Dec 19, 2017, at 6:04 PM, Lonnie Abelbeck <li...@lo...> wrote:

> Hi David,
> 
> I figured it out ... long story short, if we define "listening_ip=" with the interface name rather than IP/NM
> -- old
> listening_ip=192.168.101.1/255.255.255.0
> -- new
> listening_ip=eth1
> --
> No more warnings.
> 
> The new interface matching code only works if "listening_ip=" is an interface name, otherwise it defaults to "0"  as in "interface index not matching 0 != 7"
> 
> Ref: https://github.com/miniupnp/miniupnp/blob/master/miniupnpd/miniupnpd.conf#L8
> --
> # LAN network interfaces IPs / networks
> # There can be multiple listening IPs for SSDP traffic, in that case
> # use multiple 'listening_ip=...' lines, one for each network interface.
> # It can be IP address or network interface name (ie. "eth0")
> # It is mandatory to use the network interface name in order to enable IPv6
> # HTTP is available on all interfaces.
> # When MULTIPLE_EXTERNAL_IP is enabled, the external IP
> # address associated with the subnet follows. For example:
> #  listening_ip=192.168.0.1/24 88.22.44.13
> #listening_ip=192.168.0.1/24
> #listening_ip=10.5.0.0/16
> #listening_ip=eth0
> --
> 
> BTW, I also tested VLAN's with listening_ip= and it works.
> 
> While this is a regression in miniupnpd, the configuration fix is simple enough and would be needed if we every wanted to enable IPv6.
> 
> I'll make the appropriate changes to our miniupnpd init.d script.
> 
> Lonnie
> 
> 
> On Dec 19, 2017, at 1:30 PM, David Kerr <Da...@Ke...> wrote:
> 
>> For reference, here is my .conf file...
>> 
>> ## Auto generated file. Do not edit.
>> ext_ifname=eth0
>> listening_ip=
>> 192.168.17.1/255.255.255.0
>> http_port=5000
>> enable_natpmp=yes
>> enable_upnp=yes
>> lease_file=/mnt/kd/upnp.leases
>> bitrate_up=1000000
>> bitrate_down=15000000
>> secure_mode=yes
>> min_lifetime=120
>> max_lifetime=86400
>> system_uptime=yes
>> notify_interval=60
>> clean_ruleset_interval=600
>> uuid=b30041e7-8d39-4bc1-a554-8f6d1b51e50f
>> serial=000001
>> friendly_name=AstLinux
>> Router
>> model_name=AstLinux Router
>> model_description=astlinux-1.3-5e29e2
>> model_number=astlinux-1.3-5e29e2
>> allow 1024-65535 
>> 192.168.17.0/24
>> 0-65535
>> deny 0-65535 
>> 0.0.0.0/0 0-65535
>> 
>> 
>> 
>> On Tue, Dec 19, 2017 at 1:12 PM, Michael Keuter <li...@mk...> wrote:
>> 
>>> Am 19.12.2017 um 18:57 schrieb Lonnie Abelbeck <li...@lo...>:
>>> 
>>> David and Michael,
>>> 
>>> Do you both have UPnP enabled alone or part of NAT-PMP/PCP ?
>>> 
>>> It seems without UPnP the error does not occur. Such as with [ NAT-PMP/PCP only ] .
>>> 
>>> Lonnie
>> 
>> I have enabled "NAT-PMP/PCP & UPnP" on "1st LAN" on my router.
>> 
>>> On Dec 19, 2017, at 10:05 AM, David Kerr <Da...@Ke...> wrote:
>>> 
>>>> Since miniupnpd version was bumped this week my syslog is getting flooded with warning messages...
>>>> 
>>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:07 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:08 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:18 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:28 pbx daemon.warn miniupnpd[3936]: interface index not matching 0 != 7
>>>> Dec 19 10:37:32 pbx daemon.notice miniupnpd[3936]: shutting down MiniUPnPd
>>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: HTTP listening on port 5000
>>>> Dec 19 10:37:33 pbx daemon.notice miniupnpd[27970]: Listening for NAT-PMP/PCP traffic on port 5351
>>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7
>>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7
>>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7
>>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7
>>>> Dec 19 10:37:36 pbx daemon.warn miniupnpd[27970]: interface index not matching 0 != 7
>>>> 
>>>> 
>>>> Totally flooded... I am going to have to revert to previous version.
>>>> Is anyone else seeing this?
>>>> 
>>>> Cause is this update...
>>>> https://github.com/miniupnp/miniupnp/commit/50d21a38d0719682f276173efd705ccbe78aca3d#diff-daa89c3563f327bfe2e660cddc141ce7
>>>> 
>>>> Any ideas?  The only thing I can think of is whether this has to do with my use of a bridge on my internal lan.  So "listening_ip" address is on br0 interface rather than on a regular ethernet interface.
>>>> 
>>>> Any thoughts?
>>>> David