IPWATCHD.CONF(5)
π IPWATCHD.CONF(5) π
okay bestie, gather round, because this is the ipwatchd.conf page from the File Formats Manual β yeah, section 5, the config-file girlies β and I'm about to make it make sense. π
β¨ NAME β¨
ipwatchd.conf β the configuration file of the IPwatchD daemon, aka the lil text file that tells your daemon how to behave π¦
πΈ SYNOPSIS πΈ
/etc/ipwatchd.conf
π DESCRIPTION π
so the IPwatchD daemon reads its config from whatever file you point at with -c on the command line. that's it, that's the hookup. the file is just keyword-argument pairs, one per line, no drama. lines that start with a # sign? ignored. empty lines? also ignored. we love a low-maintenance file π
here are all the possible keywords and what they actually mean, no gatekeeping:
iface_configurationβ sets the config mode for your network interfaces. in automatic mode, IPwatchD detects all your network interfaces by itself and slaps passive protection mode on them, no input needed. in manual mode, it's on the administrator to hand over the list of interfaces and their protection modes. accepted values areautomaticormanual. default isautomatic.ifaceβ names a network interface and its protection mode. this value only gets accepted in manual configuration mode, so don't try it in automatic, she won't answer. in active protection mode, IPwatchD protects your host from IP takeover by answering the Gratuitous ARP requests coming from the conflicting system. in passive protection mode, it just records the info about the IP conflict through the standard syslog interface β no clapback, just receipts. the interface you name must exist, and the protection mode must bepassiveoractive. periodt.defend_intervalβ the minimum interval between defensive ARPs, in seconds. accepted value is a number from0to600. default is0.user_scriptβ the absolute path to a user-defined script that IPwatchD calls when an IP conflict happens. if no script is specified, IPwatchD just generates a syslog event for every single IP conflict. the file you specify must exist. there is no default value β it's giving choose-your-own-adventure π«Άsyslog_facilityβ the facility used for logging. accepted values areauth,authpriv,cron,daemon,kern,lpr,mail,news,syslog,user,uucp,local0,local1,local2,local3,local4,local5,local6andlocal7. default value isdaemon.
π EXAMPLES π
automatic configuration mode, the no-thoughts-just-vibes option:
iface_configuration automatic
defend_interval 10
user_script /usr/sbin/ipwatchd-script
syslog_facility daemon
manual configuration mode, for when you're the main character who wants control:
iface_configuration manual
iface eth0 active
iface eth0:0 passive
defend_interval 10
user_script /usr/sbin/ipwatchd-script
syslog_facility daemon
π AUTHOR π
this manual page was written by Jaroslav Imrich <jariq@jariq.sk> β iconic, honestly π
π¦ SEE ALSO π¦
ipwatchd(8), ipwatchd-script(1)
and that's the whole page, bestie!! this was IPWATCHD.CONF(5) from the File Formats Manual β go forth and configure responsibly, you absolute legend βπ
π¦ where this page comes from
- debian bookworm: ipwatchd 1.2.1-1+b2
- debian trixie: ipwatchd 1.3.0-1+nmu3
- ubuntu jammy: ipwatchd 1.2.1-1build1
- ubuntu noble: ipwatchd 1.2.1-1build3
- ubuntu questing: ipwatchd 1.3.0-1+nmu3
- ubuntu resolute: ipwatchd 1.3.0-1+nmu3build1
- ubuntu stonking: ipwatchd 1.3.0-2 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms