Bug 78808 - inappropriate bogon messages with -n flag
Summary: inappropriate bogon messages with -n flag
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: tcpdump   
(Show other bugs)
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-12-01 01:03 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-01 01:04:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Need Real Name 2002-12-01 01:03:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Running arpwatch with the -n flag still gives me bogon messages.
The -n flag doesn't seem to work as advertized.

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


How reproducible:
Always

Steps to Reproduce:
1. arpwatch -d -n 123.123.123.0/8


Actual Results:  arpwatch: bogon 123.123.123.123 0:xx:xx:xx:xx:xx


Expected Results:  No bogon messages for an address in the additional networks

Additional info:

arpwatch.c:774 checks for bogons:
   if ((sia & np->netmask) == np->net)
       return 0;

with -n 123.123.123.0/8 and a packet from 123.123.123.123, the variables I see are:

  sia:         0x7B7B7B7B
  np->netmask: 0x000000FF
  np->net:     0x007B7B7B

np->netmask seems to have the wrong byte order.

Comment 1 Need Real Name 2002-12-01 01:17:08 UTC
Okay, I've just realized that I'm an idiot.  I wanted 123.123.123.0/24, not /8...

arpwatch works fine if I give it correct input.


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