Hi Aaron, I don't really understand what it is you are trying to do. It is possible to get just parts of a packet by using Tee (to copy the packet), and then combinations of Truncate and Strip to get just the part you are interested in... but I am suspicious that this is not actually what you want.
If you want the packets to be dumped to a text file, you should look at the ToIPSummaryDump element, which you can use to print out all of the fields you listed below. Beyond that, if you want to do something custom where you store certain parts of specific packets, you probably need to write your own element to do this. There are many elements checked in already though, so you should be able to look at them for guidance. Cliff On Tue, Sep 22, 2009 at 7:49 PM, 科进 舒 <[email protected]> wrote: > > hi, > Nowadays I am trying to handle netflows with click.I think it's really > useful and helpful when I caputure or classify the packets but when I want > to handle the packets more precisely,it's hard to do that. > As I see from the web,click stores packets in a single flat array of > bytes.And now I want to parse the packets and then store every part of > packets separately. > Now my question is I can parse the packets from the array,but I don't > know how to store them,particularly,the data.How to store and handle the > binary data? > Besides,is there a packet structure that I can use to get every part > of the packet easily,like src ip,dst ip,src port,dst port,protocol and so on > ? > Best wishes and waiting for your responses! > Thank you! > > Sincerely yours, > > Aaron > > > ___________________________________________________________ > 好玩贺卡等你发，邮箱贺卡全新上线！ > http://card.mail.cn.yahoo.com/ > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
