From owner-freebsd-hackers Fri Apr 5 09:31:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA27689 for hackers-outgoing; Fri, 5 Apr 1996 09:31:33 -0800 (PST) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA27682 for ; Fri, 5 Apr 1996 09:31:29 -0800 (PST) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id MAA10337 for ; Fri, 5 Apr 1996 12:34:24 -0500 Date: Fri, 5 Apr 1996 12:34:24 -0500 Message-Id: <199604051734.MAA10337@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: dennis@etinc.com (dennis) Subject: Re: Freebsd Vs. Linux Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >X-Sender: tjeffers@nastg.gsfc.nasa.gov >Date: Fri, 05 Apr 1996 11:30:09 -0500 >To: dennis@etinc.com (dennis) >From: Anthony Jefferson >Subject: Re: Freebsd Vs. Linux > >At 10:41 AM 4/4/96 -0500, you wrote: > >>>You can increase the buffer space to get rid of the ENOBUF errors, but >>>they are really "backoff and retransmit warnings". The other OS's you >>>tested are probably silenty dropping the packets. >> >>or queueing endlessly . There are good reasons to limit queue space, and >>if you overflow this with a non-realistic test then you havent learned very >>little. These can be tuned, I believe, as well. I think IFQ_MAXLEN is 50, >> which is really too small for an ethernet link (note that I think it is 300 >>in LINUX), >> particularly if the traffic is largely small packets that are being >>pummelled onto >> the line. You may try tuning this value (in /usr/src/sys/net/if.h) and see >>what happens. >> > >Thanks, your statement about "backoff and retransmit" was exactly the >senario we were experiencing. We had never had any OS tell us before >dropping the packets. What a nice change. > >We are also doing some work with multicast, was 2.0 BSD released with >multicast enabled and 2.1 disabled. We tried to join a multicast group using >2.1 and received some errors. In addtion, when we do a netstat -g we receive: > >muiltcast not compiled into the system. > >A fairly good indication we have something wrong. How do you enable >multicast in 2.1 ? I did not see any config parameters related to multicast ? > >Well, thanks again for the response. BSD was the OS we wanted to use! > >******************************************************************************* >* Anthony C. Jefferson Phone:(301)794-2895 FAX:(301) 794-9530 >* Computer Sciences Corp. 7700 Hubble Drive Lanham-Seabrook Md. 20706 >* E-MAIL:tjeffers@nastg.gsfc.nasa.gov 8-{) >******************************************************************************* > > > ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX