miniupnpd has a bug -- not mapping non 255.255.255.0 netmask clients

[liyafe1997@…]

for example:
router IP:192.168.2.1 netmask255.255.0.0
client maching IP:192.168.1.x netmask 255.255.0.0

In client run some upnp software,but miniupnpd cannot mapping:
Jan 7 16:45:31 SSS daemon.info miniupnpd[2762]: SSDP M-SEARCH from 192.168.1.2:xxxxx ST: urn:schemas-upnp-org:service:WANPPPConnection:1
Jan 7 16:45:31 SSS daemon.err miniupnpd[2762]: Can't find in which sub network the client is

It is clear,miniupnpd cannot visit client machine.
But client ip set as 192.168.2.x(in 255.255.255.0 same as router network segment),miniupnpd CAN mapping.
So I think miniupnpd is working at 255.255.255.0.

I modify /etc/init.d/miniupnpd
"echo "listening_ip=$ipaddr" >>$tmpconf"
I manually changed to "echo "listening_ip=$ipaddr/16" >>$tmpconf"
and restart miniupnpd.
In /var/etc/miniupnp.conf can see listening_ip has changed to 192.168.2.1/16
miniupnpd is working at netmask 255.255.0.0,192.168.1.x clients CAN normal mapping.

I think this is a bug.Hope the developer attention.
thank you.

[anonymous]

I am getting this same error as you describe, but my system is nothing special: just 192.168.1.1/255.255.255.0 mask.

[anonymous]

Replying to anonymous:

I am getting this same error as you describe, but my system is nothing special: just 192.168.1.1/255.255.255.0 mask

.
Same issue here as well: 192.168.1.1/255.255.255.0 on my normal network and 192.168.0.1/255.255.255.0 on my guest network.
Clients that are trying to use upnp are all on my normal network and are generating a ton of "Jan 10 18:11:44 Blah daemon.err miniupnpd[2209]: Can't find in which sub network the client is" type messages in the system log.

[jow]

Should be fixed with r29722

[jow]

Milestone Attitude Adjustment 12.09 deleted