Sander Hoentjen
Mon, 10 Mar 2008 00:20:18 -0700
Hi Paolo, Thank you very much for your response. We ourselves are not IPv6 ready as well, although we are planning on it. It looks like a customer has a router that has IPv6 turned on, and this router is sending the packets. Anyway, I will modify the scheme. Thanks you for this great product. Sander On Sun, 2008-03-09 at 21:37 +0000, Paolo Lucente wrote: > Hi Sander, > > you are absolutely correct about both the cause of the issue and > its solution: manually modifying the SQL schema makes the trick. > This is documented in the sql/README.IPv6 file. It refers to > source and destination IP addresses but indeed the same applies > to the IP protocol - will integrate the document. > > The main reason underlying the shorter fields is to use smaller > strings for people who don't need an IPv6-ready environment - > which, hope you would agree, unfortunately are the wide majority > out there. > > Cheers, > Paolo > > > On Sun, Mar 09, 2008 at 01:08:44PM +0100, Sander Hoentjen wrote: > > Hi, > > > > I get the follow (ip-address changed) in my logs: > > > > ERROR ( in/mysql ): Duplicate entry '55.55.55.55-0-ipv6-c-2008-03-09 > > 00:00:00' for key 1 > > > > Now I thought that it would update my current record instead of trying > > to insert a new one. Can this be because ip_proto is actually ipv6-crypt > > instead of ipv6-c? > > If this is the case maybe the default length of the mysql field should > > be larger (10?) or the names should be truncated in pmacct-data.h? > > If it is a different problem altogether please ignore my comments. > > > > What would be the best way to handle this problem? > > > > Kind regards, > > > > Sander Hoentjen > > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists