Hi,
I've been trying to get official eMule application to work inside i2p network for a while, every now and then with some new ideas.
Yesterday I was first time succesful to connect client with server within i2p network. I put up an eepsite with picture and short video, which can be found from emule-info.i2p.
I copy/paste the information here, so it will be available on internet as well, if someone finds it usable.
Download and install official eMule client.
(You can block it with firewall and restrict connection to public networks, to make it sure it's i2p only)
Start the application and set nickname and other things as you wish.
Most important thing is to setup your TCP port to 7656 and UDP port to 7655 (Those are default ports of i2p's SAM bridge).
Disable protocol obfuscation and all secure connection ticks, since they are not needed in i2p network.
At this point it would be a good point to create Socks5 client service in "hidden services manager".
In my example, I have used port 4337.
At the same you can go to Settings and choose clients tab. Make sure SAM application bridge is enabled.
Next you can open eMule client again. Go to options and choose proxy tab. Select Socks5 from dropdown menu.
Enter IP as 127.0.0.1 and port (4337 in example) you used for creating the Socks5 client.
All the connection settings, download/upload limiters can be set to your own taste.
That's it.
To test your connection, you can connect my test server I created. I keep it running 24/7 for now.
ed2k://|server|4lmtenjiesfeqcxzpvk3unszrgrfodk7jqzebagcj4kp7paqaxfa.b32.i2p|4661|/
P.S. Even the eMule's IRC Works. I used irc.postman.i2p in eMule IRC options and disabled 'Delay opening client tunnel' from IRC Tunnel management options.
P.P.S I got the server working within Win7 x64, with Microsoft's Loopback network driver.
I didn't get Lugdunum to work in local network, so I used the loopback driver, to trick the server software.
I used Lugdunum 17.15 software in my tests. On i2p side I created standard server with 4661 port.
-----------------------------------------------------------
[donkey.ini configuration]
[server]
name=i2pTest
desc=Serving the i2p Community
maxClients=100
public=true
logFile=true
verbose=true
welcome[0]= i2p P2P Server
LOWIDenable=1
LOWIDpercent=20
blacktime=3600
blocsize=4194304
login_timeout=60
max_clients_per_ip=12
maxservers=4096
msgrandomport=4662
quickack=true
minVersion=39
maxVersion=2000
thisIP=[Your IP]
port=4661
threads=3
type=key
tableSize=3089
keywordSearch=true
-----------------------------------------------------------
The donkey.ini configuration is modified version of something, I found from these forums.
All the settings are not needed and might be more harmful, than necessary, but works as an example
Page 1 of 1
A Way To Run Official Emule Within I2p Network
#2
Posted 17 October 2024 - 06:48 AM
Really interesting, thank you!!!
This post has been edited by ]Axl[: 17 October 2024 - 06:48 AM
#3
Posted 27 October 2024 - 01:37 PM
Quote
Axl[' date='17 October 2024 - 08:48 AM' timestamp='1729147686' post='1109146']
Really interesting, thank you!!!
Really interesting, thank you!!!
I have been now testing over a week, to find completely working solution, but I'm afraid that my method still doesn't work well enough.
Well, I have tried 4-5 methods already and get it connect with multiple ways, but sames problems prevail.
What works:
Sharing files
IRC
Connecting to server with High ID
Kademlia operates, but haven't been able to connect nodes
Search works from server
What doesn't:
File Transfer
When I posted the first information, I had only been able to make single connection and everything seemed to operating perfectly.
I expected to some other users to connect, but in the end I had to create multiple VM boxes and do the testing myself.
At that point the problems started, when I started making multiple connections.
If I change some i2p settings, I'm able to connect with multiple clients.
BUT
All the users has the same ID, and for that reason the downloads doesn't start.
If I change settings little more, only one client is able to connect, and when other one connects the other will drop out.
In the end, it seems that the server is not able to treat the incoming connections properly and for that reason thinks, every connection is from same address.
It might be because, the server/client is not created to be used in LAN, so it would need some minor modifications to make it work properly.
Information is still valid, to the connection point. Wanted to continue the story little bit, if someone starts to test it more.
Connection can be made through socks/http proxy or completely without them using loopback adapters ips in i2p.
Many ways but the result is always the same.
If someone has ideas how I could get around this problem, let me know. I'll keep the configuration for now, for if I can think of something else what I could try.
For now I'm starting to run out of ideas myself.
Page 1 of 1