warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

Cannot Use Custom Block Lists #171

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Manually Add custom Block List from computer hard drive, formatted the
same way as for peerguardian in p2p format.
2. Go to any blocked site listed ^& watch it permit blocked traffic as allowed

What is the expected output? What do you see instead?

The expected output is that peerblock will successfully block IP's within
ranges specified in the IP blocklist. However, it permits all traffic, all
the time, unless it is using a list from the internet -- but who wants to
use one of those lists that block out the sites & services we need? Hence
CUSTOM block list.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?

32-bit/64-bit Vista/Server 08 and/or Windows 7/Server 08 R2 -- doesn't matter. 

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

Original issue reported on code.google.com by mrdra...@gmail.com on 23 Oct 2009 at 6:40

Attachments:

GoogleCodeExporter commented 9 years ago
I can't reproduce this - creating a custom blocklist via notepad and then 
adding it
to PeerBlock via the List Manager seems to work just fine.  Could you please 
post
your peerblock.conf and the .p2p custom file you're having trouble getting 
PeerBlock
to accept?

Original comment by peerbloc...@gmail.com on 30 Oct 2009 at 2:19

GoogleCodeExporter commented 9 years ago
Sorry that you cannot reproduce this, but I can, and the couple of people I 
know that
use peerblock are having the same issue. We do not have the issue when 
selecting any
of the default lists - it works fine. It is only when we are specifically using 
ONLY
a custom list & no default lists do we have this issue. Peerblock will accept 
and use
a custom list only after a fresh installation of it. After that, its a pain in 
the
(you know what) to get it to work again. On Vista/Server 08 I have managed to 
get it
to work by clicking enable/disable a few times (which is a hassle & is 
mentioned by
another user in the bugtrack), but on Windows 7/Server 08 R2, after I shutdown
peerblock & restart it, or reboot, the custom list will simply not work, 
everytime,
no matter how many times I click enable/disable. However, on Win7/Svr08r2 if I 
add
one of the default lists & then remove that default list, then the custom list 
will
work again (sometimes I have to click enable/disable), until I shutdown 
peerblock or
reboot the system. Also, It doesn't matter if the custom list is in the same
directory as peerblock or in another location.

I have attached the peerblock.conf & custom .p2p file. This .p2p file contains 
all
the default lists peerblock uses & more, but with exclusions removed so I can 
view
certain sites that these default & public lists normally block. This is why I 
have to
use custom lists & cannot be satisfied with the lists provided.

Original comment by mrdra...@gmail.com on 30 Oct 2009 at 3:29

Attachments:

GoogleCodeExporter commented 9 years ago
Interesting - I just performed a simple "add a custom Block list with one IP 
address"
test to attempt a repro; will try more in-depth testing later.

As far as removing certain IP addresses from the predefined lists, you are 
aware that
we support custom Allow lists too, right?  That is the intended usage of them; 
you
can use default automatically-updated lists, but still "whitelist" certain IP 
ranges.
 This is how the "Allow Permanently" right-click menu option works, by adding the
selected IP address to the lists\permallow.p2b allow-list.

Either way, we'll look into the "custom blocklists not working" issue and see 
what we
can see.  Thanks for reporting the problem!

Original comment by peerbloc...@gmail.com on 30 Oct 2009 at 3:36

GoogleCodeExporter commented 9 years ago
I just updated peerblock to the latest r202 on my Vista/Server08 machines (note 
these
are x64 that I have been speaking of for this platform, the Win7 is x86, but 
Server08
R2 is x64 as well), and tried the enable/disable trick for my custom list, and 
now I
cannot get it to work at all. I have sat here for the past 10 minutes with a 
known
government site with its IP range in the list, clicking enable/disable each time
before reloading the page, and only 1 time did peerblock catch it and listed it 
as
blocked, but it still allowed the site to pass through and load. It only did 
that one
time, every other time I clicked refresh it still allowed the site to pass, and 
did
not list it as blocked. The site is 
http://www.epa.gov/region4/waste/npl/index.htm 
It is also included in one (dont know which one - LOL) of the 4 default (P2P,
Spyware, Advertising, Education) lists that peerblock features for selection. 
After
selecting these 4 default selected lists in the list manager and updating them, 
it
catches this site, and blocks it fine. Remove the selections of these 4 default 
lists
& click "add" to browse to my custom list, and now the custom list works and 
blocks
this specific site mentioned I use to test peerblock with. However, after I 
close
peerblock, and open it again, the custom list is no longer functioning.

Original comment by mrdra...@gmail.com on 30 Oct 2009 at 3:55

GoogleCodeExporter commented 9 years ago
Also, I meant to add that I am aware of the feature to allow IP's within 
peerblock,
but it is a hassle to go to every single site I need to allow on every machine 
just
to do this, which is why I have a custom list I can just drop on every computer 
and
be done with it.

Original comment by mrdra...@gmail.com on 30 Oct 2009 at 4:08

GoogleCodeExporter commented 9 years ago
I would like to report, that with the newest beta v.r223 custom block lists are
working like a charm. No need for any tricks! Custom lists are implemented
immediately on program load & after restart, and appears to be catching all 
blocked
IP's within ranges. 

Original comment by mrdra...@gmail.com on 28 Nov 2009 at 9:59

GoogleCodeExporter commented 9 years ago
Sounds like this issue was fixed along with one of the other fixes that'd gone 
in in
the November timeframe, so marking it as Fixed in order to close it.  If this is
incorrect, or if the bug reappears, please comment and we can always reopen it.

Original comment by peerbloc...@gmail.com on 20 Jan 2010 at 6:40