[netsniff-ng] Issue 13 in netsniff-ng: Fix TX_RING and implement a non-zero copy mode for kernels that does not support it

[netsn...@googlecode.com]

Status: Accepted
Owner: emmanuel...@googlemail.com
CC: d.borkm...@gmail.com
Labels: Type-Enhancement Priority-High

New issue 13 by d.borkm...@gmail.com: Fix TX_RING and implement a non-zero
copy mode for kernels that does not support it
http://code.google.com/p/netsniff-ng/issues/detail?id=13

Fix TX_RING and implement a non-zero copy mode for kernels that does not
support it. A 'time-correct' replay can be evaluated later after this task
is completed, but the current implementation needs to be stable first.



--
You received this message because you are subscribed to the Google
Groups "netsniff-ng" group.

To post to this group, send email to netsn...@googlegroups.com

To unsubscribe from this group, send email to
netsniff-ng...@googlegroups.com

http://code.google.com/p/netsniff-ng/

[netsn...@googlecode.com]

Comment #1 on issue 13 by emmanuel...@googlemail.com: Fix TX_RING and

implement a non-zero copy mode for kernels that does not support it
http://code.google.com/p/netsniff-ng/issues/detail?id=13

As there is no reason to only implement a TX compatibility mode, users who
don't have PACKET_MMAP at all can use the RX compatibility mode added in
r417

[netsn...@googlecode.com]

Comment #2 on issue 13 by emmanuel...@googlemail.com: Fix TX_RING and

implement a non-zero copy mode for kernels that does not support it
http://code.google.com/p/netsniff-ng/issues/detail?id=13

Added the BPF feature while capturing packet in compatibility mode with r418

[netsn...@googlecode.com]

Comment #3 on issue 13 by emmanuel...@googlemail.com: Fix TX_RING and

implement a non-zero copy mode for kernels that does not support it
http://code.google.com/p/netsniff-ng/issues/detail?id=13

Activated the compatibility mode with r422. Use the -c switch to activate
the compatibility mode