Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[xoltex]

When I try to connect the latest aMule client I get
"Universal Plug and Play: error(UPNP_DISCOVERY_ADVERTISEMENT_ALIVE): Error retrieving device description from http://192.168.1.1:80/igd.xml: Unknown Error"

If I try to go to http://192.168.1.1:80/igd.xml I do get an XML file (I can post it completely here if needed), which start:

<root xmlns="urn:schemas-upnp-org:device-1-0">
 
<specVersion>
   <major>1</major>
   <minor>0</minor>
</specVersion>
 
<device>
   <deviceType>urn:schemas-upnp-org:device:InternetGatewayDevice:1</deviceType>
..........................
So it seems that aMule libraries are failing to parse it (or to find the right information). Anyway, the net result is that aMule can not set the my home firewaill/router so I get low ID.

I do not have any rules set on my home firewall but and I do not use OS X's firewall rules either. Interestingly, when I use eMule (i.e. not aMule) from another box all works fine - eMules sets the rules on the firewall correctly and I get high ID...

Any ideas ?

[Stu Redman]

Forward the ports in your router manually.

[Kry]

Oooooooooor we could take a look into libupnp, which would be Phoenix.

[xoltex]

Thanks for quick response guys...

Stu, your sugestion seems the quickest one but  I think it would be better to fix the problem as Kry suggested. Bellow you will find complete log of my aMule client. As you will notice, contrary to what I've said in my first post (oversite on my side btw), the UPnP problem starts before "Error retrieving device description" -its starts  in the line "UPnP Error: CUPnPControlPoint::AddPortMapping: WAN Service not detected." Dont have a clue what it means but  the main questions stays the same: the same modem and eMule work just fine.

2010-01-18 23:43:17: Starting aMule 2.2.6 using wxMac v2.8.10
2010-01-18 23:43:17: Creditfile loaded, 0 clients are known
2010-01-18 23:43:17: Loading IP-filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2010-01-18 23:43:17: Loaded 0 IP-ranges from '/Users/XXXXXXX/Library/Application Support/aMule/ipfilter.dat'. 0 malformed lines were discarded.
2010-01-18 23:43:17: Loaded 0 IP-ranges from '/Users/XXXXXXX/Library/Application Support/aMule/ipfilter_static.dat'. 0 malformed lines were discarded.
2010-01-18 23:43:17: External connections disabled in config file
2010-01-18 23:43:17: Created Server UDP-Socket at port 54665
2010-01-18 23:43:17: Created Client UDP-Socket at port 54672
2010-01-18 23:43:17: Universal Plug and Play: bound to 192.168.1.8:50000.
2010-01-18 23:43:17: Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: WAN Service not detected.

2010-01-18 23:43:17:  - This is aMule 2.2.6 using wxMac v2.8.10 based on eMule.
2010-01-18 23:43:17:    Running on Mac OS X (Darwin 10.2.0 i386)
2010-01-18 23:43:17:  - Visit http://www.amule.org to check if a new version is available.

