5. System Specific Notes

5.1 GNU/Linux

The client under Linux may not be entirely happy when applied to an aliased interface. You will see some error messages, however things should proceed OK.

5.2 Solaris

No major issues so far. Building the package may become "interesting" if you have not setup your build environment properly.

5.3 FreeBSD

Under FreeBSD the client, sniffer, and the server will make use of two bpf devices. This is because of a limitation in dnet which makes it only single directional for sending packets. Consequently libpcap is used to open another bpf devices for reading. If you run out of bpf devices you will need to compile a kernel with more bpf devices.

5.4 NetBSD

NetBSD ships with a pcap which does not come with pcap_freecode this results in a small mem leak when the client reinitializes its raw network code. To avoid this upgrade to the latest version of pcap and nuke your old pcap library.

See above note for FreeBSD and BPF since it applies to all BSDs.

5.5 OpenBSD

OpenBSD has some brain damage with its bpf structure. Unlike the other BSD flavors it insists on using unsigned instead of signed integers for the number of seconds in its timestamp. This results in some inaccuracy when calculating timeouts. Lobby your OpenBSD developers to stop the brain damage.

See above note for FreeBSD and BPF since it applies to all BSDs.