Yearly Archives: 2007

05/21/07

Reinventing the wheel…

So I’ve been working on the bits and bytes of SSL a lot lately which has required me to look at the OpenSSL code. Long story short, it’s not the prettiest code I’ve ever seen (by a long shot). But it does have a few gems. This gem is going to one of my new interview questions:


void update(unsigned char *buf) {
  int i;
  for (i = 7; i >= 0; i--) {
    ++buf[i];
    if (buf[i] != 0) break;
  }
}

What does this function do? Do you think this is actually faster then obvious the alternative?

05/20/07

Siig quality sucks

I needed some fast disk space for working on my photos and after some research settled on a pair of Western Digital My Book Premium ES 500GB drives and a Siig eSATA ExpressCard/34 card to connect them to my Mac Book Pro. Continue reading →

05/10/07

mytreo.net hacked or selling email addresses?

So just about every website/company I do business with that requires an email address, I use a unique email address. The email address takes a very simple form: <company name>@synfin.net. The most important rules is that these email address are never used anywhere. So when I noticed I started getting spam to the email address for www.mytreo.net (no I still won’t post it so that spam harvesters can get it, but you can probably guess what it is), it would appear one of two things have happend:

  1. The people behind www.mytreo.net sold my email address to someone and at some point it was given/sold to a spammer
  2. Someone hacked the www.mytreo.net servers and dumped all the email addresses for all the registered users

If someone has a 3rd idea why, I’d love to hear it.

05/1/07

3.0.1 on time!

I’m happy to release that 3.0.1 is not only out, but released on time… pretty amazing if you ask me. :)

Anyways, this release has a number of fixes, most of which were bugs filed by users, so a big thanks to everyone who found a bug and either filed a ticket or emailed the list.

05/01/2007: Version 3.0.1

  • Stop tcpreplay causing OS X WiFi from disassociating (#167)
  • –pnat incorrectly matched all IP addresses (#170)
  • Fix serious memory leak in core common library (#175)
  • Fix tcprewrite –enet-vlan on little endian systems (#174)
  • Bad pcap timestamps were causing excessive delays (#169)
  • Code cleanup (#173)

As always, you can grab the latest tarball from:
http://tcpreplay.synfin.net/trac/wiki/Download

04/22/07

RFC: 802.11 support

So 3.1 development has already started, and based on numerous user requests, one of the first tasks was adding IEEE 802.11 support. If you are someone who is interested in 802.11 support in tcpreplay, please take a few minutes to read this and write a reply. Your feedback is very important!
Continue reading →

04/20/07

3.0.0 final(ly) released

I’m happy to announce that tcpreplay 3.0.0 has officially been released. 3.0 is a complete rewrite of the old 2.x branch which is now officially EOL. During the 3.0 rewrite I had four main goals:

  1. Clean up and reorganize the code to make development easier
  2. Standardize configuration options
  3. Improve performance
  4. Improve the documentation

I’m happy to say that all four of these goals have been met. Performance is noticeably improved and the code is much more maintainable. There is now a standalone library for all packet editing functionality which is used in tcprewrite, tcpbridge and optionally tcpreplay. DLT support is now done via plugins, so adding support for additional DLT’s is much easier. User configuration processing is now handled by GNU Autogen, providing a consistent set of arguments for both command line and configuration files. The man pages/built in help is better and the tcpreplay manual and FAQ have moved to the tcpreplay website wiki.

One unexpected enhancement was adding Windows/Cygwin support. During development I noticed about 20% of tcpreplay downloads were for the Win32 version, so I made an effort to improve portability and add support for Winpcap.

So what about the future? Well 3.1 is already in the planning stages. Feel free to look at the open tickets and leave comments for anything you’d prefer to see take care of sooner rather then later.

Most of all, I’d love to hear any success or failure stories people have with 3.0. Knowing what features people like helps me prioritize other similar features for the future.