On this page we will keep track of things that still need to be done. In addition, we will list the cool things that might be done, given sufficient time, students, volunteers, coffee, etc.
You might also want to check out the static TODO list at http://ffpf.sourceforge.net/general/todo.php, as that contains a bit more detail.
1. Have FFPF accept MAPI filters (see http://www.ist-scampi.org/ for more information on the MAPI)
2. Build a daemon-like front-end, to support MAPI applications out of the box
3. Add udev support
1. FFPF for firewalls, NATs
2. Distributed FFPF
3. FFPF for `normal' packet reception by processes
4. a monitoring GUI for (1) displaying the active state of the kernelspace subsystem
and (2) controlling it. Even a simple control app only for the kernel modules would be useful.
5. Adaptive FFPF: automate the monitoring of the FFPF graph by reacting to prespecified changes in behaviour, e.g. load an eDonkey blocker when that type of traffic is seen.
6. TCP stream reconstruction and cooked stream handling for (among others) more elaborate IDS/IPS solutions.
7. pure userspace FFPF. Mostly for debugging purposes, have userspace FFPF accept packets from iptables or even regular sockets.