thanks for your detailed thoughts. I will use the chance to explain
our strategy in a little bit more detail.
The overall objective is to make OpenDPI more valuable. We plan to do
this in multiple ways: pattern updates, new protocols and features,
and external interfaces and tools to "really" use OpenDPI.
We will update detection patterns for existing protocols frequently.
ipoque's commercial DPI engine and OpenDPI will be kept synchronized
New Protocols and Features:
... will follow. A main point on our agenda is IPv6 support. For IPv6
we currently disentangle dependencies from proprietary code. I will
provide a list of protocols we are working on (hopefully in October).
Another feature we are working on is the support of asymmetric
traffic. This has the same status like IPv6.
In general I see a lot of potential for volunteers here.
Interfaces and Tools:
The most useful thing would be an iptables integration. This would
allow the use of its powerful traffic shaping and firewall
functionalities. The "live pcap processing" is a great idea, but we
are lacking the resources to implement this, so it would be great if
this is done by a volunteer too.
Here is our preliminary roadmap:
- IPv6 support
- asymmetric traffic
- iptables wrapper
In general, we invite everybody to contribute to this project.
Therefore we have activated the code repository and the issue tracker.