Bug 78728 - [arpwatch] Gives 'bogon' message for 0.0.0.0 IP
[arpwatch] Gives 'bogon' message for 0.0.0.0 IP
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: tcpdump (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-28 07:48 EST by Enrico Scholz
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-12-08 11:20:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Removes bogus 'bogon 0.0.0.0' message (338 bytes, patch)
2002-11-28 07:49 EST, Enrico Scholz
no flags Details | Diff

  None (edit)
Description Enrico Scholz 2002-11-28 07:48:30 EST
Description of Problem:

DHCP sets the source-IP address to 0.0.0.0 on DHCPDISCOVER messages. Same
happens when doing "Duplicate address detection  mode  (DAD)" (see '-D' option
at 'man 8 arping').

When arpwatch sees such packages, it creates a 'arpwatch: bogon 0.0.0.0 <mac>'
message.


Version-Release number of selected component (if applicable):

arpwatch-2.1a11-16


How Reproducible:

100%


Steps to Reproduce:
1.  run arpwatch
2a. on a DHCP enabled machine release the lease and restart the machine, OR
2b. run 'arping -D <IP>'
3.  watch /var/log/messages


Actual Results:

something like.
| ... arpwatch: bogon 0.0.0.0 0:2:b3:9a:9f:c4


Expected Results:

no such message
Comment 1 Enrico Scholz 2002-11-28 07:49:31 EST
Created attachment 86844 [details]
Removes bogus 'bogon 0.0.0.0' message
Comment 2 Harald Hoyer 2003-03-10 10:31:35 EST
is it fixed with the latest rawhide 3.7.2 version?
Comment 3 Enrico Scholz 2003-04-28 20:56:09 EDT
Still seeing it with the latest RHL 7.3 errata (arpwatch-2.1a11-17.7.3.2)
Comment 4 Harald Hoyer 2004-12-08 11:20:17 EST
please report that upstream... 

Note You need to log in before you can comment on or make changes to this bug.