Hi Axel, So far I unsuccessfully tried to reproduce the issue you are reporting on a Linux 2.6/x86 and a Solaris 5.10/sun4u. Which OS and architecture are you running? Maybe this can help guessing whether your inet_ntop() is playing dirty.
I would also appreciate if you can send me privately a brief capture of some sFlow packets (integral, don't forget the "-s 1500") in pcap format together with the expected agentId value. Cheers, Paolo On Mon, Feb 09, 2009 at 04:03:36PM +0100, Axel Apitz wrote: > Hi all, > > we get a lot of Messages of the style: > WARN: expecting flow 'xxxxx' but received 'yyyyy' > collector=0.0.0.0:6343 agent=:::1 > or > WARN: expecting flow 'xxxxx' but received 'yyyyy' > collector=0.0.0.0:6343 agent=::a8:0:0:1 > if compiled it with --enable-ipv6 > > Using the tool "sflowtool | grep -i agent" we see that both routers > use correct value for agentId. > > The both different values for agent= seems random on a new start of > sfacctd and then change not until a restart. > > Some Ideas ? > > Best Regards > Axel Apitz > > PS: the routers and sfacctd communicate over IPv4 > > -- > Axel Apitz > > The unbelievable Machine Company GmbH > Grolmanstr. 40 > 10623 Berlin > Tel.: +49 - 30 - 8892656 - 15 > Fax.: +49 - 30 - 8892656 - 11 > Mobile: +49 - 172 - 7300539 > > http://www.unbelievable-machine.com _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
