aMule Forum

English => aMule Help => Topic started by: gav616 on September 13, 2010, 01:28:27 PM

Title: a/eMule IPFilter loads different numbers
Post by: gav616 on September 13, 2010, 01:28:27 PM

using the same list in each client results in,

eMule: 163046
aMule: 202118

there's obviously a reason why...?

Title: Re: a/eMule IPFilter loads different numbers
Post by: Kry on September 13, 2010, 07:55:12 PM

Merged ranges?

Title: Re: a/eMule IPFilter loads different numbers
Post by: Stu Redman on September 15, 2010, 08:24:43 PM

Different blocking levels?

Title: Re: a/eMule IPFilter loads different numbers
Post by: gav616 on September 15, 2010, 08:29:41 PM

Quote from: Kry on September 13, 2010, 07:55:12 PM

Merged ranges?

The filter is compiled and checked with ranges merged already

Quote from: Stu Redman on September 15, 2010, 08:24:43 PM

Different blocking levels?

Its' compiled with 000

Title: Re: a/eMule IPFilter loads different numbers
Post by: GonoszTopi on September 17, 2010, 04:58:39 PM

aMule splits some ranges when storing, although I don't know if it can cause such a big difference.