B.I.S.S. Forums > New gnutella Templist

B.I.S.S. Forums > Bluetack Forums > Global News

Pages: 1, 2

firstaid

Mar 25 2006, 07:43 PM

We are now the proud supporter of the Gnuetella.txt and Gnutella.zip files. Made by Aaron walkhouse.

*New*
Gnutella Templist
---------------------------
Gnutella.zip:
gnutella.zip
---------------------------

So everyone give him a big hand

A little information on the list.

QUOTE

FYI: Categories in effect for today's list are as follows:

759 360share and eTomi clones.txt
4,216 BAD GUID - 5D1CECE8584FF507FF5EE44E3F5A5701 GiFT .txt
9,795 BAD GUID - 9C51E42153D4C94A858F8E8A8391173D Morpheus.txt
377,431 BearShare Pro scams and worms.new.txt
72,398 BearShare Pro scams and worms.repeats.txt
309,485 Fakes.new.txt
413,506 Fakes.repeats.txt
4,416 SPAM - 0-8K bytes - How2 [open with notepad.avi].new.TXT
3,350 SPAM - 0-8K bytes - How2 [open with notepad.avi].repeats.txt
748,232 SPAM - 15,872, 70-170K bytes - EFreeClub.repeats.txt
166,457 SPAM - 22 bytes - Empty zip files.new.txt
27,730 SPAM - 22 bytes - Empty zip files.repeats.txt
12,689 SPAM - Various.new.TXT
3,377 SPAM - Various.repeats.txt
36,356 TROJAN - 233472 bytes - Dropper.Generic.DZD.new.txt
80,245 TROJAN - 50-80K bytes - ISTbar.new.txt
8,106 TROJAN - 50-80K bytes - ISTbar.repeats.txt
486 TROJAN - 61-62K bytes - Mainpean StarDialer.new.txt
1,045 TROJAN - 61-62K bytes - Mainpean StarDialer.repeats.txt
5,466 TROJAN - 783843 bytes - Crypt.B.new.txt
4,250 TROJAN - 783843 bytes - Crypt.B.repeats.txt
3,636 TROJAN - 81,964 bytes - WinVBIE Toolbar.new.txt
2,327 TROJAN - 81,964 bytes - WinVBIE Toolbar.repeats.txt
2,212 WORM - 123897 bytes - GEDZAC VBS-Israfel.new.txt
1,478 WORM - 123897 bytes - GEDZAC VBS-Israfel.repeats.txt
1,178 WORM - 178861 bytes - IRC.Backdoor.SdBot.LFI.new.txt
2,106 WORM - 178861 bytes - IRC.Backdoor.SdBot.LFI.repeats.txt
13,581 WORM - 202477 bytes - Generic.FX!CME-24.new.txt
23,968 WORM - 535082 bytes - W32.Alcra.D.new.txt
4,176 WORM - 535082 bytes - W32.Alcra.D.repeats.txt
709 WORM - 643767 bytes - VB.FL.new.txt
34 WORM - 643767 bytes - VB.FL.repeats.txt
26,841 WORM - 71,070 bytes - W32.Alcra.C.new.txt
10,308 WORM - 71,070 bytes - W32.Alcra.C.repeats.txt
238,798 WORM - 872159 bytes - VB.CC.new.txt
167,774 WORM - 872159 bytes - VB.CC.repeats.txt

That's 36 lists in 20 categories. I had 18 categories last week but
found a worm and a trojan since then.

You won't find many of these in the usual lists, and none of them are
ranges. A few of the smaller lists might raise an eyebrow but they tend
to shield us from the most careless folks who don't check recent
downloads before sharing them. They tend to fall off the lists quickly.

The BearShare Pro list is a grab bag of worms, zombied spam and some of
the nastiest trojans out there, as well as a few pointlessly hacked
versions of BearShare. I'm looking at doing the same for LimeWire soon
because the results seem to round up everything the other lists missed.

