eMule 0.50a beba 2.72 beta

[tux.]

There are eMule 0.50b "official" alpha builds, latest one from yesterday AFAICS, where beba is based upon. 

[OrnitOrincO]

Uh, ok I'm quite ignorant in that, and not a good tester at all

[tux.]

All testers are good testers. 

[THOR]

Coming back to your previous beta (dated november 2013) all things are fine. Mybe is an "official new bug" 

[tux.]

Depends if you can reproduce it with the official *mule.

[OrnitOrincO]

For some reason I now have (on 0.50.1.10) a high ID, after nearly an hour of connection. Looking through the verbose, I see that UPNP has tried desperately to do its job:
- Traversing the service list of UPnP device failed.
- upnp: Event Subscription Failed
- No more available UPnP implementations left
Then it looks like an external kad port was found. I did a ports test, which failed due to UDP.

Just to point it out, the error message about the too many files etc. comes out exactly 4 minutes after each server connection/change ok, not true, after 15 minutes since the last server change is not happened yet :P

[tux.]

Interesting.

Well, just testing a bit. Indeed, it takes suspiciously longer to get a High ID now...

I just updated the archives with latest eMule upstream changes and MiniUPnP 1.9. 
My beba has a High ID with it.

[tux.]

BTW, I mis-merged this version.  So there's one "if" too much, but that shouldn't affect functionality.

[THOR]

I just updated the archives with latest eMule upstream changes and MiniUPnP 1.9. 
My beba has a High ID with it.

Still low id here 

[OrnitOrincO]

Same here Basically, the only difference I noticed from 0.50.1.10 (and from my previous comment) is that after 4 hours I still not get an high ID kad...

[tux.]

Why does it work for me?

Anything possibly relevant in the verbose log?

[OrnitOrincO]