2010-01-18 23:43:17: Loaded 248 flag bitmaps.
2010-01-18 23:43:17: Universal Plug and Play: Internet Gateway Device Detected.
2010-01-18 23:43:17: Universal Plug and Play: Internet Gateway Device Detected.
2010-01-18 23:43:17: Universal Plug and Play: Uninteresting service detected: 'urn:schemas-upnp-org:service:WANEthernetLinkConfig:1'. Ignoring.
2010-01-18 23:43:17: Universal Plug and Play: WAN Service Detected: 'urn:schemas-upnp-org:service:WANPPPConnection:1'.
2010-01-18 23:43:17: Loading server.met file: /Users/XXXXXXX/Library/Application Support/aMule/server.met
2010-01-18 23:43:18: 33 servers in server.met found
2010-01-18 23:43:18: No part files found
2010-01-18 23:43:18: Found 0 known shared files
2010-01-18 23:43:18: Connecting
2010-01-18 23:43:18: Connecting to free.usenet.nl (87.230.83.44 - 87.230.83.44:443) using protocol obfuscation.
2010-01-18 23:43:18: ThreadScheduler: Completed task 'AICH Syncronizing', 0 tasks remaining.
2010-01-18 23:43:18: Connected to free.usenet.nl (87.230.83.44:4661)
2010-01-18 23:43:18: Universal Plug and Play: Successfully retrieved SCPD Document for service urn:schemas-upnp-org:service:WANPPPConnection:1, absEventSubURL: http://192.168.1.1:80/upnp/event?WANPPPConnection.
2010-01-18 23:43:18: Universal Plug and Play: Successfully subscribed to service urn:schemas-upnp-org:service:WANPPPConnection:1, absEventSubURL: http://192.168.1.1:80/upnp/event?WANPPPConnection.
2010-01-18 23:43:18: Universal Plug and Play: WAN Service Detected: 'urn:schemas-upnp-org:service:WANIPConnection:1'.
2010-01-18 23:43:18: Universal Plug and Play: UPNP_EVENT_RECEIVED:
2010-01-18 23:43:18:     SID: uuid:df448cd8-1dd1-11b2-95b8-8ee1218b7a25
2010-01-18 23:43:18:     Key: 0
2010-01-18 23:43:18:     Property list:
2010-01-18 23:43:18:         s:PossibleConnectionTypes='Unconfigured,IP_Routed'
2010-01-18 23:43:18:         s:ConnectionStatus='Connected'
2010-01-18 23:43:18:         s:ExternalIPAddress='87.65.150.146'
2010-01-18 23:43:18:         s:PortMappingNumberOfEntries='0'
2010-01-18 23:43:18:         s:X_Name='WAN Connection'
2010-01-18 23:43:18: Connecting to Master Server 10 (83.233.165.65 - 83.233.165.65:4500) using protocol obfuscation.
2010-01-18 23:43:18: Connected to Master Server 10 (83.233.165.65:4500)
2010-01-18 23:43:18: Your copy of aMule is up to date.
2010-01-18 23:43:18: Universal Plug and Play: Successfully retrieved SCPD Document for service urn:schemas-upnp-org:service:WANIPConnection:1, absEventSubURL: http://192.168.1.1:80/upnp/event?WANIPConnection.
2010-01-18 23:43:18: Universal Plug and Play: Successfully subscribed to service urn:schemas-upnp-org:service:WANIPConnection:1, absEventSubURL: http://192.168.1.1:80/upnp/event?WANIPConnection.
2010-01-18 23:43:18: Universal Plug and Play: Uninteresting service detected: 'urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1'. Ignoring.
2010-01-18 23:43:18: Universal Plug and Play: Uninteresting service detected: 'urn:schemas-wifialliance-org:service:WFAWLANConfig:1'. Ignoring.
2010-01-18 23:43:18: Universal Plug and Play: Uninteresting service detected: 'urn:schemas-microsoft-com:service:OSInfo:1'. Ignoring.
2010-01-18 23:43:18: Universal Plug and Play: Uninteresting service detected: 'urn:schemas-upnp-org:service:Layer3Forwarding:1'. Ignoring.
2010-01-18 23:43:18: Universal Plug and Play: UPNP_EVENT_RECEIVED:
2010-01-18 23:43:18:     SID: uuid:df90e5ba-1dd1-11b2-95b8-8ee1218b7a25
2010-01-18 23:43:18:     Key: 0
2010-01-18 23:43:18:     Property list:
2010-01-18 23:43:18:         s:PossibleConnectionTypes='Unconfigured,IP_Routed'
2010-01-18 23:43:18:         s:ConnectionStatus='Connected'
2010-01-18 23:43:18:         s:ExternalIPAddress='87.65.150.146'
2010-01-18 23:43:18:         s:PortMappingNumberOfEntries='0'
2010-01-18 23:43:18:         s:X_Name='WAN Connection'
2010-01-18 23:43:18: WARNING: free.usenet.nl (87.230.83.44:4661) - NG : Your 54662 port is not reachable. Please review your network config.
2010-01-18 23:43:18: Connection established on: free.usenet.nl
2010-01-18 23:43:18: New clientid is 9595572
2010-01-18 23:43:18: WARNING: You have received Low-ID!
2010-01-18 23:43:18:    Most likely this is because you're behind a firewall or router.
2010-01-18 23:43:18:    For more information, please refer to http://wiki.amule.org
2010-01-18 23:43:20: Error: Could not unlock mutex (error 0: Unknown error: 0)
2010-01-18 23:45:30: Universal Plug and Play: error(UPNP_DISCOVERY_ADVERTISEMENT_ALIVE): Error retrieving device description from http://192.168.1.1:80/igd.xml: Unknown Error.

[GonoszTopi]

the same modem and eMule work just fine.

eMule uses another UPnP library.

[Stu Redman]

Stu, your sugestion seems the quickest one but  I think it would be better to fix the problem as Kry suggested.

Sure, but only phoenix can do that, and he doesn't have a lot of time.

aMule's UPnP works in principle. Just not for you. Whyever. You know, it's a convenience option, saving setup trouble. If it works. If not, then getting it to work is total overkill in comparison to just forward the ports. (Unless you might have a router where you don't have access to the setup, but still has UPnP, then it's valuable of course.)

[Kry]

Stu, stop it. It's a bug. We want to be as compatible as possible. Phoenix happens to be in charge of uPnP. Not your problem, so please, drop it.

[phoenix]

xoltex,

It seems to me that you have at least two, most likely three UPnP devices responding to your requests, and one of them is not working. At least two of them are devices capable of routing. And worst, they share the same ip address. Another possibility is that you have switched on an off your router during aMule operation, but I have ruled this out because you would have to be too quick according to your log times.

