Bit-Twist 1.0 Released

A year has passed since the last release and Bit-Twist 1.0 is finally out!

Bit-Twist is packaged for BSD, Linux and Windows platform but the source files are now the same across all platforms! Development on Windows platform is done with combination of Eclipse IDE for C/C++ Developers and Cygwin environment.

If you use bittwiste program, please note that comma (,) is now used as separator for all replace options. Previously, slash (/) was used instead.

There are 2 new feature requests added into bittwiste in this release. In particular, few users have asked if they can maintain traffic session at link-layer. For example, to replace MAC address 00:08:55:64:65:6a with 00:00:aa:bb:cc:dd you can now do this:

Bit-Twist 0.80 Released

Several memory allocation errors in bittwiste have been addressed in this release.

Thanks to Uwe Andersen, Kevin Springle and Reading Wesley for reporting this problem. Thanks also to Rene Simon for his ideas on improving bittwist's performance.

There are also 2 new feature requests added into bittwiste in this release. You can now save packets from within a specific timeframe. For example, you can save any packets that have a timestamp value between October 22, 2006 21:47:35 and October 24, 2006 13:16:05 by using:

Bit-Twist 0.74 Released

Added 2 feature requests into bittwiste.

You can now modify IP address field without breaking the session. For example, you can replace host IP address 192.168.0.1 that appears either in source or destination IP address field with 192.168.1.1 by using:

Bit-Twist 0.73 Released

This release introduces the first addition of a feature request in the project; to allow bittwiste to replace a specific port number with a new port number. For example, with the following command, you can replace the destination port field for all TCP packets from port 80 to 8080:

Bit-Twist 0.72 for Windows

The first Bit-Twist release for Microsoft Windows XP/2000 is now available for download. This release comes only with the bittwist and bittwiste program.

The bittwistb program has not been ported successfully as of this release. Please let me know if you think this program may be useful to you. Otherwise, it will probably never find its way into the Windows system.

OpenBSD Patch Released

A patch for Bit-Twist 0.72 has been released to solve a compilation issue on OpenBSD system. You may download the patch from the download section and refer to the installation guide for instructions on how to apply the patch. Thanks to C.S. Lee for reporting this problem.

Examples

The examples section is now available. Simple and interesting practical examples will be added from time to time into this section to get you started with Bit-Twist. For now, check out the first example to learn how ARP cache poisoning is possible with Bit-Twist!

Bit-Twist 0.72 has been released earlier on April 29, 2006 and thanks to Wesley Shields who is kind enough to maintain the FreeBSD port for Bit-Twist.

Bit-Twist 0.7 Released

Bittwiste can now automatically recalculate ICMP, TCP, or UDP checksum for user payload which covers the header and data for these packets. Given this support, you can use 2 bytes of zeros, e.g. 0000, for the checksum field in your payload which is supplied to the -X flag in the bittwiste program.

Some updates are also visible in the bridge program, bittwistb.

Bit-Twist 0.6 Released

You can now bridge 2 or more LAN segments with bittwistb; a newly added program in this release. The option to save a specific range of packets using bittwiste is also working now.

Bridge in Upcoming Release

Ethernet bridging support to bridge 2 LAN segments will be among the main features in Bit-Twist 0.6, which is scheduled for release on March 31, 2006.

Bit-Twist 0.5 Released

Many improvements have been added to the trace file editor. You get more control over various fields of Ethernet, ARP, IP, ICMP, TCP, and UDP header. Addition of support for user payload allows you to utilize an existing packet header and append your own data to the packet. It is also possible for you to save a specific range of packets from the original trace file into another trace file.