From owner-freebsd-current  Sat Aug 24 16:30:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA10932
          for current-outgoing; Sat, 24 Aug 1996 16:30:59 -0700 (PDT)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA10925
          for <current@freebsd.org>; Sat, 24 Aug 1996 16:30:57 -0700 (PDT)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA12029; Sat, 24 Aug 1996 16:29:00 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3)
	id sma012027; Sat Aug 24 16:28:56 1996
Message-ID: <321F8FFC.7991A45@whistle.com>
Date: Sat, 24 Aug 1996 16:27:56 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
CC: Brian Tao <taob@io.org>, current@freebsd.org
Subject: Re: rarpd broken on 2.2-960801-SNAP?
References: <199608242010.QAA04360@skynet.ctr.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Bill Paul wrote:
> 
>
> Are you absitively posolutely sure it's not sending out a reply,
> even a garbled one? When I first shoehorned rarpd into 2.0.5, I
> discovered that when I set the ether_type in the outgoing frame,
> I had to deliberately _not_ convert it to network byte order (no htons())
> in order for it to go out correctly. This confused me greatly because
> NetBSD did (does?) use htons(). I could swear I read somewhere that
> this was due to a bug in BPF. It's possible someone fixed the bug,
> making the htons() necessary again.
> 
I believe this may be the case.....
I remember some traffic on the topic....