Date: Mon, 3 Feb 1997 00:54:45 -0800 (PST) From: Julian Elischer <julian@current1.whistle.com> To: "Joe \"Marcus\" Clarke" <jmcla@ocala.cs.miami.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: le0 driver and CAP-6.0 Message-ID: <Pine.BSF.3.95.970203005223.23665A-100000@current1.whistle.com> In-Reply-To: <Pine.SGI.3.95.970202234119.22164A-100000@ocala.cs.miami.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm surprised that the patches to CAP to allow it to use kernel support for ddx are not used.. netatalk runs pretty much out of the box and uses the ekrnel appletalk support.. julian On Sun, 2 Feb 1997, Joe "Marcus" Clarke wrote: > 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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970203005223.23665A-100000>