It might be a bug on our side, our strategy to detect one working UPnP router device could be failing when there are multiple devices, although I have explicitly tested this situation when I wrote the code. But if you have two routers at the internal network using the same IP address, I see no chance of working.

Try to find your routing devices, check their IP addresses and enable UPnP port forwarding in only one of them. aMule or any other program has no way to know what is the actual routing device, if you have two on your network, other programs might be working out of pure luck, because they have chosen the right one in a 50% chance.

Just to proove my point that there is something very strange with your network, look at these lines:

Code: [Select]

2010-01-18 23:43:18: Universal Plug and Play: UPNP_EVENT_RECEIVED:
2010-01-18 23:43:18:     SID: uuid:df448cd8-1dd1-11b2-95b8-8ee1218b7a25
2010-01-18 23:43:18:     Key: 0and

Code: [Select]

2010-01-18 23:43:18: Universal Plug and Play: UPNP_EVENT_RECEIVED:
2010-01-18 23:43:18:     SID: uuid:df90e5ba-1dd1-11b2-95b8-8ee1218b7a25
2010-01-18 23:43:18:     Key: 0
You have two different successfull subscriptions to the same service at the same IP address. You can see that they are two different subscriptions because the subscription ID (SID) is different. And they both have a key zero, which means it is the first event. Zero can only happen once for each different subscription.

One explanation to what is happening is that aMule could be using one SID and the wrong UPnP device is answering saying he does not recognize having issue this SID. The best theory I can device so far is this, you have at least two, most likely three, UPnP devices at your network, and at least two share the same IP address, 192.168.1.1

Cheers!

[xoltex]

Phoenix - thanks for the time you've put in pulling up the reply ... its really appreciated...

I have read it carefully but I can tell you I have only one device on my home network - it Philips ADSL modem/router. The model is BBOX6726 (and the IP is 192.168.1.1  with WPA2 protection. There are 3 PCs on my network (1MacBook Pro, 1 Mac Mini and 1 Vista box) and thats all. I've checked and they all have a different IP address. Now I dont know if they have the UPnP capabilities or not but from your last message you had a concern about me having more then one device having the sam IP address - right ? Either me or you are missing something fundamentally here (sorry if its me  :-). Could it be that one device can have more then one service to subscribe to ? Dont know ... Anyway, if you find some time I would be more then happy to assist you in sorting this out... This is  not really a questions of my own connection coz like Stu mentioned it can be easily fixed manually - its more about fixing a bug (which I think its there in :-)..

Btw, do you see the following line at the end of the listing:
2010-01-18 23:45:30: Universal Plug and Play: error(UPNP_DISCOVERY_ADVERTISEMENT_ALIVE): Error retrieving device description from http://192.168.1.1:80/igd.xml: Unknown Error.

For me it means that UPnP library in aMule fails processing that file received from my router (http://192.168.1.1:80/igd.xml). As I've mentioned, I can go manually (in  browser) and download file easily. Seeng the above messing means "bug somewhere"  to me. 

Again, if you find the time to work on the above two problems  just let me know and I'll perform all the tests you will need as well as posting here the igd.xml  and other UPnP files.... What ever ...
 
Once more, many thanks and greetings from Belgium !

[Kry]

Me, when I see a duplicated response from a router, I feel like a bug is happening in the router itself - especially with different SIDs. Then again, couldn't a duplicated REQUEST cause this as well?

Whatever the case, I was sceptical (With reason) about two devices with the same IP (collisions anyone?). I think our next move should be finding out how the exact packet flow between computer and router for uPnP and shcekc for duplicated requests/responses, phoenix, does that exist in a debug build category?

[phoenix]

Yeah, libUPnP is a pretty messy code. I checked it out, and at one point it mixes libUPnP generated error codes with http error codes, so the error you are seeing could be something like 404. I did a patch to at least print the error code, if you are using the latest svn code, you can at least test what I am saying.

Kry, a duplicate request? If this was aMule's code fault, I would probably have seen it before. Most UPnP devices go unnoticed with a default configuration ip, I have seen it before, it is pretty common that someone add a pre-configured hardware to the network that happens to be configured in the not so rare address of 192.168.1.1. UPnP has some UDP in the protocol, I would really have to look at the docs and check to be sure where, but not beeing TCP it could mix replies in those cases. But I agree it is pretty hard to keep any kind of conversation with two devices on the same IP at the network, and the protocol seems to have advanced a lot for that to be the case.

libUPnP compiled from the sources with debug enabled prints debug information in "IUpnpErrFile.txt" and "IUpnpInfoFile.txt". These files can be very large, so I do not recommend using a debug version all the time. Also, I used ethereal, now called wireshark to debug the packet flow sequences.