From owner-freebsd-current  Sun Feb  2 20:46:24 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA07755
          for current-outgoing; Sun, 2 Feb 1997 20:46:24 -0800 (PST)
Received: from ocala.cs.miami.edu (ocala.cs.miami.edu [129.171.34.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA07735
          for <freebsd-current@freebsd.org>; Sun, 2 Feb 1997 20:46:16 -0800 (PST)
Received: from localhost by ocala.cs.miami.edu via SMTP (950413.SGI.8.6.12/940406.SGI)
	for <freebsd-current@freebsd.org> id XAA22189; Sun, 2 Feb 1997 23:46:08 -0500
Date: Sun, 2 Feb 1997 23:46:08 -0500 (EST)
From: "Joe \"Marcus\" Clarke" <jmcla@ocala.cs.miami.edu>
To: freebsd-current@freebsd.org
Subject: le0 driver and CAP-6.0
Message-ID: <Pine.SGI.3.95.970202234119.22164A-100000@ocala.cs.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Recently I upgraded to 3.0-SNAP.  I did a complete clean install.  I was
able to get all of my network functions working except CAP.  This was no
big surprise since CAP never worked with 2.2 either, but I thought I
might give it a shot.  I was able to isolate the problem through many
tests and conversations with Max, who maintains the package.  He was
quite helpful.  This is the error I receive when I try to run aarpd with
an le0 ethernet card and 16 bpf devices:

aarpd -D 20 "le0" "Res Labs (SRC)"
23:43:52 02/02/97  Ethernet address for le0 is 08:00:2b:99:3e:87
23:43:52 02/02/97  Packet from self
23:43:52 02/02/97  Packet from self
23:43:52 02/02/97  Packet from self
23:43:52 02/02/97  Packet from self
23:43:52 02/02/97  Packet from self
23:43:52 02/02/97  Packet from self
23:43:52 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  Packet from self
23:43:53 02/02/97  acquired node 1 on interface le0
Interface le0, zone Res Labs (SRC), acquired node number 1/255.0
SIOCADDMULTI: Invalid argument
Can't add multicast address!


Max suggests that there is a problem with the driver and how it handles
DEC ethernet ioctl on DEC ethernet cards.  Has anyone gotten CAP to run
under 3.0-SNAP with a DEC EtherWORKS 3 model 205 ethernet card?  Can
anyone confirm the error I'm receiving?  Is there a solution besides
switching cards?  Thanks.

-Joe Marcus