It doesn't seem to mean anything of it's own for tcpdump
, so in this case it's equivalent to a single n
.
For some networking tools it used to be/is that a single n
disabled conversion that (might have) required network traffic (e.g. host name lookups) while two disabled every such conversion (i.e. post numbers are usually converted by looking in /etc/services
). I don't remember if that was also the case for tcpdump
, but else it might just be a habbit to use two n
's.
But the only way to be sure in any particular case, is to ask whoever wrote the command why they use a double n
.