Hi Jeremy please read below. > On 26 Jul 2016, at 11:50, Jeremy Ashton <[email protected]> wrote: > > I am looking to implement a packet processing pipeline that first > aggregates a number of interfaces, generates ipfix flows and outputs > to multiple aggregated queues (cento-ids).
Please provide: - (rough) number on ingress interfaces - expected ingress total rate > Afterwards, I am looking > to have (cento?) read from one of the aggregated queues and apply > packet shunting before passing it off to n2disk. Cento already does shunting on aggregated queue (for feeding n2disk). > The other aggregated > queues would be used to feed other analysis tools via load balanced > output queues. Cento already does load balancing, but not after aggregation (it distribute to multiple egress queues traffic coming from each -i). Please note you can specify an interface pair with -i ethX,ethY if you have two directions from two ingress interfaces (i.e. from a TAP). Is it ok for your use case? Alfredo > I am currently using zbalance_ipc for the initial “capture” and > distribution. But it seems cento is the way it should be done. From > what I can tell, I would require two new features to be added: > > 1) Adding the ability to create multiple aggregated queues as output > from cento. (https://github.com/ntop/nProbe/issues/86). > > 2) Add the ability to bypass flow generation in cento and use it just > for aggregation and distribution of packets. > > I am not sure if this is the correct approach. I wonder if you might > offer some advice as to the best approach for doing this. > > Thanks! > _______________________________________________ > Ntop-misc mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop-misc
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
