ABC
ABC
I consider implementing _'standalone mode'_ of operation for the module, where you don't need to insert iptables rules into chains, but module will 'just catch' all the traffic (like `ETH_P_ALL`)...
I'm already in process of implementing utility to parse flows statistics exported via `/proc/net/stat/ipt_netflow_flows`. Flows stat interface is already moved from `debugfs` to `proc` as part of implementing this feature...
I think we need to use benefit of being kernel module and provide connection/packet/skb data which is visible only from inside of kernel and not visible by passive packet observation...
To help distinguish the traffic is may be useful to provide some statistical information about connections content. Such as: 1. Record first _N_ data bytes of a connection. 2. Entropy...
I consider implementing TCP export mode for IPFIX protocol. This may require major rewrite of exporting logic, may be not, depends.
https://sourceforge.net/p/ipt-netflow/bugs-requests-patches/77/
- Debian New Maintainers' Guide https://www.debian.org/doc/manuals/maint-guide/index.en.html - Debian packaging http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html - DKMS article http://www.linuxjournal.com/article/6896 - https://wiki.kubuntu.org/Kernel/Dev/DKMSPackaging - https://help.ubuntu.com/community/Kernel/DkmsDriverPackage - http://basilevsthecat.blogspot.ru/2011/11/how-to-build-dkms-debian-package.html ##### Links for other projects for inspiration: - https://drbd.linbit.com/users-guide/s-build-deb.html -...
> The openSUSE Build Service is the public instance of the Open Build Service (OBS) used for development of the openSUSE distribution and to offer packages from same source for...