[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Pydonkey-general] xmule trace ...
From: |
Joël Vennin |
Subject: |
[Pydonkey-general] xmule trace ... |
Date: |
Thu, 29 May 2003 21:45:29 +0200 |
User-agent: |
KMail/1.5.2 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've make some trace produce by xmule ....
I've join the file. There is a strange behavior in emule protocol.
81.51.193.33 send to 80.224.179.139
Protocol: E3 Opcode: 1 - hello
80.224.179.139 send to 81.51.193.33
Protocol: C5 Opcode: 1 - Emule Hello
81.51.193.33 send to 80.224.179.139
Protocol: C5 Opcode: 2 - Emule Hello Answer
80.224.179.139 send to 81.51.193.33
Protocol: E3 Opcode: 4C - hello answer
81.51.193.33 send to 80.224.179.139
Protocol: E3 Opcode: 58 - File Request
80.224.179.139 send to 81.51.193.33
Protocol: E3 Opcode: 59 - File Request Answer
80.224.179.139 send to 81.51.193.33
Protocol: E3 Opcode: 50 - File Status
81.51.193.33 send to 80.224.179.139
Protocol: E3 Opcode: 54 - Slot Request
80.224.179.139 send to 81.51.193.33
Protocol: C5 Opcode: 60 - Emule Rank
You can see that the other client (80.224 ...) which is an emule client,
doesn't need a File Status Request. It send automaticly the File Status ....
where as edonkey client need a file status request ...
You can see all the protocol in the log ....
I must make a trace of what pydonkey make, to know where is the error !
Jol
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+1mNcOzJ7itUoJpQRAg+dAJ44oNKsq/F7EggY9iILPfCT68QTKACfS85y
mp8GTAXxwu/gqk7K53YvDzo=
=OZK6
-----END PGP SIGNATURE-----
result_xmule
Description: Text document
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Pydonkey-general] xmule trace ...,
Joël Vennin <=