The bad GUID lists cover the two known outbreaks of servents widely
released with the non-unique GUIDs shown here. It is as much to protect
them as it is us since all push requests to any of them inevitably hits
the whole group on line at the time, flooding each of them while
resulting in a virtual DDOS of "Not Shared" replies back to us. I have
warned the developers of both servents as soon as the outbreaks started
and it looks like both were contained reasonably quickly.

The scattered local IP addresses will serve to protect some people
inside the big LANs without interfering with normal home users.
Only those local IP addresses that wouldn't normally be assigned by a
home router are included. Naturally, the local addresses would only come
into effect if the user deliberately disables BOTH the IANA Private and
Non-LAN lists_AND_happens_to_be_on_one_of_the_huge_LANs. Everyone else
would be unaffected no matter what they do.

I block the few remaining 360share and eTomi clones of Shareaza and
LimeWire "just because". (Fortunately that scam seems to be fading
fast) ;]

Set it up fast. These lists work best when fresh from the oven. ;D

firstaid

Moore

Mar 25 2006, 07:51 PM

Thanks Aaron

5cardstud

Mar 25 2006, 09:44 PM

QUOTE (firstaid @ Mar 26 2006, 01:43 AM)

So everyone give him a big hand

marklusty

Mar 26 2006, 02:57 AM

wow,very nice stuff,

great work to all involved,
mark

Aaron.Walkhouse

Mar 26 2006, 08:35 AM

For those of you with BearShare, the 90,480 rules of the above list are also a part of
The BearShare Fullsize Hostiles List, which is currently at 357,171 rules.

fe_de_7

Mar 27 2006, 04:19 AM

Good job Aaron!

regharding

Apr 9 2006, 12:23 PM

Alright Aaron, can you tell me why my routers ip number is in the gnutella.txt please?

Aaron.Walkhouse

Apr 10 2006, 12:34 AM

I could, but first you have to tell me which IP address it is.

ares_rulz

Apr 10 2006, 01:05 AM

When I use this list, my internet stops working. Nothing is being blocked in PG2 though. I dont think my IP is in the list. Whats wrong?

regharding

Apr 10 2006, 06:55 AM

QUOTE (Aaron.Walkhouse @ Apr 10 2006, 06:34 AM)

I could, but first you have to tell me which IP address it is.

