Feature Request: Arpwatch DB persist
-
This is a feature request for the Arpwatch package. Arpwatch needs a setting to persist it's database. Every time I update the package it's followed by a barrage of emails. There is no good reason it cant keep that file through an update. Please fix. Thanks!
-
@ex1580 this feature is already implemented in the latest Arpwatch version: https://redmine.pfsense.org/issues/10475
-
@viktor_g That was fast! My inbox thanks you!
-
@viktor_g But I have never found this to work.
And for what it's worth, the new Suppress capability doesn't prevent notifications either.
Could it be because I am using DHCP Reservations / static mapping?
-
Any ideas of why the latest release still notifies me of new stations even though I am using the Suppress capability? And that installing the new release still seems to have clobbered the database of the previous version?
-
@viktor_g arpwatch 0.2.0_3 seems to do the trick! Thanks!
-
@viktor_g Yes, 0.2.0_3 kept the database. Thanks!
-
@viktor_g The DB was kept BUT today I got an alert for an automatic private IP. Hmm.
arpwatch reused old ethernet address 0.0.0.0 30:59:b7:14:8d:4e (84:fd:d1:e6:22:10) arpwatch new station 169.254.53.9 30:59:b7:14:8d:4e
-
I guess changing to an automatically assigned address is still a MAC address change. I couldnt find anything in any manuals about if reporting these is normal or not for Arpwatch and I never noticed before so I'm just looking for confirmation. Not really a big deal and potentially helpful for DHCP issues. I believe this one was due to the computer being in sleep mode when the DHCP address renewed but that's just a guess.
