Flowreplay is dead

I’m officially killing flowreplay as a future feature of tcpreplay. After giving more thought to this problem and where protocols and applications are going, it’s become clear to me that the goals of flowreplay are unobtainable.

The basic issue is that protocols/applications are becoming more state based and even so-called stateless protocols like HTTP have many important stateful characteristics which preclude a tool like flowreplay from properly interacting with a target. Also more and more protocols are including security features which actively prevent successful replay.

Hence, rather then spending a lot of effort building a custom IP stack and some basic protocol decoders to handle protocols like FTP and SIP, I’ve decided my relatively limited free time is better spent elsewhere. With that in mind, I’ll be removing the flowreplay code from the tcpreplay trunk branch. If someone/group of people are interested in continuing development of this project, I’m more then willing to provide hosting and access to the old code, but I’m unlikely to provide much in the way of assistance.