Closed GoogleCodeExporter closed 8 years ago
Not a bug.
See these links to allow IPs
http://www.peerblock.com/userguide/how_to_use/htu-allowingconnections
http://www.peerblock.com/userguide/how_to_use/htu-creatinglists
Original comment by nightstalkerz
on 29 Mar 2010 at 7:56
ok. so this is kinda pointless when i have to reinstall it everytime. is it
just me
having to reinstall it everytime?
Original comment by statebow...@gmail.com
on 30 Mar 2010 at 6:28
You don't have to reinstall everytime you get blocked.
Did you read the links I gave?
You may need to allow multiple IPs because the Xfire and Second Life servers
may have
multiple IPs.
Original comment by nightstalkerz
on 30 Mar 2010 at 7:57
For the two services you mentioned Xfire and Second Life, there are even two
pre-made
lists of IP addresses used by those servers - head on over to
http://iblocklist.com/lists.php and check out their "Xfire" and "Linden Lab"
lists,
and add them to your List Manager as lists of type "Allow" as per
http://www.peerblock.com/userguide/how_to_use/htu-usinglists. That should let
you
connect to their servers without issue.
Worst-case scenario you shouldn't need to uninstall/reinstall PeerBlock - even
if you
can't identify the relevant IP addresses you should be able to just Exit or
Disable
PeerBlock, and it will stop blocking IP addresses until you start / enable it
again.
The links to our online User Guide that nightstalkerz provided should explain
how to
allow individual IPs that are causing problems. If you run into further
problems
with games/services for which pre-made lists do not exist, you'll need to
right-click
on the blocked IP addresses in the PeerBlock main window, and
Temporarily/Permanently
Allow them. You can also create your own custom allow-lists; the iblocklist.com
Search page can help you easily find IP address ranges that belong to certain
companies to make this easier. (We can - and should - make this easier to do
within
the PeerBlock interface itself, and hopefully will in a future release, but
we're not
there yet.)
Marking this bug as "Invalid" to close it, since PeerBlock is working as it
should.
Original comment by peerbloc...@gmail.com
on 30 Mar 2010 at 1:11
Original issue reported on code.google.com by
statebow...@gmail.com
on 28 Mar 2010 at 2:03