Bug 244606
Summary: | apple mac mini floods arpwatch | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dave Jones <davej> |
Component: | arpwatch | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | ivazquez, pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-09 13:04:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dave Jones
2007-06-18 02:35:30 UTC
That sounds like IPv4LL as part of Bonjour. How long did this persist? until I gave it an entry in my dhcpd.conf and restarted dhcpd. actually, I was mistaken. I restarted arpwatch, and powered it back up. The flood resumed. It does it even if it has a valid IP address, which seems a bit crazy. Bogons from 169.254/16 can be avoided by adding -n 169.254/16 to /etc/sysconfig/arpwatch. I'm not sure we want this enabled by default, an administrator might want to know about it. Bogons from 0.0.0.0 can be avoided only by using -N (completely disabling bogons reporting). arpwatch could be fixed to allow -n 0/32, would that be enough? I'm not sure we should do anything. Technically, 0.0.0.0 _is_ a bogon, so we'd want to know about it. I blame apple. arpwatch-2.1a15-6.fc8 allows to use -n 0/32 which will disable reporting bogons from 0.0.0.0. |