Sniffer10G bypasses the kernel and the kernel's regular networking mechanisms. This is achieved directly by applications that use the SNF API or in this case, libpcap over SNF API. The snf0 is not a real network interface that is listed under ifconfig, but it's an interface that libpcap can recognize. However, only *our* libpcap recognizes it (or a libpcap compiled with SNF API support). If your application uses shared libraries, it may be sufficient to
LD_LIBRARY_PATH=/usr/local/opt/snf/lib ./<application_exe>
for the application to pick up our libpcap.so. If not, compile the application with --with-pcap=/usr/local/opt/snf/lib.
Then, confirm that the application can correctly pick up Sniffer through the SNF API.
As an example, please read: How do I run Linux tcpdump with the Sniffer10G software?
Note: An Ethernet port remains usable as a regular ethernet device until (and if ever) it is opened for sniffing (Sniffer mode). So if only ever snf0 is opened, the myri1 ether device remains usable. Similarly, as soon as snf0 is closed for sniffing, the myri0 ethernet device is again usable if it has previously been brought up with ifconfig. Both myri0/myri1 can be configured (or not) as ethernet devices at anytime -- the only difference is that Sniffer will usurp the ethernet traffic from the regular driver path when snf0 (or snf1) is opened for Sniffing (either through pcap or the API).