What about Analysis, TCP reassembly, etc..

jNetPcap briefly introduced an experimental feature which analyzes (in great detail) various protocols and provides Ip4 and tcp-reassembly services. The feature was deprecated fairly quickly due to some limitations of the existing jNetPcap implementation. Especially at the native level and how information is stored about decoded packet states. The existing memory management of jNetPcap turned out to be inadequate for the task and greatly complicated implementation of this feature.

This is however #1 feature requested and sought after by most users. It is currently being completely rewritten for the next generation of the jNetPcap API in the coming 2.x 1.5 releases. The expected time frame for first release of this feature is in October June of 2011. It will be decoupled from overall jnetpcap dependency and released as a separate module. Of course this module will work in conjunction with jnetpcap, the libpcap java wrapper module.

Analysis, protocol decoding/dissecting and packet scanning will not be separate features anymore. A protocol definition will contain all 3 components listed above as a single and comprehensive protocol definition. Users will be able to work with protocols at whatever level is needed, such as individual message fragments (per packet), reassembled messages or streams, and full analysis such as error or questionable conditions.

The deprecated analysis feature is still available for experimentation purposes both in binary (upto ver 1.3.b0003) and source form. However we can not currently provide support for that feature. There are several known bugs that we do not plan on fixing and we would advise everyone not to use this feature in any production code, until it is properly released in Q3 of 2011 with full support.

Schedule delay to Dec. 2010.

Schedule delay to Dec. 2010. Due to amount of issues that had to be addressed between jNetPcap version 1.3 beta 1 and current release, the schedule for 2.X first development build to be released has slipped to beginning of December of 2010.

I know this is an eagerly awaited upgrade to jNetPcap, but we have a limited amount of resources to do both development on 2.X and 1.X versions at the same time. I believe that we have resolved all of the major issues with 1.X releases (both 1.3 and 1.4.) A new 1.3 beta 4 release is being tested now which will provide major performance increase and lower/more stable memory usage.

If you would like to help, the best way is to support our efforts though a purchase of dedicated support contracts which will allow us to expand and grow.

Sly Technologies, Inc.

Also I wait all protocol

Also I wait all protocol support Smile for the 2.X release.