From owner-freebsd-questions  Fri Feb 21 10: 0:10 2003
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5CF0E37B401
	for <freebsd-questions@FreeBSD.ORG>; Fri, 21 Feb 2003 10:00:09 -0800 (PST)
Received: from bjwcs.com (swing.bjwcs.com [208.185.25.11])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 471FC43FBD
	for <freebsd-questions@FreeBSD.ORG>; Fri, 21 Feb 2003 10:00:05 -0800 (PST)
	(envelope-from brently@bjwcs.com)
Received: from samba [68.98.15.6] by bjwcs.com with ESMTP
  (SMTPD32-7.07) id A83875800F4; Fri, 21 Feb 2003 12:56:08 -0500
From: "Brent Wiese" <brently@bjwcs.com>
To: "'Joseph Noonan'" <jfn@msc.com>
Cc: <freebsd-questions@FreeBSD.ORG>
Subject: RE: Bizarre Networking Problem
Date: Fri, 21 Feb 2003 10:56:08 -0700
Message-ID: <002501c2d9d2$8392f100$0a0114ac@home.bjwcs.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <20030221105259.Y87091@pcjfn.msc.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

> Well the problem is solved, but I am not happy about the 
> solution as it makes absolutely no sense to me.
> 
> xl0: 
> flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
>         options=3<rxcsum,txcsum>
>         inet 192.246.38.10 netmask 0xffffff00 broadcast 255.255.255.0
>         inet 208.23.240.10 netmask 0xffffff00 broadcast 208.23.240.255
>         ether 00:04:75:b0:24:12
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> 

Your nic is set autosense. While probably not the only culprit, if you
can manage your 3com switch, hard set the port and your NIC to 100 full
duplex. 

It may not solve the problem, but its one more variable eliminated.

I was running a HP 4000M and all the machines set auto. I did a code
upgrade on the switch and all of sudden performance went in the gutter
because, for some reason, autosense "broke". Once I hard set 100fd on
everything, performance was once again stellar.

The broadcast for 192.246.38.10 is wrong too.

You shouldn't have to run in promiscous mode to solve this... Doing so
is going to kill your CPU when traffic gets high.

Brent


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message