Hi Thomas,
I feel this is documented enough. The QUICKSTART guide, chapter III,
invites to read README files in the sql/ dir of the tarball if using
RDBMS. README.mysql and equivalents say:
* src_host => ip_src (CHAR(15) NOT NULL, see README.IPv6)
- or (INT(4) UNSIGNED NOT NULL, if sql_num_hosts: true)
- or (INT(16) UNSIGNED NOT NULL, if sql_num_hosts: true and --enable-ipv6)
* dst_host => ip_dst (CHAR(15) NOT NULL, see README.IPv6)
- or (INT(4) UNSIGNED NOT NULL, if sql_num_hosts: true)
- or (INT(16) UNSIGNED NOT NULL, if sql_num_hosts: true and --enable-ipv6)
Then README.IPv6 documents precisely the same kind of change to the
SQL schema that you did by yourself.
Cheers,
Paolo
On Thu, Oct 16, 2014 at 02:39:27AM +0100, Thomas Jepp wrote:
> Hi all,
>
> I couldn't see any bug tracker so I'm sending this to the list -
> please correct me if I'm wrong.
>
> I've been using pmacctd to store bandwidth usage information in a
> MySQL database using the "pmacct-create-db_v1.mysql" schema.
>
> The "ip_src" and "ip_dst" fields in the example schema is only 15
> chars. This means that v6 addresses get truncated. I've increased
> these fields in my own database to 39 chars and the problem is solved.
>
> It'd be great if the example SQL should be corrected to account for this.
>
> --
> Thomas Jepp
> pma...@tomjepp.co.uk
>
> _______________________________________________
> pmacct-discussion mailing list
> http://www.pmacct.net/#mailinglists
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
