By default, fwknopd will now exit if the interface that it is sniffing goes down (patch contributed by Github user 'sgh7'). If this happens, it is expected that the native process monitoring feature in things like systemd or upstart will restart fwknopd. However, if fwknopd is not being monitored by systemd, upstart, or anything else, this behavior can be disabled with the EXIT_AT_INTF_DOWN variable in the fwknopd.conf file. If disabled, fwknopd will try to recover when a downed interface comes back up.
The typical work flow when generating gcov coverage results is: - compile fwknop with coverage support - run the test suite - hack on fwknop - re-run the test suite to see what coverage has been added This work flow is much more common than collecting coverage results for a complete test suite run. Therefore, this commit switches the default behavior in --enable-complete mode (which enables coverage support) to not zero-out coverage counters. A new argument --enable-profile-coverage-init zeros the counters in preparation for a global coverage run.
…n by Jonathan Bennett
…iptables vs. firewalld)
…directly with --afl-pkt-file