That’s a great question, Rene. I’ll pass this to Mark in our call as one of the suggestions I’m passing. As an aisde, there appears to be a workaround, if you are interested and have access to your apache configs.
https://support.wordfence.com/support/articles/1000011134-i-m-getting-errors-that-wordfence-can-t-detect-visitor-ip-addresses-or-i-use-ipv6-on-my-site-and-i
Back up any config files before you change them, of course.
If I get a more definitive answer, I’ll let you know.
tim
Thanks Tim,
but i am using NGINX.
Look at this chart:
http://w3techs.com/technologies/details/ce-ipv6/all/all
IPv6 is used by 4.3% of all the websites.
Thats not much, but this is rising, of course
So 5% of WordPress user are not able to use Wordfence and they will probably not buy any premium key;-)
Rene,
I hate to see anyone not be able to use this plugin. I was using it long before Mark brought me in and my experience has always been positive. I think I told Mark “it saved my butt tons of times” because it has. I noted that Mark as said earlier that IPV6 support is being looked at, but I don’t know what level of priority it has vs the other billion things Mark does 🙂 He and I talk frequently and I’ll make sure he knows that its been requested. I only offered the work around because I found it while digging through our stuff for info.
tim
Hi Rene,
This has been a hot button topic for some time. Some more data:
Google has a chart showing user adoption:
https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption
And this shows the number of autonomous systems growth:
http://www.ipv6actnow.org/info/statistics/
To give you an idea of how it’s growing in the hosting environment.
The reason implementing IPv6 for us is a big deal is because we store IP addresses in your database and an IPv6 address can’t be stored simply as an unsigned integer – or put differently an integer stored in 32 bits of address space that is always greater than zero.
We need to store those addresses using 128 bits or 16 bytes of space for every address. So we need to change our database schema to accommodate this. It’s a big deal both in complexity, performance impact and risk for introducing new bugs – so it’s something I’ve been postponing for a while.
I can’t make you any promises about when we’ll implement this today because I need to do a full analysis on what the change requires and come up with implementation details. But know that it’s in the works and as you can tell from the charts I posted it is inevitable.
Regards,
Mark.