The IP number was here but someone has moved it to some questions area what I'm going to have to hunt down. Found it.
(http://www.bluetack.co.uk/forums/index.php?showtopic=13782)

I also sent you a message from this site with the IP number, havent you checked your messages.

The IP number of my router that is blocked by the list is 10.0.0.138-10.0.0.138.

regharding

Apr 10 2006, 09:52 AM

I booted up the pc one day about a week ago, with PG2 autorunning in the background with all the lists I use active, one list was gnutella.txt templist. I was unable to connect to the internet and I couldn't browse my routers IP and check/change the settings.
I have just put this list back into PG2 and I can't even connect to this fine website, I have had to turn off the list to accsess this site.
This is the only list from this brilliant website that I have ever had trouble with and have had to disable to browse this site or the internet.

shadow666

Apr 10 2006, 10:02 AM

import gnutella.txt into blocklist manger with the other lists. doesnt work very good importing it straight into pg2 list manger if thats how you did it

firstaid

Apr 10 2006, 10:06 AM

yes, if importing the gnutella list into blm you will need to have merge adjacent checked in options / general and use listview unchecked as well.

firstaid

regharding

Apr 10 2006, 10:28 AM

I don't use blm I only use Pg2, all I do is right click and copy a shortcut wich is http://www.bluetack.co.uk/config/gnutella.txt then I go to Pg2 and use the list manager and the add button to add the the link to the lists what are now being blocked, each list is seperate. No importing or anything like that.

ares_rulz

Apr 10 2006, 12:53 PM

You having the same exact problem as me then... nothing showes as being blocking, but theres just ni internet activity.

Aaron.Walkhouse

Apr 10 2006, 02:03 PM

What's the IP address of your router, ares_rulz? I also need the make and
model number so I can check the manufacturer for defaults and add them to
my intermediate filters.

In the meantime, just remove that IP address from your PW file.

regharding

Apr 23 2006, 05:36 PM

My default gateway on SpeedTouch 536 router is 10.0.0.138

Alright Aaron,

I had a browse of the http://www.bluetack.co.uk/config/gnutella.txt
and found this:
"Spam, fakes and worms on gnutella:10.0.0.138-10.0.0.138"
Approx line 142. Thats my routers IP number from ntl: ISP UK and it's still in the list.
I was under the impression from you that you was actually going to remove this IP range from the gnutella.txt and/or gnutella.zip. At the moment I am still being blocked when using your two lists.

It's still in the list Aaron even after me tipping you off about this IP number. Will you be removing it like you said you would please? and if so when please? I like to use the G2 network and sometimes the G1 network via Sheraza, at the moment my routers IP number being blocked in the gnutella lists, is making my life and internet experience very distressing, difficult and dangerous. If the list is up and running from boot I can't even connect to the internet or browse my router to alter settings. I don't really feel like perm allowing anything in PeerGuardian2 thats being blocked.

I'm not "on your case" Aaron but, I can't belive I'm still getting blocked by your gnutella list(s).

Yours looking forward to being able to browse the internet and use your gnutella blocklists very soon and at the same time.
Nice1.

Aaron.Walkhouse

Apr 23 2006, 07:43 PM

That entry has been gone for almost a couple of weeks now. Clear your
browser cache and "Temporary Internet Files" folder even if you don't use IE
to look at the list.

Besides, it's just a text file. Delete that line if you can't get the update.

Aaron.Walkhouse

Apr 24 2006, 04:23 AM

Speaking of updates, here's another gnutella.txt. ;]

regharding

Apr 24 2006, 08:53 AM

Aaron Walkhouse,

Well done Aaron I am now able to use your fine gnutella.txt blocklist with my SpeedTouch 536 router, your list now rocks.
Woo Woo.
Nice1.

Aaron.Walkhouse

Apr 25 2006, 04:11 AM

This time it took 38 files to get 82622 rules. Some of the older worms were dying off
but new ones kept the count from dropping as much as we hoped.

CODE

340 360share and eTomi clones.txt
4,188 BAD GUID - 5D1CECE8584FF507FF5EE44E3F5A5701 GiFT .txt
196 BAD GUID - 9C51E42153D4C94A858F8E8A8391173D Morpheus.new.txt
28 BAD GUID - 9C51E42153D4C94A858F8E8A8391173D Morpheus.repeats.txt
116,490 BearShare and LimeWire Pro scams and worms.repeats.txt
609,713 Fakes.new.txt
93,630 Fakes.repeats.txt
7,262 SPAM - 0-8K bytes - How2 [open with notepad.avi].new.txt
1,892 SPAM - 0-8K bytes - How2 [open with notepad.avi].repeats.txt
621,676 SPAM - 15,872, 70-170K bytes - EFreeClub.repeats.txt
30,716 SPAM - 22 bytes - Empty zip files.repeats.txt
9,035 SPAM - Various.new.TXT
3,446 SPAM - Various.repeats.txt
110,425 TROJAN - 233472 bytes - Dropper.Generic.DZD.new.txt
2,712 TROJAN - 233472 bytes - Dropper.Generic.DZD.repeats.txt
133,184 TROJAN - 50-80K bytes - ISTbar.new.txt
20,818 TROJAN - 50-80K bytes - ISTbar.repeats.txt
1,098 TROJAN - 61-62K bytes - Mainpean StarDialer.new.txt
512 TROJAN - 61-62K bytes - Mainpean StarDialer.repeats.txt
6,156 TROJAN - 783843 bytes - Crypt.B.new.txt
1,898 TROJAN - 783843 bytes - Crypt.B.repeats.txt
2,674 TROJAN - 81,964 bytes - WinVBIE Toolbar.new.txt
984 TROJAN - 81,964 bytes - WinVBIE Toolbar.repeats.txt
1,580 WORM - 123897 bytes - GEDZAC VBS-Israfel.new.txt
644 WORM - 123897 bytes - GEDZAC VBS-Israfel.repeats.txt
1,600 WORM - 178861 bytes - IRC.Backdoor.SdBot.LFI.new.txt
380 WORM - 178861 bytes - IRC.Backdoor.SdBot.LFI.repeats.txt
236,546 WORM - 202477 bytes - Generic.FX!CME-24.new.txt
1,312 WORM - 202477 bytes - Generic.FX!CME-24.repeats.txt
37,179 WORM - 535082 bytes - W32.Alcra.D.new.txt
7,322 WORM - 535082 bytes - W32.Alcra.D.repeats.txt
421 WORM - 643767 bytes - VB.FL.new.txt
128 WORM - 643767 bytes - VB.FL.repeats.txt
28,778 WORM - 71,070 bytes - W32.Alcra.C.new.txt
9,738 WORM - 71,070 bytes - W32.Alcra.C.repeats.txt
262,839 WORM - 872159 bytes - VB.CC.new.txt
103,616 WORM - 872159 bytes - VB.CC.repeats.txt

Total Lines Read: 82622
Lines Ignored: 0
Lines Added: 0
Dupes Merged: 0
Merged Ranges: 0
Split Ranges: 0
Sources Processed: 1
Deny IP Count: 83,078 (out of 4,294,967,296 IP's or 0.00193%)
Total IP Count: 83,078 (out of 4,294,967,296 IP's or 0.00193% !!)
Process Time: 8.32 seconds.
Download Time: 0.00 seconds.
Total Time: 8.32 seconds.
Rules Added: 82622
Rules Per Second: 9928.74
Error Count: 0

If you want the SHA1 signatures found in the above searches and your software can
use them, download gnutella.SHA1.txt and give it a try. The tiny list of 4677
signatures will protect you almost as well as gnutella.txt alone. Let us know how to
do it for your software and we'll spread the word for you.

Sabu75

May 29 2006, 01:54 AM

wow aron : thank you very much. very good work.

i used it now awhile with the other lists together and i was surprised, how much hits i get while using emule.

how do you get this list together?

Have a nice Day

Sabu

Aaron.Walkhouse

May 29 2006, 03:45 AM

QUOTE (Sabu75 @ May 29 2006, 12:54 AM)

Last time it took 21 searches of the gnutella network, as described above.

Odds are high anybody sharing this crap is using other P2P networks, so it's no surprise
you see plenty of hits in eMule.

Sabu75

Feb 24 2007, 02:34 AM

any news for an update?

Sabu

Aaron.Walkhouse

Feb 24 2007, 10:12 PM

QUOTE (Sabu75 @ Feb 24 2007, 01:34 AM)

any news for an update?

Sabu

No problem. I've been streamlining the process in preparation of making it a daily thing.

…Nope, forget it. They must have lost my account and password because I can't log in to upload an update.

I'd attach it to a post but that option has apparently been disabled in the forums.
If you still want it, PM me with an email address. It's ready to go.

firstaid

Feb 24 2007, 11:58 PM

pm me Aaron.Walkhouse and we can get things set up again, think things got a little weird when the site went down last.

firstaid

Aaron.Walkhouse

Feb 25 2007, 01:12 AM

I figured that was why. ;]

shadow666

May 21 2007, 10:17 AM

can't get gnutella blocklist getting this error in blm while trying to get it

Getting 'ProtoWall (PeerGuardian/SafePeer)' Blocklist file: http://www.bluetack.co.uk/config/gnutella.txt
:: URL Unavailable : http://www.bluetack.co.uk/config/gnutella.txt
:: Error in DecodeFormat: File Line#: 1, Line Contents:
:: http://www.bluetack.co.uk/config/gnutella.txt is empty.
:: Processing cancelled.

Aaron.Walkhouse

May 21 2007, 11:18 AM

Hmmm… It's definitely there. I just checked and the version I uploaded yesterday is still good.

Perhaps you should try the gnutella.zip file anyway. It's only 1.2 megs instead of 7.3.

http://www.bluetack.co.uk/config/gnutella.zip

Nope. There's definitely a problem on the server. The zip is there, but downloads do not work.

Aaron.Walkhouse

May 21 2007, 11:32 AM

Oh well. Must be a server problem. Use mine instead:

http://www3.telus.net/Aaron_Walkhouse/gnutella.zip

firstaid

May 21 2007, 11:40 AM

I think due to bw issues we stopped supporting the gnutella.txt, but I just uploaded the .zip now again and its working fine for me. Lets keep an eye on it, just incase a cron is removing it when it should not be.

firstaid

Aaron.Walkhouse

May 21 2007, 01:20 PM

Yes, I agree we should use the zip file from now on.
The uncompressed text file is always going to be very large.

Sabu75

May 22 2007, 01:00 AM

hm, i believe the gnutella zip is going to be too huge now. could it possible that its not the gnutella templist?
see below what i got .... blm freaks out!

Getting 'ProtoWall (PeerGuardian, SafePeer, P2PHazard)' Blocklist file: http://www.bluetack.co.uk/config/gnutella.zip
Decoding and Adding...
Converting List...
Splitting List...
Loading data... 248891 lines.
248890 rules added.

thats definetely too much, normally the gnutella templist was around 85000 rules right?

after sorting out ,thats happens:

Sorting Array...
Merging overlapping ranges...
:: Deny rules have the priority.
:: Merging of Adjacent rules enabled.
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1, Line Contents:
:: Error in PostProcArray: File Line#: 1025, Line Contents:
:: Error in PostProcArray: File Line#: 1537, Line Contents:
:: Error in PostProcArray: File Line#: 1537, Line Contents:
:: Error in PostProcArray: File Line#: 1537, Line Contents:
:: Error in PostProcArray: File Line#: 1537, Line Contents:
:: Error in PostProcArray: File Line#: 1537, Line Contents:
:: Error in PostProcArray: File Line#: 1537, Line Contents:
:: Error in PostProcArray: File Line#: 2177, Line Contents:
:: Error in PostProcArray: File Line#: 2177, Line Contents:
:: Error in PostProcArray: File Line#: 2945, Line Contents:
:: Error in PostProcArray: File Line#: 3201, Line Contents:
:: Error in PostProcArray: File Line#: 3201, Line Contents:
:: Error in PostProcArray: File Line#: 4353, Line Contents:
:: Error in PostProcArray: File Line#: 4353, Line Contents:
:: Error in PostProcArray: File Line#: 4353, Line Contents:
:: Error in PostProcArray: File Line#: 4353, Line Contents:
:: Error in PostProcArray: File Line#: 5377, Line Contents:
:: Error in PostProcArray: File Line#: 5377, Line Contents:
:: Error in PostProcArray: File Line#: 5377, Line Contents:
:: Error in PostProcArray: File Line#: 5377, Line Contents:
:: Error in PostProcArray: File Line#: 6273, Line Contents:
:: Error in PostProcArray: File Line#: 6273, Line Contents:
:: Error in PostProcArray: File Line#: 6401, Line Contents:
:: Error in PostProcArray: File Line#: 6785, Line Contents:
:: Error in PostProcArray: File Line#: 6913, Line Contents:
:: Error in PostProcArray: File Line#: 6913, Line Contents:
:: Error in PostProcArray: File Line#: 7553, Line Contents:
:: Error in PostProcArray: File Line#: 7553, Line Contents:
:: Error in PostProcArray: File Line#: 9089, Line Contents:
:: Error in PostProcArray: File Line#: 9473, Line Contents:
:: Error in PostProcArray: File Line#: 9473, Line Contents:
:: Error in PostProcArray: File Line#: 9601, Line Contents:
:: Error in PostProcArray: File Line#: 9857, Line Contents:
:: Error in PostProcArray: File Line#: 9857, Line Contents:
:: Error in PostProcArray: File Line#: 9985, Line Contents:
:: Error in PostProcArray: File Line#: 9985, Line Contents:
:: Error in PostProcArray: File Line#: 10497, Line Contents:
:: Error in PostProcArray: File Line#: 10753, Line Contents:
:: Error in PostProcArray: File Line#: 10753, Line Contents:
:: Error in PostProcArray: File Line#: 10881, Line Contents:
:: Error in PostProcArray: File Line#: 11265, Line Contents:
:: Error in PostProcArray: File Line#: 11265, Line Contents:
:: Error in PostProcArray: File Line#: 11265, Line Contents:
:: Error in PostProcArray: File Line#: 11521, Line Contents:
:: Error in PostProcArray: File Line#: 11521, Line Contents:
:: Error in PostProcArray: File Line#: 11905, Line Contents:
:: Error in PostProcArray: File Line#: 12033, Line Contents:
:: Error in PostProcArray: File Line#: 12033, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 12545, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13569, Line Contents:
:: Error in PostProcArray: File Line#: 13697, Line Contents:
:: Error in PostProcArray: File Line#: 13697, Line Contents:
:: Error in PostProcArray: File Line#: 13697, Line Contents:
:: Error in PostProcArray: File Line#: 13697, Line Contents:
:: Error in PostProcArray: File Line#: 13697, Line Contents:
:: Error in PostProcArray: File Line#: 15617, Line Contents:
:: Error in PostProcArray: File Line#: 15617, Line Contents:
:: Error in PostProcArray: File Line#: 15617, Line Contents:
:: Error in PostProcArray: File Line#: 15617, Line Contents:
:: Error in PostProcArray: File Line#: 15617, Line Contents:
:: Error in PostProcArray: File Line#: 15617, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16257, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16513, Line Contents:
:: Error in PostProcArray: File Line#: 16897, Line Contents:
:: Error in PostProcArray: File Line#: 16897, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 17921, Line Contents:
:: Error in PostProcArray: File Line#: 18049, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 18945, Line Contents:
:: Error in PostProcArray: File Line#: 19073, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19201, Line Contents:
:: Error in PostProcArray: File Line#: 19457, Line Contents:
:: Error in PostProcArray: File Line#: 19457, Line Contents:
:: Error in PostProcArray: File Line#: 19585, Line Contents:
:: Error in PostProcArray: File Line#: 19585, Line Contents:
:: Error in PostProcArray: File Line#: 19585, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 19841, Line Contents:
:: Error in PostProcArray: File Line#: 20609, Line Contents:
:: Error in PostProcArray: File Line#: 20609, Line Contents:
:: Error in PostProcArray: File Line#: 20609, Line Contents:
:: Error in PostProcArray: File Line#: 22145, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 22401, Line Contents:
:: Error in PostProcArray: File Line#: 25217, Line Contents:
:: Error in PostProcArray: File Line#: 27009, Line Contents:
:: Error in PostProcArray: File Line#: 27137, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27265, Line Contents:
:: Error in PostProcArray: File Line#: 27649, Line Contents:
:: Error in PostProcArray: File Line#: 28289, Line Contents:
:: Error in PostProcArray: File Line#: 28289, Line Contents:
:: Error in PostProcArray: File Line#: 30849, Line Contents:
:: Error in PostProcArray: File Line#: 30849, Line Contents:
:: Error in PostProcArray: File Line#: 30849, Line Contents:
:: Error in PostProcArray: File Line#: 30849, Line Contents:
:: Error in PostProcArray: File Line#: 30849, Line Contents:
:: Error in PostProcArray: File Line#: 30977, Line Contents:
:: Error in PostProcArray: File Line#: 30977, Line Contents:
:: Error in PostProcArray: File Line#: 30977, Line Contents:
:: Error in PostProcArray: File Line#: 30977, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31233, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31361, Line Contents:
:: Error in PostProcArray: File Line#: 31617, Line Contents:
:: Error in PostProcArray: File Line#: 31873, Line Contents:
:: Error in PostProcArray: File Line#: 32001, Line Contents:
:: Error in PostProcArray: File Line#: 32385, Line Contents:
:: Error in PostProcArray: File Line#: 32385, Line Contents:
:: Error in PostProcArray: File Line#: 32385, Line Contents:
:: Error in PostProcArray: File Line#: 32385, Line Contents:
:: Error in PostProcArray: File Line#: 32385, Line Contents:
:: Error in PostProcArray: File Line#: 32385, Line Contents:
:: Error in PostProcArray: File Line#: 32897, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33025, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33665, Line Contents:
:: Error in PostProcArray: File Line#: 33921, Line Contents:
:: Error in PostProcArray: File Line#: 34561, Line Contents:
:: Error in PostProcArray: File Line#: 34561, Line Contents:
:: Error in PostProcArray: File Line#: 35073, Line Contents:
:: Error in PostProcArray: File Line#: 35073, Line Contents:
:: Error in PostProcArray: File Line#: 35073, Line Contents:
:: Error in PostProcArray: File Line#: 35073, Line Contents:
:: Error in PostProcArray: File Line#: 35073, Line Contents:
:: Error in PostProcArray: File Line#: 35073, Line Contents:
:: Error in PostProcArray: File Line#: 35073, Line Contents:
:: Error in PostProcArray: File Line#: 35201, Line Contents:
:: Error in PostProcArray: File Line#: 35201, Line Contents:

and so on, then i had to cancel blm.

any ideas?

Sabu

Aaron.Walkhouse

May 22 2007, 07:58 AM

That's the right file. It averages between 150-200,000 lines but can run higher when new spammers show up.

You probably ran into your array limit set in the registry at HKCU\Software\Bluetack\Blocklist Manager. The lack of data in the Line Contents: part of the error message is a pretty good hint of that. Set MaxArray to 524288 and see what happens.

Sabu75

May 22 2007, 10:51 AM

thanks aron, but sadly it doesnt do the trick, same error messages while blm wants to merge the lists.

i use the last beta 2.75 just for the info.

cheers

Sabu

Aaron.Walkhouse

May 22 2007, 11:34 AM

Odd. 2.7.5 was never a problem for me.
Try 2.7.7 too, in case there's a difference.

I just tried it and there were no errors at all.

Are you running low on free RAM?
What other lists were you merging it with?

Sabu75

May 22 2007, 11:48 AM

i use 2.7.7 already.

i have 512 mb but haven´t any problems ( listview is turned off!).

all lists except master exclusion and the spider list plus some special extra lists ( korea, china, all akamai ranges,lacnic , some inclusions + etc.)

EDIT:

done some testing, even disable all other list and only use gnutella.zip . of couse having flushed before and redownload it ........... doesnt work. got the same error messages .

lol. very strange !

Sabu

hackattack142

May 22 2007, 04:25 PM

Could you go into the registry, go to "HKEY_CURRENT_USER\Software\Bluetack\Blocklist Manager" and tell me the value of MaxArray.

That behavior is similar to that when you run out of Array space.

Sabu75

May 22 2007, 11:00 PM

its 524288 what aron suggested to put into it, before it was something like 48450 or so if i remember correctly.

Sabu

talotin

May 22 2007, 11:30 PM

Hi guys.

I have the same error as Sabu. I have to disable the gnutella list to merge everything else normally. If I include the gnutella list, it goes haywire ~73% or so.

I'm running blm 2.77
My comp has 2gb of ram
That registry tweak didn't fix the problem for me either.

The MaxArray was 327680 before I changed it to 524288.

Here's my normal output for the lists I download (without gnutella):

CODE

        BLM Version: 2.7.7 Public Beta
      Finished Time: 5/23/2007 1:28:45 AM
   Total Lines Read: 287588
      Lines Ignored: 17
        Lines Added: 5
       Dupes Merged: 1767
      Merged Ranges: 37000
       Split Ranges: 5
  Sources Processed: 18
      Deny IP Count: 2,890,141,787  (out of 4,294,967,296 IP's or 67.29136%)
    Permit IP Count: 271,056,900  (out of 4,294,967,296 IP's or 6.31104%)
     Total IP Count: 3,161,198,687  (out of 4,294,967,296 IP's or 73.60239% !!)
       Process Time: 73.30 seconds.
      Download Time: 0.22 seconds.
         Total Time: 73.52 seconds.
        Rules Added: 248810
   Rules Per Second: 3394.52
        Error Count: 0

hackattack142

May 23 2007, 05:54 AM

I currently have BLM set it at 409600. I have not tested it above this value and this should be more than enough to handle all the lists. Try this value. It still sounds like a memory issue to me.

Also, make sure you are not using a modified Sources.txt. Use the Import Manager to get the extra lists.

Sabu75

May 23 2007, 06:54 AM

okay, i´ve set it back to what youve said. and strangely enough i can load the list now.

what in the hell? but together with the other lists it doesnt work.

i give up now. i don´t have any memory issue.

i use the gnutella templist now in pw and all the others in my p2g programm.

Sabu

talotin

May 23 2007, 05:24 PM

That still didn't work for me.

I can't load the gnutella list, whether it's by itself or with any other lists. When I loaded gnutella by itself, it started giving the PostProcArray error at ~13%
Sometime in the next week or so I'll run a scan on my memory, just in case.
I'll post back here afterwards.

hackattack142

May 23 2007, 06:23 PM

I am experiencing the problem aswell and am trying to find the cause.

Aaron.Walkhouse

May 24 2007, 10:49 AM

Odd. I'll set aside that copy for further experimentation and generate a new one.
This next one should be a wee bit larger.

Aaron.Walkhouse

May 24 2007, 01:55 PM

Okay, a new one is uploaded. I don't know when the admins will update the download folder,
but the new file is dated today (the 24th) and is exactly 1,227,887 bytes long.

hackattack142

May 24 2007, 04:11 PM

Issue found. It appears the list was recently changed and the comments removed to save space (which is fine) and BLM did not have good handling of Null comments.

For anyone using the Beta, a refreshed build is available.

Aaron.Walkhouse

May 25 2007, 01:01 AM

Oho! I'm glad it wasn't because of the size of the list. ;]

EDIT
uploaded the gnutella list to the correct folder. Let me know when you have a new one.

HvT

pj48

Sep 9 2007, 02:58 AM

Can't load the gnutella list either, internet will not connect or it will connect at very slow speeds with it in pg2. I will try Aaron's gnutella temp list and see if that works shortly.

I have a gnutella list from late 2006 that works fine in pg2.

Aaron.Walkhouse

Sep 9 2007, 08:24 AM

Are you saying PG2 slows down, that your P2P is slow, or that all of the internet connection slows down?
Or are you just saying it takes longer for your P2P to get it's first host connections?
There are so many ways to interpret what you said

What's the difference between "the gnutella list" and "Aaron's gnutella temp list"?

Get rid of any old list. The whole idea is to have the latest version.
Old lists are worse than useless because they block the wrong places.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.