Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 78808 - inappropriate bogon messages with -n flag
Summary: inappropriate bogon messages with -n flag
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: tcpdump
Version: 8.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
Depends On:
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:
Clone Of:
Last Closed: 2002-12-01 01:04:01 UTC

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:

Steps to Reproduce:
1. arpwatch -d -n

Actual Results:  arpwatch: bogon 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 and a packet from, 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, 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.