Hi Paolo, I would say sflow->netflow translation would be valuable according to my field experience.
Reason: the nature of sflow is sampling the packet and forward the info to backend (i.e. sflow collector) ASAP. This causes at least ten times of SQL rows and thus, more than ten times of data processing complexity. TC -----Original Message----- From: pmacct-discussion [mailto:pmacct-discussion-boun...@pmacct.net] On Behalf Of Paolo Lucente Sent: Thursday, November 27, 2014 8:17 PM To: pmacct-discussion@pmacct.net Subject: Re: [pmacct-discussion] IPFIX -> NetFlow v9 convert Hi Eugene, Translation of protocols and protocol versions is not supported by pmacct. Every now and then somebody asks for it but there has never been enough push to look into it (specifically handle all the corner cases in order to do something proper). Cheers, Paolo On Mon, Nov 24, 2014 at 10:41:34AM +0400, Eugene Prokopiev wrote: > Hi, > > I need to receive IPFIX datagrams from 1.1.1.1 to 2.2.2.2 and > translate them to 3.3.3.3 as NetFlow v9? How to do it with pmacct? > > I tried to see tee plugin description and tee_receivers.lst.example, > but I can't find any solution. > > -- > WBR, > Eugene Prokopiev > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists ==================================================================== 本信件可能包含工研院機密資訊,非指定之收件者,請勿使用或揭露本信件內容,並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient. _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists