MLG Smokers

<?php
$mem = new Memcached();
$mem->addServer("127.0.0.1", 11211);

$result = $mem->get("blah");

if ($result) {
    echo $result;
} else {
    echo "No matching key found yet. Let's start adding that now!";
    $mem->set("blah", "I am data!  I am held in memcached!") or die("Couldn't save anything to memcached...");
}
?>

Thanks for the quick responses.

-Nick

Hmm,

Cannot find Memcache class

Any ideas why?

https://iotahosting.org/cache_test.php

If you click the link above, it’s a file that changes when held in memcached.

So it seems to be working somewhere.

Wflandon,

Thanks for the quick and professional responses.

I’ll let you know if I discover any further bugs but hopefully it’s smooth sailing from here on out.

Thanks again,

Nick

• This reply was modified 8 years, 5 months ago by MLG Smokers.

Hey wflandon,

thanks for the responses and suggested fixes. I tried the fix and it seems to have worked! But I think all my IPv6 IPs are due for the lowercase treatment, because as soon as that error subsided another one jumped up from the other IP.

Error message
E_WARNING: inet_pton(): Unrecognized address 2C0F:F248:[0000-FFFF]:[0000-FFFF]:[0000-FFFF]:[0000-FFFF]:[0000-FFFF]:[0000-FFFF]

Stack trace
…inet_pton called at /var/www/html/wp-content/plugins/wordfence/lib/
wfUtils.php (256)
…::inet_pton called at /var/www/html/wp-content/plugins/wordfence/lib/
wfLog.php (1323)
… called at /var/www/html/wp-content/plugins/wordfence/lib/
wfActivityReport.php (295)
… called at /var/www/html/wp-content/plugins/wordfence/lib/
wfActivityReport.php (221)
… called at /var/www/html/wp-content/plugins/wordfence/lib/
wfActivityReport.php (181)
… called at /var/www/html/wp-content/plugins/wordfence/lib/
wfActivityReport.php (433)
… called at /var/www/html/wp-content/plugins/wordfence/lib/
wfActivityReport.php (65)
in wfActivityReport::outputDashboardWidget called at ? (?)
in call_user_func called at /var/www/html/wp-admin/includes/template.php (1045)
in do_meta_boxes called at /var/www/html/wp-admin/includes/dashboard.php (227)
in wp_dashboard called at /var/www/html/wp-admin/index.php (136)

I supposed changing all my IPV6 range IPs to lowercase will fix the issue for now.

I also want to report another issue, that I think is semi-related to another IPv6 whitelisting issue.

I attempted to whitelist my server’s own IP “2604:a880:0:1010::e19:8001” (This is the format provided me by my host)

Although I woke up to a notification showing that WordFence had blocked that address from the site.

I cleared it and yet again it was blocked.

It wasn’t until I added the full uncompressed address for my IPv6 address was it able to stay whitelisted.

That address was “2604:a880:0:1010:0:0:e19:8001”

So even though, 2604:a880:0:1010::e19:8001 = 2604:a880:0:1010:0:0:e19:8001, Wordfence would only take the 2nd IPv6. Even though the hits in the live activity show the first address as well.

Is this working as intended or is “::” in Ipv6 just not supported yet by wordfence?

Sorry if I’m unclear, feel free to ask questions I can clear stuff up.

-Nick

Oh, forgot to mention, awesome plugin otherwise ??