Emule 0.50B Beta1 Released
#42
Posted 13 April 2015 - 10:18 AM
fox88, on 11 April 2015 - 10:58 PM, said:
the example was about verbose log, because ordinary log is uninformative - we already heard that UPnP failed.
Also it might be interesting to give logs from both 0.50a and 0.50b beta1.
Zangune, on 11 April 2015 - 11:50 PM, said:
Thanks for the instruction.
0.50a log:
2015/4/13 13:35:16: Known.met file version is 14 (doesn't support 64bit tags)
2015/4/13 13:35:16: Using MiniUPnPLib based implementation
2015/4/13 13:35:16: miniupnpc © 2006-2008 Thomas Bernard - http://miniupnp.free.fr/
2015/4/13 13:35:16: Using 'C:\Users\barbara\AppData\Local\eMule\config\' as config directory
2015/4/13 13:35:16: Taskbar Notifier Color: R:58 G:101 B:195, Brightness: 102, Transparent: No
2015/4/13 13:35:16: AICHSyncThread finished
2015/4/13 13:35:16: UploadSpeedSense: Try #1. Collecting hosts...
2015/4/13 13:35:17: Cleaning up TrackedClientList, 0 clients on List...
2015/4/13 13:35:17: ...done, 0 clients left on list
2015/4/13 13:35:24: Using Windows Service based UPnP Implementation for current try
2015/4/13 13:35:24: UPNP: No Internet Gateway Devices found, aborting
2015/4/13 13:35:33: Found no UPnP gateway devices - will retry with different parameters
2015/4/13 13:35:42: Found no UPnP gateway devices
2015/4/13 13:35:42: No more available UPnP implementations left
0.50B Beta1 log:
2015/4/13 13:30:45: Known.met file version is 15 (does support 64bit tags)
2015/4/13 13:30:45: Using MiniUPnPLib based implementation
2015/4/13 13:30:45: miniupnpc © 2006-2013 Thomas Bernard - http://miniupnp.free.fr/
2015/4/13 13:30:45: Using 'E:\eMule0.50b_BETA1\config\' as config directory
2015/4/13 13:30:45: Taskbar Notifier Color: R:58 G:101 B:195, Brightness: 102, Transparent: No
2015/4/13 13:30:45: Cleaned up known2.met, removed 0 hashsets and purged 0 hashsets of old known files (0 Bytes)
2015/4/13 13:30:45: AICHSyncThread finished
2015/4/13 13:30:45: UploadSpeedSense: Try #1. Collecting hosts...
2015/4/13 13:30:45: AICH Hashset to write should be already present in known2.met - QS2JBLHVP63HUBRPRS43ACFEBVUSU7IW
2015/4/13 13:30:46: Cleaning up TrackedClientList, 0 clients on List...
2015/4/13 13:30:46: ...done, 0 clients left on list
2015/4/13 13:30:46: Using Windows Service based UPnP Implementation
2015/4/13 13:30:46: List of UPNP devices found on the network:
2015/4/13 13:30:46: Desc: http://192.168.1.1:4.../wps_device.xml, st: uuid:00000000-0000-1000-0000-e005c5e03a3e
2015/4/13 13:30:46: Desc: http://192.168.1.1:4.../wps_device.xml, st: upnp:rootdevice
2015/4/13 13:30:46: Desc: http://192.168.1.1:1900/igd.xml, st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
2015/4/13 13:30:46: Found valid IGD : http://192.168.1.1:1900/ipc
2015/4/13 13:30:46: Our LAN IP: 192.168.1.101
2015/4/13 13:30:46: No UPnP Mappings to remove, aborting
2015/4/13 13:30:46: Adding PortMapping failed, Error Code 4294967185
2015/4/13 13:30:55: Found no UPnP gateway devices - will retry with different parameters
2015/4/13 13:31:04: Found no UPnP gateway devices
2015/4/13 13:31:04: No more available UPnP implementations left
Seems like both failed for different reasons.
#43
Posted 13 April 2015 - 10:52 AM
If I read well the Windows implementation of UPnP in eMule BETA 1 found "something more", but maybe it is just a coincidence.
Desc: http://192.168.1.1:1900/igd.xml, st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
and
Found no UPnP gateway devices
Does it mean UPnP service on router dies?
I strongly believe most of the times UPnP fails because of the router, not eMule. Is this the case?
#44
Posted 13 April 2015 - 04:21 PM
Zangune, on 13 April 2015 - 06:52 PM, said:
If I read well the Windows implementation of UPnP in eMule BETA 1 found "something more", but maybe it is just a coincidence.
Desc: http://192.168.1.1:1900/igd.xml, st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
and
Found no UPnP gateway devices
Does it mean UPnP service on router dies?
I strongly believe most of the times UPnP fails because of the router, not eMule. Is this the case?
It's not the router's problem, because kMule (and also other apps) can setup up UPnP successfully.
#45
Posted 13 April 2015 - 04:48 PM
hunzhang, on 13 April 2015 - 01:18 PM, said:
2015/4/13 13:30:46: Using Windows Service based UPnP Implementation
Seems like both failed for different reasons.
It appears you are using Windows service UPnP implementation, not miniUPnPc one.
Please check your settings for UPnP in config\preferences.ini
Are there lines with the following parameters?
DisableMiniUPNPLibImpl
DisableWinServImpl
#46
Posted 13 April 2015 - 04:55 PM
fox88, on 14 April 2015 - 12:48 AM, said:
hunzhang, on 13 April 2015 - 01:18 PM, said:
2015/4/13 13:30:46: Using Windows Service based UPnP Implementation
Seems like both failed for different reasons.
It appears you are using Windows service UPnP implementation, not miniUPnPc one.
Please check your settings for UPnP in config\preferences.ini
Are there lines with the following parameters?
DisableMiniUPNPLibImpl
DisableWinServImpl
Sorry but I can't find these lines in my config\preferences.ini file
#47
Posted 14 April 2015 - 04:18 AM
Then I noticed these lines in the verbose log:
4/13/2015 9:10:37 PM: UPnP device state variable PossibleConnectionTypes changed to IP_Routed in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:37 PM: UPnP device state variable ConnectionStatus changed to Connected in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:37 PM: UPnP device state variable ExternalIPAddress changed to xxx.xxx.xxx.xxx in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:37 PM: UPnP device state variable PortMappingNumberOfEntries changed to 8 in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:38 PM: UPnP device state variable PossibleConnectionTypes changed to IP_Routed in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:38 PM: UPnP device state variable ConnectionStatus changed to Connected in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:38 PM: UPnP device state variable ExternalIPAddress changed to xxx.xxx.xxx.xxx in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:38 PM: UPnP device state variable PortMappingNumberOfEntries changed to 7 in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable PossibleConnectionTypes changed to IP_Routed in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable ConnectionStatus changed to Connected in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable ExternalIPAddress changed to xxx.xxx.xxx.xxx in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable PortMappingNumberOfEntries changed to 8 in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable PossibleConnectionTypes changed to IP_Routed in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable ConnectionStatus changed to Connected in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable ExternalIPAddress changed to xxx.xxx.xxx.xxx in urn:upnp-org:serviceId:WANPPPConn1 4/13/2015 9:10:40 PM: UPnP device state variable PortMappingNumberOfEntries changed to 9 in urn:upnp-org:serviceId:WANPPPConn1
Does this has something to do with the UPnP failure after restart eMule a fixed number of times? Once that happened, I'll have to reboot my router to get it work again.
This post has been edited by Enig123: 14 April 2015 - 04:20 AM
#48
Posted 15 April 2015 - 12:59 PM
Enig123, on 14 April 2015 - 07:18 AM, said:
Maybe it was router's fault, not eMule's?
My little test.
Downloaded 0.50b beta1 binary, unpacked and executed first run wizard.
I enabled UPnP in router, and about 5 times in Options->Connections did the following: check 'Use UPnP to setup ports' - 'Apply' - see successful forwarding in Verbose log - uncheck 'Use UPnP...' - 'Apply' - and repeat the sequence again.
So it was working.
Then I started and exited eMule about 30 times, each time with successful UPnP results.
#49
Posted 17 April 2015 - 05:18 AM
hunzhang, on 13 April 2015 - 09:55 AM, said:
fox88, on 14 April 2015 - 12:48 AM, said:
hunzhang, on 13 April 2015 - 01:18 PM, said:
2015/4/13 13:30:46: Using Windows Service based UPnP Implementation
Seems like both failed for different reasons.
It appears you are using Windows service UPnP implementation, not miniUPnPc one.
Please check your settings for UPnP in config\preferences.ini
Are there lines with the following parameters?
DisableMiniUPNPLibImpl
DisableWinServImpl
Sorry but I can't find these lines in my config\preferences.ini file
You might want to try X-mod, in which has an UPnP implementation originally from ACAT mod, to see it it works for your router.
#50
Posted 18 April 2015 - 01:34 PM
Enig123, on 17 April 2015 - 01:18 PM, said:
hunzhang, on 13 April 2015 - 09:55 AM, said:
fox88, on 14 April 2015 - 12:48 AM, said:
hunzhang, on 13 April 2015 - 01:18 PM, said:
2015/4/13 13:30:46: Using Windows Service based UPnP Implementation
Seems like both failed for different reasons.
It appears you are using Windows service UPnP implementation, not miniUPnPc one.
Please check your settings for UPnP in config\preferences.ini
Are there lines with the following parameters?
DisableMiniUPNPLibImpl
DisableWinServImpl
Sorry but I can't find these lines in my config\preferences.ini file
You might want to try X-mod, in which has an UPnP implementation originally from ACAT mod, to see it it works for your router.
yeah kMule has a working UPnP function also I can set virtual server in my router. Thanks anyway.
#51
Posted 18 April 2015 - 09:23 PM
#52
Posted 19 April 2015 - 06:23 AM
Actually when eMule official want to add UPnP to the project, I have recommended this implementation as an alternative. Since SS said he might add other implementations to eMule offcial, I think it's time to test other options, to offer useful feedback for SS to decide.
#53
Posted 19 April 2015 - 08:44 AM
#54
Posted 19 April 2015 - 08:53 AM
Enig123, on 19 April 2015 - 09:23 AM, said:
In that particular case it would be incorrect way to go.
Official and kMule use more or less the same implementation, but different versions of the same library:
0.50a 1.4
kMule 1.8
0.50b 1.9
So the real question is: are implementation differences meaningful, or there is a regression in miniupnpc library.
If lucky owners of TP-Link feel technical enough to try command line utility and test library itself, here is the link to downloads page. You will need Windows executable, starting with the latest one with the name upnpc-exe-win32-20140422.zip.
#55
Posted 19 April 2015 - 07:51 PM
#56
Posted 19 April 2015 - 08:50 PM
#57
#58
#59
Posted 20 April 2015 - 09:34 AM
Quote
The same here. No UPnP working on official emule 0.50a and 0.50b, UPnP full working on kmule.
TPLINK TL-WR841ND last firmware.
]Axl[,
hunzhang
Could you try to post verbose logs of successful UPnP action in kMule?
Edit. If nobody is interesting in making things better, it will remain the same.
This post has been edited by fox88: 02 May 2015 - 05:54 PM
#60
Posted 20 April 2015 - 09:41 AM
Microsoft is long known to not only break stuff and backwards compatibility but also introduce new incompatibilities...