IPv6 support

[GoogleCodeExporter]

We need to have support for IPv6 blocking.  We currently block IPv4
addresses "masking" themselves via IPv6/Teredo, but have no support for
IPv6 addresses themselves.

One requirement for this will be implementation of the "Next-gen P2B List
Format" (Issue #81), as the P2B v4 spec includes support for them in the
lists themselves.  We'll then need to get some list-authors creating lists
that not only use P2B v4, but that also include IPv6 addresses in them in
the first place.  And then we'll need to fix some of the other IPv6 related
bugs (Issue #62 and Issue #63), and of course implement IPv6 blocking in
PeerBlock.

On the plus side, much of this work has already been done in the PG3
source-code, so we should be able to leverage that to get a jump-start on
things...

Original issue reported on code.google.com by peerbloc...@gmail.com on 4 Nov 2009 at 1:58

[GoogleCodeExporter]

Also rumor has it that IPv4 protocol will run out of ip addresses at end of 
this year. So blocking IPv6 ips is a must.

Original comment by robrpatt...@gmail.com on 4 Aug 2010 at 2:20

[GoogleCodeExporter]

how does one check teredo masked ipv4 in the log or the history?  is this made 
before logging, and the translation to real ipv4 address is behind the log 
scene?

Original comment by dariouch...@gmail.com on 16 Dec 2011 at 8:05

[GoogleCodeExporter]

im honestly surprised ipv6 hasnt already been implemented since it was publicly 
announced in 2008.
I mean implemented sometime between 2008 and around 2012 when it became 
required to be supported by ISP's.
honestly this is a huge hole in peerblock and even worse that a milestone 
hasn't even been set for this issue yet.
I think priority on this issue needs to be changed to Critical.

Original comment by sonic0...@gmail.com on 27 Sep 2012 at 2:29