On Sun, Jun 21, 2015 at 08:02:40PM +0300, Vadim Kochan wrote: > On Sat, Jun 20, 2015 at 01:10:45AM +0200, Daniel Borkmann wrote: > > On 06/20/2015 12:25 AM, Vadim Kochan wrote: > > ... > > >>Ok, how would all of this tie together with flex and bison that we > > >>use for trafgen as parser generator? It looks on a first glance that > > >>this design would be outside of that scope? > > . > > >You mean that this is out of scope of this thread which was related to > > >mz ? If so, then yes ... may be extend the trafgen's cfg script to > > >describe the protocols and then add the cmd line interface based on this > > >extension ? Or do you think that extending cfg script syntax is not good > > >or may be problematic ? > > > > > >Well, I think may be I can do some "just for fun" implementation, just > > >for demonstration ... > > > > As a start, if you're interested, I think it would be great if you have > > some cycles to look into: > > http://thread.gmane.org/gmane.linux.network.netsniff-ng/799 > > I.e. the idea would be to have a _textual_ replacement initially and then > > push the config through the lexer/parser. > > > > Anyway, back to the topic, as it started out with mz. ;) > > > > I do quite like the interactive mode of mz and it's cmdline syntax is > > fine with me too. mz's implementation rather hacky and uneasy to maintain. > > trafgen so far has a very low level language on how to define packets. > > > > I'm happy to entertain the idea to add an mz-like _interactive_ mode > > that is libreadline-based with more or less similar feature set. I'm > > also good if we add a similar direct _cmdline_ usage possibility. Think > > of it as kind a /clean/ merge of mz which is in staging, into trafgen, > > together with the (f.e. performance) benefits of having direct packet > > socket access. > > > > Thus, we'd end up having the ability of cmdline, config, and interactive > > mode in one traffic generator with different levels of granularity. > > > > Thanks, > > Daniel > > Not sure if it is necessary to use libnet by trafgen as it is used by mz > to generate packets ? It will add the new dependency, but seems it can > simplify generation of the proto packets. > > Regards,
Well, anyway I am trying to implement basic cmdline mz-like proto generation API with few layered protocols: eth, ip, udp for trafgen utility. If I success with this I will share the patch series (I will try to better split it for easier review). Regards, -- You received this message because you are subscribed to the Google Groups "netsniff-ng" group. To unsubscribe from this group and stop receiving emails from it, send an email to netsniff-ng+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
