@anonymous-piwik-user opened this Issue on April 19th 2009

In the visit.php file of Piwik_Tracker, use the function below instead of ip2long to get the right number .

function myip2long($ip){
if (is_numeric($ip)){
return sprintf("%u", floatval($ip));
} else {
return sprintf("%u", floatval(ip2long($ip)));
}
}

@robocoder commented on April 26th 2009 Contributor

Attachment:
0.2.35.php

@robocoder commented on May 16th 2009 Contributor

Attachment:
668.diffs

@anonymous-piwik-user commented on April 19th 2009

Replying to rjmacy:

In the visit.php file of Piwik_Tracker, use the function below instead of ip2long to get the right number .

function myip2long($ip){
if (is_numeric($ip)){
return sprintf("%u", floatval($ip));
} else {
return sprintf("%u", floatval(ip2long($ip)));
}
}

@anonymous-piwik-user commented on April 19th 2009

The new myip2long() function works on both 32 and 64 bit systems.

@mattab commented on April 20th 2009 Owner

what's the issue with the php core one?
what's the consequences in piwik?

@anonymous-piwik-user commented on April 21st 2009

Matt, thanks for getting back to me. I've been using Piwik for a few weeks now and love it. I hope to produce a Plugin and write an article about it soon.
The issue is that on a 32 bit system, the ip2long() function overflows the signed int when we deal with an IP address with a high first octet. Consequently, a negative number gets placed in the DB in the location_ip field. One solution is to tell installers to use only 64 bit systems. Another solution is to implement a replacementment function for ip2long().

I suggest doing something like
function myip2long($ip){ $test = ip2long($ip);
if ( $test < 0)
{if (is_numeric($ip)){ return sprintf("%u", floatval($ip)); } else { return sprintf("%u", floatval(ip2long($ip))); } }
else return $test;}

@mattab commented on April 21st 2009 Owner

as long as long2ip is bijective (ie. negative int give back the same IP) this is not an issue is it?

@anonymous-piwik-user commented on April 24th 2009

It is an issue because the number in the database is negative and the SQL function inet_ntoa() reports a NULL value when used on it. The location_ip column should be an unsigned int and we should be using inet_aton() to store the data there.
I am writing a big plugin and had to perform extra modifications to the Piwik code to get everything to work.

@robocoder commented on April 24th 2009 Contributor

Matt's point is that the issue isn't impacting Piwik because PHP's long2ip() is able to handle the negative int -- arising from the fact that PHP doesn't have an unsigned int type.

However, I'm not opposed to the proposed change if it make its easier for plugin authors and/or when accessing the database directly. However, changing location_ip to "int unsigned" isn't exactly non-trivial. For example, the following SQL replaces negative numbers with 0:

ALTER TABLE piwik_log_visit CHANGE location_ip location_ip INT UNSIGNED;

Assuming the aforementioned roadblock is overcome, the ip2long() wrapper can probably be simplified as:

function myip2long($ip) {
    return sprintf("%u", ip2long($ip));
}
@anonymous-piwik-user commented on April 24th 2009

I agree that this change is not simple, but currently I have to store the IP address in a new colomn in dotted decimal form in order to get data from MySQL into other systems. This means I have two columns that contain basically the same data, but one is in unusable form. My manager needs the data in a usable form.

I'm introducing ten programmers to Piwik and we plan on making it our company's standard for this type of data collection. As the user base of Piwik grows I think we would want to be able to pull SQL reports out of the DB directly and not have to rely on the front end for everything. BTW, you guys are doing a great job!

@robocoder commented on April 25th 2009 Contributor

Ok, working in our favor is that location_ip is a BIGINT. We'll want to keep this as a bigint so we can store ipv6 addresses (someday).

Perhaps something like the following?

UPDATE log_visit SET location_ip=location_ip+POW(2,32) WHERE location_ip < 0;
ALTER TABLE log_visit CHANGE location_ip location_ip BIGINT UNSIGNED;
@robocoder commented on April 25th 2009 Contributor

And for consistency, the change should also be applied to caller_ip.

@robocoder commented on May 16th 2009 Contributor

matt: the update script has to be renamed, but otherwise I believe this patch is good to go. Please review.

Before update:

+-------------+
| location_ip |
+-------------+
|          -1 | 
| -1062731519 | 
|  2130706433 | 
+-------------+

After update:

+-------------+
| location_ip |
+-------------+
|  4294967295 | 
|  3232235777 | 
|  2130706433 | 
+-------------+

+------------------------+
| inet_ntoa(location_ip) |
+------------------------+
| 255.255.255.255        | 
| 192.168.1.1            | 
| 127.0.0.1              | 
+------------------------+
@anonymous-piwik-user commented on May 16th 2009

It works great. Thanks.

@robocoder commented on May 16th 2009 Contributor

BTW the -1 was dummy data that I inserted for testing.

@mattab commented on May 18th 2009 Owner

vipsoft, getDottedIp could be renamed getIpString.

Will the PHP call: long2ip( $visitor['location_ip'] ) - used in plugins/Live/Visitor.php - still return the original IP as expected?

@robocoder commented on May 18th 2009 Contributor

Ok. I'll rename it.

Yup, long2ip() works as expected, eg long2ip(-1) and long2ip(4294967295) both return 255.255.255.255.

@mattab commented on May 18th 2009 Owner

lgtm

("looks good to me" that is sometimes used for successful patch reviews)

@robocoder commented on May 18th 2009 Contributor

(In [1140]) fixes #668 - store location_ip as unsigned

@robocoder commented on August 2nd 2009 Contributor

(In [1350]) refs #668 - fix inconsistency between fresh install and upgrade path

This Issue was closed on August 2nd 2009
Powered by GitHub Issue Mirror