Hmm, actually, some hours ago I get in the verbose an error message that I've never seen before, so I copypasted it. You have to translate it, also because I do not know what it means despite being in Italian:
Error: Client UDP socket, failed to receive data from [SOMEBODY'S IP]: Error 10040: Le dimensioni del messaggio inviato su un socket di datagramma sono maggiori del buffer interno dei messaggi o di un altro limite di rete oppure le dimensioni del buffer di ricezione del datagramma sono inferiori quelle del datagramma stesso.
Hope this coud help...

[tux.]

No, not related to the IDs at all ...

[OrnitOrincO]

After six hours I got a high ID. Apart from the connection time, my situation looks the same as of February 12 (port test failed due to UDP, etc.)
EDIT: I lost the high ID less than an hour after I got it... :(

[THOR]

This is my verbose log after a few minutes

Spoiler

18/02/2014 08:49:36: Known.met file version is 14 (doesn't support 64bit tags)
18/02/2014 08:49:37: Using 1.60 MB of data for CA clients!
18/02/2014 08:49:38: Using 'C:\Users\THOR\AppData\Local\eMule\config\' as config directory
18/02/2014 08:49:38: Taskbar Notifier Color: R:26 G:19 B:12, Brightness: 20, Transparent: Yes
18/02/2014 08:49:38: Cleaned up known2.met, removed 0 hashsets and purged 0 hashsets of old known files (0 Bytes)
18/02/2014 08:49:38: AICHSyncThread finished
18/02/2014 08:49:38: UploadSpeedSense: Try #1. Collecting hosts...
18/02/2014 08:49:38: ASFU: Starting v3.5...
18/02/2014 08:49:39: Starting Kademlia
18/02/2014 08:49:39: Read 1 source, 3751 keyword, and 46 load entries
18/02/2014 08:49:39: Terminating CIndexed::CLoadDataThread - finished loading data
18/02/2014 08:49:39: Loaded search Spam Filter. Entries - ServerIPs: 0, SourceIPs, 0, Hashs: 0, PositiveHashs: 0, FileSizes: 0, FullNames: 0, SimilarNames: 0
18/02/2014 08:49:41: Starting NODEFWCHECKUDP Kad Search
18/02/2014 08:49:41: Received possible external Kad Port 46760 from 85.65.34.203
18/02/2014 08:49:45: Client TCP socket (OnConnect): Error 10049: Indirizzo richiesto non valido nel proprio contesto.; Client=229.224.51.204 '(null)' (,Connecting/None/None)
18/02/2014 08:49:46: 'http://www.amule.org' has failed the secure identification, V2 State: 0
18/02/2014 08:49:46: received multiple signatures from one client
18/02/2014 08:49:46: received multiple signatures from one client
18/02/2014 08:49:46: received multiple signatures from one client
18/02/2014 08:49:54: Received possible external Kad Port 46760 from 89.76.165.130
18/02/2014 08:49:54: Set external Kad Port to 46760
18/02/2014 08:49:54: Selected client for UDP Firewallcheck: 78.235.190.111
18/02/2014 08:49:55: Received UDP FirewallCheck packet from 78.235.190.111 with incoming port 46760
18/02/2014 08:49:55: New KAD Firewallstate (UDP): Open, using intern port
18/02/2014 08:49:55: Received UDP FirewallCheck packet from 78.235.190.111 with incoming port 46760
18/02/2014 08:49:56: 'http://emule-project.net' has failed the secure identification, V2 State: 0
18/02/2014 08:49:56: received multiple signatures from one client
18/02/2014 08:49:56: received multiple signatures from one client
18/02/2014 08:50:09: UploadSpeedSense: Got enough hosts. Listing the hosts that will be tracerouted:
18/02/2014 08:50:09: UploadSpeedSense: Host #1: 91.200.42.46
18/02/2014 08:50:09: UploadSpeedSense: Host #2: 83.41.239.72
18/02/2014 08:50:09: UploadSpeedSense: Host #3: 176.103.48.36
18/02/2014 08:50:09: UploadSpeedSense: Host #4: 91.200.42.119
18/02/2014 08:50:09: UploadSpeedSense: Host #5: 91.200.42.47
18/02/2014 08:50:09: UploadSpeedSense: Host #6: 151.25.3.227
18/02/2014 08:50:09: UploadSpeedSense: Host #7: 79.38.79.17
18/02/2014 08:50:09: UploadSpeedSense: Host #8: 77.120.115.66
18/02/2014 08:50:09: UploadSpeedSense: Host #9: 46.105.126.71
18/02/2014 08:50:09: UploadSpeedSense: Host #10: 78.235.190.111
18/02/2014 08:50:09: UploadSpeedSense: Starting traceroutes to find last common host.
18/02/2014 08:50:10: UploadSpeedSense: Pinging for TTL 1...
18/02/2014 08:50:10: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=2.23ms (2.23ms 1ms) TTL=1
18/02/2014 08:50:10: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.55ms (1.55ms 0ms) TTL=1
18/02/2014 08:50:10: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.37ms (1.37ms 0ms) TTL=1
18/02/2014 08:50:10: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.29ms (1.29ms 0ms) TTL=1
18/02/2014 08:50:10: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.26ms (1.26ms 0ms) TTL=1
18/02/2014 08:50:10: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.05ms (1.05ms 0ms) TTL=1
18/02/2014 08:50:13: Error from 79.38.79.17: Error=11010
18/02/2014 08:50:13: UploadSpeedSense: Failure #1 to ping host! (TTL: 1 IP: 79.38.79.17 error: 11010). Sleeping 1 sec before retry. Error info follows.
18/02/2014 08:50:13: IP_REQ_TIMED_OUT (11010)
18/02/2014 08:50:18: UploadSpeedSense: Failure #2 to ping host! (TTL: 1 IP: 79.38.79.17 error: 10060). Sleeping 1 sec before retry. Error info follows.
18/02/2014 08:50:18: Pinger: Error 10060: Impossibile stabilire la connessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato.
18/02/2014 08:50:19: UploadSpeedSense: Unknown pinging error! (TTL: 1 IP: 79.38.79.17 status: 10060). Reason follows. Changing ping method to see if it helps.
18/02/2014 08:50:19: Pinger: Error 10060: Impossibile stabilire la connessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato.
18/02/2014 08:50:22: UploadSpeedSense: Failure #1 to ping host! (TTL: 1 IP: 77.120.115.66 error: 10060). Sleeping 1 sec before retry. Error info follows.
18/02/2014 08:50:22: Pinger: Error 10060: Impossibile stabilire la connessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato.
18/02/2014 08:50:23: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.64ms (1.64ms 1ms) TTL=1
18/02/2014 08:50:23: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.22ms (1.22ms 0ms) TTL=1
18/02/2014 08:50:23: Reply (ICMP-pinger) from 192.168.0.1: bytes=0 time=1.19ms (1.19ms 0ms) TTL=1
18/02/2014 08:50:23: UploadSpeedSense: Host at TTL 1: 192.168.0.1
18/02/2014 08:50:23: UploadSpeedSense: Pinging for TTL 2...
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=15.10ms (15.10ms 14ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.42ms (14.42ms 14ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=15.26ms (15.26ms 14ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.37ms (14.37ms 13ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=15.22ms (15.22ms 14ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.67ms (14.67ms 14ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.25ms (14.25ms 13ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=15.32ms (15.32ms 14ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=13.91ms (13.91ms 13ms) TTL=2
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.87ms (14.87ms 13ms) TTL=2
18/02/2014 08:50:23: UploadSpeedSense: Host at TTL 2: 213.205.0.145
18/02/2014 08:50:23: UploadSpeedSense: Pinging for TTL 3...
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.62.81: bytes=0 time=14.36ms (14.36ms 13ms) TTL=3
18/02/2014 08:50:23: Reply (ICMP-pinger) from 213.205.62.97: bytes=0 time=14.80ms (14.80ms 14ms) TTL=3
18/02/2014 08:50:23: UploadSpeedSense: Found differing host at TTL 3: 83.41.239.72. This will be the host to ping.
18/02/2014 08:50:23: UploadSpeedSense: Done tracerouting. Evaluating results.
18/02/2014 08:50:23: UploadSpeedSense: Found last common host. LastCommonHost: 213.205.0.145 @ TTL: 2
18/02/2014 08:50:23: UploadSpeedSense: Found last common host. HostToPing: 83.41.239.72
18/02/2014 08:50:23: UploadSpeedSense: Finding a start value for lowest ping...
18/02/2014 08:50:24: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.86ms (14.86ms 14ms) TTL=2
18/02/2014 08:50:24: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.59ms (14.59ms 13ms) TTL=2
18/02/2014 08:50:24: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=15.11ms (15.11ms 14ms) TTL=2
18/02/2014 08:50:24: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.80ms (14.80ms 14ms) TTL=2
18/02/2014 08:50:24: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.98ms (14.98ms 14ms) TTL=2
18/02/2014 08:50:25: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=15.47ms (15.47ms 14ms) TTL=2
18/02/2014 08:50:25: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.53ms (14.53ms 13ms) TTL=2
18/02/2014 08:50:25: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.46ms (14.46ms 13ms) TTL=2
18/02/2014 08:50:25: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=15.14ms (15.14ms 14ms) TTL=2
18/02/2014 08:50:25: Reply (ICMP-pinger) from 213.205.0.145: bytes=0 time=14.87ms (14.87ms 14ms) TTL=2
18/02/2014 08:50:26: UploadSpeedSense: Lowest ping: 20 ms. (Filtered lower values. Lowest ping is never allowed to go under 20 ms)
18/02/2014 08:50:26: UploadSpeedSense: Done with preparations. Starting control of upload speed. (First 60 seconds will be in fast reaction mode)

There are also many strings like these:

Spoiler

18/02/2014 08:59:25: Kad: Request flood detected for opcode 0x44 (0x44) from IP 61.147.76.66 - Droping packets with this opcode
18/02/2014 08:59:28: Kad: Request flood detected for opcode 0x44 (0x44) from IP 183.136.156.7 - Droping packets with this opcode
18/02/2014 08:59:30: Kad: Request flood detected for opcode 0x34 (0x34) from IP 61.147.76.66 - Droping packets with this opcode