User Tools

Site Tools


pom-ng:features_wishlist

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
pom-ng:features_wishlist [2013/01/06 15:53] 2001:7e8:2221:300:224:8cff:fe0b:7d8epom-ng:features_wishlist [2020/05/26 21:59] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Features wishlist (aka TODO list) ======+====== Features wishlist ======
  
-Here is a list of features that will be implemented sooner or later.+Here is a list of features that were requested by usersDon't hesitate to add your feature wish and/or comment !
  
  
-===== Core ===== +Title Description Comment/Discussion 
-Name Status Target/Released version ^ Description +|Drone input|Create a small drone program able to sniff and send traffic to a central pom-ng instance.|The drone'packet filter could be controlled from pom-ngMultiple drones could connect to a pom-ng input and be handled the same way altogether.| 
-|Statistics|Not started|Target for v0.0.8|Add support for statistics. It should be possible to add any type of counter or gauge.| +|Optional system datastore|Don't make a system datastore mandatory.|This is definitely low prioritySqlite3 is a good default datastore and is available on most systemsIt will probably be implemented if some user requires no datastore at all.| 
-|Improve packet listener|Not started|Undefined|Make packet listener process protocols earlier in the code in case one of the later protocol issues PROTO_STOP.+|DVBv5 API migration|Migrate DVB inputs to the DVBv5 API.|The DVBv5 API might make things more difficult for the user since you have to select as well the delivery system for the input. Low priority for now. Might change if some card only work with DVBv5.| 
-|Improve locking contention|Not started|Undefined|Try to reduce lock contention by using gcc atomic builtin where possible. Clock would be good start.| +|Protocol signature matching|Allow protocols such as TCP to match the next protocols based on a signature.|This is definitely useful for traffic on non standard ports.| 
-|Port to non-x86 arch|Not started|Undefined|Non-x86 arch are not allowed to perform non-aligned access. Proto 802.11 needs special handling for that and the rest of the code needs to be tested.| +|NFS protocol|Create events for NFS requests, including NFSv4 COMPOUND statements.|Example using tshark and awk (doesn't work with NFSv4): http://pastebin.com/ggyVcjV1| 
-|Make system datastore optional|Not started|Undefined|Don't make a system datastore mandatory.| +|Mysql datastore|Implement MySQL support.|Low priority until outputs make more use of datastores.| 
-|Conntrack cleanup|Done|Released in v0.0.7|Cleanup the conntrack code to drop the field_id definitions and handle timeout when no child in the core.| +|Use alloca()|Compile time conditional use of alloca()|Have a macro such as pom_alloca()pom_freea(), pom_strndupa() to enable at compile time the use of alloca().| 
-|Conntrack expectations|Done|Released in v0.0.7|Allow conntracks to match related connections. Useful for protocols such as FTP or VoIP ones to match the additional connections.| +|Rework TCP buffering|Have a better algorithm for TCP queuing and buffering that takes in account tcp window to calculate the buffer size|High priority, this is needed to prevent too much buffering when sniffing docsis and wifi.
- +|TZSP|Code tzsp supportThis include parsing the TZSP protocol as well as an input listening on an UDP port for TZSP packets and an output able to send packets encapsulated in TZSP.|Moderate priority, might be a good protocol to use for the drone.|
- +
-===== Inputs ===== +
-^ Name ^ Status ^ Target/Released version ^ Description ^ +
-|DVBv5 API migration|Not started|Undefined|Migrate DVB inputs to the DVBv5 API.| +
- +
-===== Protocols ===== +
-^ Name ^ Status ^ Target/Released version ^ Description ^ +
-|Signature matching|Not started|Undefined|Allow protocols such as TCP to match the next protocols based on a signature.| +
- +
- +
-===== Datastore ===== +
-^ Name ^ Status ^ Target/Released version ^ Description ^ +
-|Use home path for default datastore|Not started|Undefined|By default, the system datastore points to the current directory to store the db file (./pom-ng.db). It should point to ~/.pom-ng/sys_dstore.db or similar.|+
pom-ng/features_wishlist.1357487592.txt.gz · Last modified: 2020/05/26 21:59 (external edit)