[Tutorial] How to block harmful IP ranges with P2PFire

**whateveritakes** · 17.01.10, 21:42

quick question, i downloaded the ipfilter.dat, and it looks like it's working fine. do i really need the *.p2p inside the p2pfire dir to make it better? so just 1 ipfilter.dat file will do the p2p protection job, won't it?

regards, and thanks so much, anon, you opened my eyes... and it just feel a bit weird, cause i don't use toilet ducks to wipe my eyes.

**anon** · 17.01.10, 21:43

Originally Posted by whateveritakes

do i really need the *.p2p inside the p2pfire dir to make it better?

No. More than a single blocklist is overkill.

regards, and thanks so much, anon, you opened my eyes... and it just feel a bit weird, cause i don't use toilet ducks to wipe my eyes.

What's up with you thinking I'm a rubber duck?

**whateveritakes** · 21.01.10, 18:00

not a rubber duck, [ame="http://en.wikipedia.org/wiki/Toilet_Duck"]Toilet Duck[/ame] is a brand

LOL

**irony** · 22.07.10, 04:50

oops double post, I fail

### EDIT: original post

I've got the program running fine, but I cannot surf the web while it is running. I'm assuming P2PFire is blocking something that's causing this to happen, but I can't figure out what!

**anon** · 22.07.10, 18:58

Originally Posted by irony

I'm assuming P2PFire is blocking something that's causing this to happen, but I can't figure out what!

That's what the log window is there for...

**Renk** · 25.07.10, 13:28

Originally Posted by anon

No. More than a single blocklist is overkill.

I which measure ? what exactly is overkilled ? Some ipfilter are complementary each others; moreover, (if I well understand) P2PFire built its own "optimized ipfilter" (the union of the files ipfilter.dat, block.p2P and guarding.p2P, minus white.p2P, with redundancies eliminated) and works with it. So the only overkill risk I see is that the "optimized ipfilter" might filter too many good IPs, but this can happen with a sole ipfilter as well as well (e.g. a sole ipfilter.dat, with a sole line: 000.000.000.000-255.255.255.255).

**anon** · 25.07.10, 19:41

Originally Posted by Renk

I which measure ? what exactly is overkilled ?

I meant more in an optimization sense, since ipfilter files tend to be anywhere in the 10+MB region nowadays (with the notable exception of the light but working IpFilterX). Adding two or more of those together without cleaning up would end with a huge file - although that shouldn't be a problem if you let P2PFire optimize the lists as you mentioned. (Other IP blocking programs don't have that built-in!)

However, I think the results would be more or less the same as when using a "paranoid" ipfilter, so it may not be worth the hassle.

**kirkedir** · 20.12.10, 18:57

Hello fellas,

I cant use p2pfire because i use windows 7 . I installed peerblock . Is it ok or p2pfire is better ? What do you recommend me ?

Thanks

**anon** · 20.12.10, 18:58

Originally Posted by kirkedir

I cant use p2pfire because i use windows 7 . I installed peerblock . Is it ok or p2pfire is better ? What do you recommend me ?

PeerBlock works on Windows 7. P2PFire doesn't. Logic kind of says PeerBlock is better.

**anon** · 08.05.11, 23:44

Yes, I just checked myself and indeed P2PFire doesn't work on Windows 7, as expected.

I updated the list of ipfilter.dat addresses. Two were dead and one changed its URL.

**super666** · 26.07.12, 23:40

hey guys i have tried to install this and all i get is it reports error and asks mwe to restart the application P2PFire.sys load: ERROR, CODE: DRV_ERROR_STARTING (-6)