arpwatch (2.1a15-4) unstable; urgency=medium This update introduces some behavior changes to arpwatch: * -N option now only stop reporting bogons as described in the man page. Previously this option caused arpwatch to process bogons as normal packets instead. To restore the old behavior, add `-a` to your options. * Starting arpwatch on an unconfigured interface will no longer implicitly watch everything (0/0). Instead you have to configure the subnet you want to watch explicitly by using the `-n` option (add `-n 0/0` to retain the old behavior). Furthermore the -R option is dropped in this release, as it did not work in all cases and could only be used when running arpwatch as root (not recommended) Instead the arpwatch service is now restarted by systemd after an unclean exit by default (which also works together with dropping privileges). -- Lukas Schwaighofer Fri, 12 May 2017 20:49:53 +0200 arpwatch (2.1a15-3) experimental; urgency=low Starting with version 2.1a15-3, arpwatch ships with systemd unit files. The change requires manual steps after the upgrade. The `/etc/arpwatch.conf` file, which can be used to specify different configuration options for multiple interface, is replaced by individual configuration files for each interface. If you have configured arpwatch using `/etc/arpwatch.conf` file, you need to convert this to the new format. See `/etc/arpwatch/README` for details. After the upgrade, arpwatch will not be started by default. You need to specify the interface(s) to run on, see `/etc/default/arpwatch` for instructions. If your database file in `/var/lib/arpwatch/` is called `arp.dat` you need to rename it to `IFACE.dat` (where IFACE is the name of the interface you configured arpwatch to run on) if you want to keep your current arp database. Also, make sure to drop the `-i` option from ARGS if you were using that to specify the interface. -- Lukas Schwaighofer Thu, 23 Mar 2017 21:05:48 +0100