UPnP does not work with miniupnpd 2.2.0-4

BitComet BitComet Bug Reports
1

My router has miniupnpd 2.2.0-4.

When I start BitComet 1.77 I can see in the router UI that the relevant UPnP redirects are added.

However, when I check the new firewall rules on the router, I see the source is set to 255.255.255.255, when it should be 0.0.0.0/0.

 

I was able to find the cause of the problem.

If you look at the request:

POST /ctl/IPConn HTTP/1.1
Accept: /
CONTENT-TYPE: text/xml;charset=“utf-8”
HOST: 192.168.2.1:5000
SOAPACTION: “urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping”
Content-Length: 628
Cache-Control: no-cache

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<s:Envelope xmlns:s=“http://schemas.xmlsoap.org/soap/envelope/” s:encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/”><s:Body><u:AddPortMapping xmlns:u=“urn:schemas-upnp-org:service:WANIPConnection:1”> 6790TCP6790192.168.2.2061BitComet TCP0</u:AddPortMapping></s:Body></s:Envelope>

you can see that the NewRemoteHost tag contains a single space. I believe that this tag should be empty.

That is what I see in [http://upnp.org/specs/gw/UPnP-gw-WANIPConnection-v2-Service.pdf](http://upnp.org/specs/gw/UPnP-gw-WANIPConnection-v2-Service.pdf)

	Quote



	

		2.3.17 RemoteHost This variable represents the source of inbound IP packets. This variable can contain a host name or a standard IPv4 address representation. This state variable MUST be formatted as:
	

	

		• a domain name of a network host like it is defined in [RFC 1035],
	

	

		• or as a set of four decimal digit groups separated by "." as defined in [RFC 3986],
	

	

		• or an empty string
	



 

Could you please fix this issue?
2

Your article is very interesting, I got a lot of useful information from it, I look forward to your next articles. Thank.

3

You may have to wait some time - that post is over a year old (and BitComet is at version 1.91 - not 1.77)