search

warvair / peerblock

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

Need "test working" functionality #8

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Would be nice if we had a routine to let us attempt to Ping a known-blocked
host.  CMD-prompt shows this (e.g. ping to 3.0.0.0) returning a "General
Failure" error as that ICMP connection displays as Blocked in the GUI; we
should be able to look for that error and if we get it we can assume that
PeerBlock is functioning correctly.

Making a button to initiate this test-action might also be a good idea, in
addition to running it automatically at startup.  Many posts to the PG2
forums are asking how they can tell if PG2 is actually blocking anything or
not, this should help minimize those sorts of posts.

Original issue reported on code.google.com by peerbloc...@gmail.com on 13 Jul 2009 at 3:54

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 13 Jul 2009 at 3:55

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 24 Jul 2009 at 5:44

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 17 Aug 2009 at 3:57

GoogleCodeExporter commented 9 years ago 
Not going to get to this one by Release 1.0.

Original comment by peerbloc...@gmail.com on 12 Sep 2009 at 3:24

GoogleCodeExporter commented 9 years ago 
Removing 'After1.0' release-targetting.

Original comment by peerbloc...@gmail.com on 29 Sep 2009 at 3:58

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 30 Sep 2009 at 4:23

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 30 Sep 2009 at 4:32

GoogleCodeExporter commented 9 years ago 
Not going to get to this in the 1.1 timeframe, so marking it as targetted for 
1.2
instead.

Original comment by peerbloc...@gmail.com on 30 Mar 2010 at 4:30