Re: [pmacct-discussion] json output of iface

2014-02-21 Thread Stig Thormodsrud
Yes, the ports, vlan and tos are also jacked-up for me: TAG, SRC_MAC, DST_MAC, VLAN, SRC_IP,DST_IP, SRC_PORT, DST_PORT, PROTOCOL, TOS, PACKETS, FLOWS, BYTES 7, dc:9f:db:28:ff:aa, 24:a4:3c:3d:51:e2, 0,10.1.0.91, 10.2.0.195, 1935, 55750,tcp, 0, 957956, 1

Re: [pmacct-discussion] json output of iface

2014-02-21 Thread Stig Thormodsrud
Sure I can try that. I'm wondering if it's a big endian issue? My platform is MIPS64. stig On Fri, Feb 21, 2014 at 11:44 AM, Paolo Lucente wrote: > Hi Stig, > > I tried to reproduce the issue with no joy, ie. all works good. I > suspect this might be something architecture specific - what CP

Re: [pmacct-discussion] json output of iface

2014-02-21 Thread Paolo Lucente
Hi Stig, I tried to reproduce the issue with no joy, ie. all works good. I suspect this might be something architecture specific - what CPU is this? Thing is input/output interface fields are u_int32_t and using 'i' would get us in trouble reading from NetFlow/sFlow exporters where interfaces ha

[pmacct-discussion] json output of iface

2014-02-20 Thread Stig Thormodsrud
Hi Paolo, I've been experimenting with the new json output - nice addition. One thing I ran into was that the iface value was wrong. For example here's the csv output compared with the json output: root@ubnt-SJ:/etc/pmacct# pmacct -p /tmp/uacctd-e.pipe -s -T bytes -O csv TAG,IN_IFACE,OUT_IFACE,