aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Wishlist  (Read 2458 times)

Fester Bestertester

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 48
Wishlist
« on: April 01, 2016, 08:44:48 AM »
G'day!
  Weird and getting worse: protocol fail? Clients that advertise they have bits you need, and connect, but time out without delivering one bit of data. Especially annoying when that connect 'claims' that last chunk of a file that has been delivered at reasonable-or-better rate by several other clients all ready to deliver, but are blocked from doing so by that 'claim' and which do so (quite promptly) only after that tiome-out freeing that chunk.
   Dearly desired: a means of blacklisting and blocking such clients: they're most often the first to connect after a Stop and Resume - another time-out ... grrrrr! IPfilter? Yeah right - where's the HOWTO/FAQ, and how about filter out by client number?
   Also dearly desired: sane queue handling! I see myself going backwards in the queue of clients that will quite spontaneously suddenly connect and deliver.  Clients with quite static queues in the tens will likewise quite spontaneously suddenly connect and deliver. What gives there?

Forlornly hopeful but not expecting anyting progressive ...

Logged

HKM

  • Jr. Member
  • **
  • Karma: 4
  • Offline Offline
  • Posts: 80
  • You don't know enough to know that you don't know.
Re: Wishlist
« Reply #1 on: April 01, 2016, 12:58:05 PM »
Ok I'm bit confused here what you trying to say. But from that I assume you ran into one of the modified aMule clients that sends out fake chunks or download chunks over and over and over? we discussed that in the past in here and eMule forum.

1) Enable and force only protocol obfuscation connections.
2) Used community based ipfilter.dat (http://upd.emule-security.org/ipfilter.zip) thats related to us and for us.
3) If you notice and verify abusive client ban them directly though software/hardware firewall.

No one is going to implement direct ability for users to ban other clients as its discussed for over more than decade which would result in more problems than it would try to fix as leecher would love that. Now ~Mule has few ways to detect bad guys and temporarily ban them until client is restarted again as ban list is cleared. But some offending client does get though in that case I use iptables and ban them directly on system level manually. I was force to take one abusive client offline (mostly always I notice from china) just 2weeks ago when I notice it tried to download 1.4gb file from 6 of my nodes and all of them shows 1gb+ uploaded to it and it reported no chunks. As it was just wasting bandwidth as it download close to 6gb+ same damn file over 12+ hours period. So I directed 2gbps packets and took it offline.
Logged