eMule has now got the basics of Shareaza type IP blocking. Currently it's a .DAT text file that is edited with the static server IP and hopefully ip rangers. A static server Ip can be a nodns.com type address.
I'm still very worried about it needing a SERVER, but we might be able to use off shore servers and IP block everything else at the client side.
Testing stage, anyone interested to work on this?
Testing eMule for TassieP2P
Here are the descriptions of the two new files for default static servers.
You could cache the serves on a remote web page and have them load up when you run, much like GNUtella GWebCache. I don't know the eMule protocol to this though.
By putting in one IP or DNS and making sure the client is all customised to local share, you should be able have a clean break to the server without world traffic. The server is then in question if it can corrupting the situation which as far as I know, shouldn't look anywhere else except the users connected.
If a rogue person uses the server then it's will corrupt everyones server lists during the session or if a user uploads server address then that also will cause haywire.
The person running the server could firewall out world IPs for the server side!
.
Code: Select all
--"What is the adresses.dat file for?"
You can enter a serverlist URL in that file. eMule will then get the serverlist from that
URL at startup (when the option "Auto-update serverlist at startup" is activated)
You could cache the serves on a remote web page and have them load up when you run, much like GNUtella GWebCache. I don't know the eMule protocol to this though.
Code: Select all
--"What is the staticservers.dat file good for?"
You can enter your favorite servers here to have them permanently in your serverlist
with high priority. You can enter the static IP of the server, or an adress like
goodserver.dyndns.net. You can also add static servers to this file via the server tab
in eMule (right-click -> add to static serverlist)
By putting in one IP or DNS and making sure the client is all customised to local share, you should be able have a clean break to the server without world traffic. The server is then in question if it can corrupting the situation which as far as I know, shouldn't look anywhere else except the users connected.
If a rogue person uses the server then it's will corrupt everyones server lists during the session or if a user uploads server address then that also will cause haywire.
The person running the server could firewall out world IPs for the server side!
.
Anachronous wrote:might soon be worth it.
Why is that?
If anyone gets a eMule system going them I will help to support it. I don't like the idea of it having a server, though.
Alot more people will use eMule in Tassie as they have had others from other States that have given testimonials, even though it's near identical to shareaza in sharing department. Actually eMule has a worse defining system.
For people interested, download the new alpha 27a and edonkey's server for the ip restriction.
Anach wrote:http://www.netspace.net.au/~pfarac/
This is the link for the NSW info.
seems it works ok for them.
It's not worth it now, unless all DC people move to it. As you know there are people that don't want to move off the horse and cart.
Emule may still have contamination problems(problems where corrupt IP lists flow in to all when someone changes a setting.) If someone runs a server I'll come in and have a trial!
Sharaza is doing the job for me, it only lacks a in built chat room.
