In the nfdump-era, the '-N' option would cause all numbers to be printed 'as plain as possible'. Fbitdump, however, expects an additional parameter to '-N', indicating the 'plainLevel'. How this 'plainLevel' actually is supposed to work is nowhere explained in the help. Also, by checking the source of Configuration.cpp, it seems that the 'plainLevel' is related to the various plugins, but not really to the basic field in fbitdump's output.
Concrete example: in a situation where I want to print the protocol number in plain (so '6' instead of 'TCP'), it seems I have to use 'plainLevel' 10. The logic behind this is however nowhere explained.
I've just added detailed informations about -N into man pages of fbitdump (commit 90e08febb11be018ac36f49e52b830303a5f42cc). I hope this will help you to understand how plainLevel works. Thanks for the report.
In the nfdump-era, the '-N' option would cause all numbers to be printed 'as plain as possible'. Fbitdump, however, expects an additional parameter to '-N', indicating the 'plainLevel'. How this 'plainLevel' actually is supposed to work is nowhere explained in the help. Also, by checking the source of Configuration.cpp, it seems that the 'plainLevel' is related to the various plugins, but not really to the basic field in fbitdump's output.
Concrete example: in a situation where I want to print the protocol number in plain (so '6' instead of 'TCP'), it seems I have to use 'plainLevel' 10. The logic behind this is however nowhere explained.