Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[eidimon]

hi everyone.a few days now, there's a client with the same nick, but with different ip, that asks for my shared files list all the time, and  although i deny, he keeps asking for my list over and over again.
at first i thought it was something like the RIAA or something, but now i am not so sure.
i don't know weather i am over-reacting or being too suspicious,but i saw his ip, and added it to my ipfilter.dat file.
the problem is that a person with that nick (gea*) is always on que,with the same client (i think the icon means shareazaa).
sometimes i see three or four people with that very nick on my que, different ip,  but all the time asking for my shared list.
i have come to the conclusion that it probably is the same person, using more instances of the same program,connecting through proxies (is this possible?).
And, as i am sick of manually adding that person's ipto my ipfilter.dat all the time , i wanted to ask : is there any way i can make amule ban that client by it's nickname?
 i mean, is there any way i can tell emule,"when a person with a nick gea* requests a download or anything automaticaly deny"?
just by his nick (pretty unique i think), as he uses more than one ip
don't know if i just have some kind of syndrom and just imajine things, but it's really annoying.
if anyone could help, i'd be very thankful...

[deltaHF]

Code: [Select]

#!/bin/bash

# Create special MLDONKEY chain
iptables -t filter -N MLDONKEY
iptables -t filter -F MLDONKEY

# Create the logdrop chain to log & drop a packet
iptables -t filter -N MLDONKEY_LOGDROP
iptables -t filter -F MLDONKEY_LOGDROP
iptables -t filter -A MLDONKEY_LOGDROP -j LOG --log-prefix "MLDONKEY"
iptables -t filter -A MLDONKEY_LOGDROP -j DROP

# Jump to the special MLD chain at the end of the INPUT chain (commented out)
#iptables -t nat -A INPUT -j MLDONKEY

# List of ip ranges to ban
iptables -t filter -I INPUT 1 -s 38.113.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 38.115.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 38.117.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 38.118.0.0/15 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 65.19.175.0/24 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 66.54.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 66.117.0.0/16 -j MLDONKEY_LOGDROP
iptables -t filter -I INPUT 1 -s 207.234.0.0/16 -j MLDONKEY_LOGDROP

cheers

[Jacobo221]

It's not RIAA or anything like that, at least apparently.
http://www.amule.org/wiki/index.php/Geaiez
Anyway, using theabove iptables script deltaHF gave you, will allow you to stop seeing those clients
Greetings!

[eidimon]

yeap,it's geaiez alright!thanks.i'll try the script and see what happens...

[eidimon]

unfortunately,they're still here...at the column named client software it says eDonkeyHybrid. do you thing changing mldonkey in the script with eDonkeyHybrid could be the solution?

[phoenix]

eidimon,

No, changing the name does nothing to help you. What you want is to add a new ip. If you are able to find the ip of the client you dont want, do this (as root, of course):

Suppose the ip is 127.0.0.1 (DONT USE THIS NUMBER, PLEASE), run:

$ iptables -t filter -A INPUT -s 127.0.0.1 -j MLDONKEY_LOGDROP

man iptables is also your friend.

Cheers!

[Jacobo221]

geiez is not only _one_ client, but many, so you'll have to keep a large track of ips of geaiez users. I would rather just don't care about it and disable listing shared files.
Greetings!

[eidimon]

listing my shared files was disabled anyway.it just was quite annoying that someone (or at least at first i thought it was one) was insisting on seeing my shared files list, although i didn't want them to see it.i'll do a little reading on iptables, but if there's nothing more i can do, i'll just leave it the way it is.thanks,anyway...

[Xaignar]

There is no point in trying to ban them, as they are valid clients with the same name and an unfortunate bug of asking for the shared files upon connection.