aMule Forum
English => en_Bugs => Topic started by: Schuttwegraeumer on April 24, 2010, 02:38:41 PM
-
This yes, the other bugs: NO.
Now (10107) the server.met is loadet at startup.
But the ipfilter.dat is not used by amule.
Problems with loading files in the .amule dir?
Testet with 10107.
-
This yes, the other bugs: NO.
What other bugs?
But the ipfilter.dat is not used by amule.
Working fine here. What error messages do you get? Any other information?
-
Since 10102, the serverlist is loadet at startup, but the ipfilter.dat is not loadet.
The settings shows correct settings but no filter effekt.
If i run a search with all servers, I got SPAM like with deaktivatet ipfilter.dat.
-
Is the IP filter not loaded or not updated?
Is there a valid ipfilter.dat in your config?
What does the log file say regarding loading of IP filter?
-
Is the IP filter not loaded or not updated?
Is there a valid ipfilter.dat in your config?
What does the log file say regarding loading of IP filter?
Its not loadet, i use the filter from BISS.
http://blocklistpro.com/download-center/view-details/p2p-ip-filters/1635-pipfilter.dat.gz.html
-
2010-04-24 17:55:47: amuleAppCommon.cpp(329): Initialising aMule SVN using wxGTK2 v2.8.10 (Debugging) (Snapshot: rev. 10106)
[...]
2010-04-24 17:55:49: IPFilter.cpp(119): Loading IP filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2010-04-24 17:55:57: IPFilter.cpp(435): Loaded 269080 IP-ranges from '/home/topi/.aMule/ipfilter.dat'. 0 malformed lines were discarded.
2010-04-24 17:55:57: IPFilter.cpp(435): Loaded 0 IP-ranges from '/home/topi/.aMule/ipfilter_static.dat'. 0 malformed lines were discarded.
2010-04-24 17:55:58: IPFilter.cpp(628): IP filter is ready
Although it takes ~8 seconds to load, it does load.
Is there a valid ipfilter.dat in your config?
What does the log file say regarding loading of IP filter?
-
@ GonoszTopi
Yes, and?
The ipfilter is not in use.
-
If you don't answer our questions we can't help you.
-
I splitted the topic because it's now about IPFilter, not server.met.
Current IPFilter implementation definiately has some bugs:
1) "Everything is filtered until IPFilter ready" renders source seeds useless:
2010-04-25 16:13:13: IPFilter.cpp(525): IPFilter: Filtered IP xxx.xxx.xxx.xxx because filter isn't ready yet.
2010-04-25 16:13:13: PartFile.cpp(2786): IPFilter: Ignored source (IP=xxx.xxx.xxx.xxx) received via Source Seeds - IPFilter
2010-04-25 16:13:13: IPFilter.cpp(525): IPFilter: Filtered IP yyy.yyy.yyy.yyy because filter isn't ready yet.
2010-04-25 16:13:13: PartFile.cpp(2786): IPFilter: Ignored source (IP=yyy.yyy.yyy.yyy) received via Source Seeds - IPFilter
[...and so on...]
2) though it did filter something, it doesn't count:
$ ./amulecmd -c statistics | grep Filtered
> Filtered: 0
> Filtered Servers: 0
$
Otherwise, working as expected, i.e. after connected to networks, wait some time elapsed:
$ ./amulecmd -c statistics | grep 'Filtered:'
> Filtered: 10
$
-
the amule seems to work normally.
The log shows the expected lines.
but the search ist not filtered, that means the unwanted servers are not filtered.
The ipfilter.det has not changed since 30.03.2010.
The first SVN with this error was the SVN with the non working server.met.
Than the server.met bug is fixed (10102) but the ipfilter.dat bug isn't.
-
Ok, how to test the IP filtering?
-
WTF???ß
I addet a server IP manually to the ipfilter.dat file and this server got filtered out correctly.
The ipfilter seems to be ok.
But why the SPAm Effekt.
I could use the "Global" serach function without the spam but now the spam ist back.
The spam commes back exactly at the same time the server.met but was in the 1010x SVN.
-
Just a test: does the spam happen with a pre-10100 client too? (I mean now, with the old client)
(I guess it's a new fake server which isn't yet in the IP filter.)
-
Just a test: does the spam happen with a pre-10100 client too? (I mean now, with the old client)
(I guess it's a new fake server which isn't yet in the IP filter.)
I must compile them, i have SVNs befor 10107 only for AMD64 and i have here a old AMD athlon without AMD64.
Give me a few minutes.
-
Ok, same effect with 10099, a lot of spam.
How can I finde the server in my serverlist?
-
Current IPFilter implementation definiately has some bugs:
Fixed in 10113.
The log shows the expected lines.
Schutti, when I ask for a log I'd like to see it with my own eyes.
How can I finde the server in my serverlist?
The one you are connected to at the moment?
-
Current IPFilter implementation definiately has some bugs:
Fixed in 10113.
The log shows the expected lines.
Schutti, when I ask for a log I'd like to see it with my own eyes.
How can I finde the server in my serverlist?
The one you are connected to at the moment?
2010-04-25 19:46:50: Loading IP filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2010-04-25 19:46:50: 197298 IP-Bereiche von /home/schutti/.aMule/ipfilter.dat geladen. 0 fehlerhafte Zeilen wurden ignoriert.
2010-04-25 19:46:50: 0 IP-Bereiche von /home/schutti/.aMule/ipfilter_static.dat geladen. 0 fehlerhafte Zeilen wurden ignoriert.
2010-04-25 19:46:50: IP filter is ready
the ipfilter is working.
I added a IP manually and the IP (a normal server) was deleted from the list.
I removed the line from the ipfilter.dat and the killed server are back.
There must be other reasons for the spam flood at the moment.