On Mon, Mar 23, 2015 at 12:12:54PM +0100, Daniel Borkmann wrote: > On 03/23/2015 11:37 AM, Vadim Kochan wrote: > >On Mon, Mar 23, 2015 at 11:25:26AM +0100, Lorenzo Pistone wrote: > ... > >Thats what I got on 3.18 with the same cfg file: > > > >$ trafgen/trafgen -c ~/trafgen.cfg -o wlp3s0 -n 1 > > 4 packets to schedule > > 168 bytes in total > >Running! Hang up with ^C! > > > > > > 0 packets outgoing > > 0 bytes outgoing > > 0 sec, 0 usec on CPU0 (0 packets) > > 0 sec, 0 usec on CPU1 (0 packets) > > 0 sec, 0 usec on CPU2 (0 packets) > > 0 sec, 0 usec on CPU3 (0 packets) > > > >Seems packet was not sent from trafgen ? > > If you increase -n e.g. to 64 or omit -n entirely, does that work? > Looks like a trafgen bug.
Yeah, w/o -n my sniffer on the other side was totally stucked:-) so it helped. -- 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.
