UPnP works, but generates errors in log

[Bunnyh]

I recently changed my router to Asus RT-N56U, and it seems to work perfectly. I didn't have to do any tweaking to get UPnP port mappings to work in µTorrent (3.1.2, Windows 7 x64). But I'm now getting these error messages periodically (even with all logging flags cleared):

[2012-04-26 23:48:17] UPnP: Device error "http://172.17.172.45:41720": (-2)

[2012-04-27 00:08:27] UPnP: Device error "http://172.17.172.45:41720": (-2)

After turning UPnP error logging on, I'm seeing this:

[2012-04-26 23:48:17] UPnP: Device error "http://172.17.172.45:41720": (-2)

[2012-04-26 23:48:17] UPnP: Getting external IP

[2012-04-26 23:48:17] UPnP: Got external IP: 213.139.171.111

[2012-04-26 23:48:51] DEBUG: UPnP: Got an m-search event

[2012-04-26 23:48:51] DEBUG: UPnP: Got an m-search event

[2012-04-26 23:48:54] DEBUG: UPnP: Got an m-search event

[2012-04-26 23:48:54] DEBUG: UPnP: Got an m-search event

[2012-04-26 23:48:57] DEBUG: UPnP: Got an m-search event

[2012-04-26 23:48:57] DEBUG: UPnP: Got an m-search event

[2012-04-27 00:08:17] UPnP(XP): TCP port 41720 -> 172.17.172.45:41720 is already mapped. Not re-mapping.

[2012-04-27 00:08:17] UPnP(XP): UDP port 41720 -> 172.17.172.45:41720 is already mapped. Not re-mapping.

[2012-04-27 00:08:17] DEBUG: UPnP: Got an m-search event

[2012-04-27 00:08:20] DEBUG: UPnP: Got an m-search event

[2012-04-27 00:08:23] DEBUG: UPnP: Got an m-search event

[2012-04-27 00:08:27] UPnP: No cached host. Returning false from CheckCachedUpnpHost()

[2012-04-27 00:08:27] DEBUG: UPnP: Got an m-search event

[2012-04-27 00:08:27] DEBUG: UPnP: Got a reply/notify event

[2012-04-27 00:08:27] UPnP: Found location from upnp notify: http://172.17.172.1:1808/rootDesc.xml

[2012-04-27 00:08:27] UPnP: Discovered host: http://172.17.172.1:1808/rootDesc.xml

[2012-04-27 00:08:27] DEBUG: UPnP: Got a reply/notify event

[2012-04-27 00:08:27] UPnP: Found location from upnp notify: http://172.17.172.45:41720

[2012-04-27 00:08:27] UPnP: Discovered host: http://172.17.172.45:41720

[2012-04-27 00:08:27] UPnP: The device "" is not a UPnP router (http://172.17.172.45:41720/)

[2012-04-27 00:08:27] UPnP: Device error "http://172.17.172.45:41720": (-2)

[2012-04-27 00:08:27] UPnP: Getting external IP

[2012-04-27 00:08:27] UPnP: Got external IP: 213.139.171.111

It seems that in addition to connecting to the router (172.17.172.1), µTorrent is also trying to connect to itself (172.17.172.45)! And then it complains about that not being an UPnP router. I'll state again that the port forwardings are working perfectly, and this is just to report possible non-critical misbehavior of µTorrent. I didn't experience these errors with my previous routers, which were also using miniupnpd. Here is my current router's /etc/miniupnpd.conf for reference:

port=0

enable_upnp=yes

enable_natpmp=no

lease_file=/tmp/upnp.leases

secure_mode=no

presentation_url=http://172.17.172.1/

system_uptime=yes

notify_interval=60

clean_ruleset_interval=600

uuid=8636dd40-8fe9-11e1-b0c4-0800200c9a66

friendly_name=ASUS RT-N56U Wireless Router

model_number=RT-N56U

serial=1.0

bitrate_up=20000000

bitrate_down=20000000

allow 80-65535 172.17.128.0/17 80-65535

deny 0-65535 0.0.0.0/0 0-65535

I'll try to replicate my earlier configurations here, and see if the "problem" goes away.

I am also seeing lots of connections to port 80 on the router from µTorrent clients. Just out of curiosity, what is that traffic? Port 80 serves the web GUI, and I don't understand why µTorrent tries to connect there. The router's web server is likely just giving all these connections the "unauthorized" page of it's web GUI. I'll try to check this with wireshark myself, I'm more interested in the above UPnP errors. EDIT: Confirmed with wireshark, the router is just refusing all these connections with the standard 401 response.

Also, µTorrent tries to connect to the 10.0.0.0/8 IP range for some reason. My LAN is on the 172.16.0.0/12 range. It's even harder to understand this traffic than the above port 80 connections. Obviously the connections are not reaching anywhere. I am not really expecting anyone to answer this one..