Mldonkey 3.0.0 binary with UTF-8 patch for MIPSEL is ready to test in Googel Code.

I have compiled mldoney 3.0.0 with static compile and UTF-8 patch. Now, the file is ready in the google code.

First, unpack mlnet.byte.static-3.0.0.mipsel.7z and put mlnet.byte.static to your NAS.

Change the permission to 755 and then open a screen to run the program in background.

./mlnet.byte.static

If you have any comment on it, feedback to me :).

Comments

It works great for me. This

It works great for me. This version fixed an urgent bug which will cause CPU overload.
So far, no bug found yet.

Thank you very much.

請先確認對外網路連線正常, 再確認是否/etc/resolv.conf設定正確

如果是DNS不能解析的話, 首先先確認對外網路連線正常, 接著試著ping 209.85.143.147

看是否有連通

Pinging www.l.GOOGLE.COM [209.85.143.147] with 32 bytes of data:

Reply from 209.85.143.147: bytes=32 time=288ms TTL=232
Reply from 209.85.143.147: bytes=32 time=300ms TTL=232
Reply from 209.85.143.147: bytes=32 time=294ms TTL=232
Reply from 209.85.143.147: bytes=32 time=293ms TTL=232

Ping statistics for 209.85.143.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 288ms, Maximum = 300ms, Average = 293ms

如果有通時便是DNS的設定問題, 可以查找 /etc/resolv.conf 並加入所須的nameserver如下

nameserver 192.168.168.1
nameserver 168.95.1.1

在ddwrt下的确好用,谢谢 可是DNS解析不能工作。

在ddwrt下的确好用,谢谢
可是DNS解析不能工作。

這個在DD-WRT下已經非常好用了,

這個在DD-WRT下已經非常好用了, 只是還有一處Unicode編碼問題, 不知道有沒有辦法解決. 共享檔案如果是UTF-8的檔名, 在Sancho以及mldonkey下查看都是沒有錯誤的. 但是其他eMule去連結到我的mldonkey上, 看到的卻是錯誤的ascii編碼. eMule在Win32下可能是UTF16吧