SNF_DEBUG_MASK=0x3
Users can ensure that a Sniffer10G-aware Libpcap library is linked to the application by setting SNF_DEBUG_MASK=0x3 in the environment when opening the Sniffer10G device snfX. For example,
$ SNF_DEBUG_MASK=0x3 SNF_FLAGS=0x2 /path/to/tcpdump -i snf3
Setting this SNF_DEBUG_MASK variable causes the SNF API to output memory mapping information when the Sniffer10G device (snfX) is opened by Libpcap. If no information is dumped to the screen, it is likely that your application is linked against a version of libpcap that is not SNF aware. Monitor myri_counters to verify that traffic is in fact being received.
Similarly, the SNF_DEBUG_MASK=0x3 can be used to ensure that a Sniffer10G application is being correctly linked to the Sniffer10G library. E.g.,
$ SNF_DEBUG_MASK=3 SNF_RSS_FLAGS=0x1 ./snf_simple_recv snf.0.0 P (userset) SNF_PORTNUM = 0 snf.0.0 P (default) SNF_NUM_RINGS = 1 (0x1) snf.0.0 P (default) SNF_RSS_FLAGS = 1 (0x1) snf.0.0 P (default) SNF_DATARING_SIZE = 268435456 (0x10000000) (256.0 MiB) snf.0.0 P (default) SNF_DESCRING_SIZE = 67108864 (0x4000000) (64.0 MiB) snf.0.0 P (default) SNF_FLAGS = 0 snf.0.0 P (environ) SNF_DEBUG_MASK = 3 (0x3) snf.0.0 P (default) SNF_DEBUG_FILENAME = stderr ...
For more information on SNF_NUM_RINGS, SNF_DATARING_SIZE, and SNF_DESCRING_SIZE, please read: What is the maximum number of rings supported by Sniffer10G?
For more information on SNF_RSS_FLAGS, please read: What RSS hashing is available in Sniffer10G?
For more information on SNF_FLAGS, please read: Can Sniffer10G v2 aggregate or merge ports?
For more information on the numbering of snfX and how this numbering corresponds to the installed adapters within a host, please read: Which interface is snf0, snf1, etc?