Please don't parse USN

Bug #1473578 reported by Paul Sokolovsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UPnP Router Control
Won't Fix
Undecided
Unassigned

Bug Description

After starting upnp-router-control, I get on console:

** (upnp-router-control:32297): WARNING **: Invalid USN: uuid:11111111-0000-c0a8-0101-404a039dxxxx::urn:upnp:rootdevice

And GUI reports "not available". Yes, the above USN is broken. Yes, the whole UPNP standard is broken. Yes, vendors produce broken devices (this one is Zyxel P-660W-T1). Yes, the breakage isn't even in upnp-router-control, it's in gupnp. So, solution is simple: don't use broken dependencies like gupnp.

Revision history for this message
Daniele Napolitano (dnax88) wrote :

Hi, thank you for the time spent in test UPnP Router Control.

I noticed that various UPnP implementations are broken, but gupnp give me the ability to keep a small code base and develop easily new features. Of course you are free to fill a bug for gupnp here: http://bugzilla.gnome.org/enter_bug.cgi?product=GUPnP

Meanwhile, can you run URC from the console in debug mode for give me more informations:

upnp-router-control --debug

Changed in upnp-router-control:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.