From owner-freebsd-stable Fri Jun 8 6:56:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hercules.icarz.com (ns1.icarz.com [207.99.22.7]) by hub.freebsd.org (Postfix) with ESMTP id 63FFC37B40B for ; Fri, 8 Jun 2001 06:56:03 -0700 (PDT) (envelope-from kenm@icarz.com) Received: from newken (dhcp113.icarz.com [207.99.22.113]) by hercules.icarz.com (8.10.1/8.10.1) with SMTP id f58DtXw15027; Fri, 8 Jun 2001 09:55:33 -0400 (EDT) Message-ID: <00c801c0f022$b7a6f360$711663cf@icarz.com> From: "Ken Menzel" To: "Tom" , "Louis A. Mamakos" Cc: "Mats Dufberg" , References: Subject: auto-negotiate/auto-detect was Re: Any patch for fxp driver? Date: Fri, 8 Jun 2001 09:55:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-Mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Tom, I have noticed a problem running my Dell with fxp0: . If I use use mediaopt full-duplex, suddenly I start losing packets sometimes with ping! I don't notice mush of a problem in running except that the program "netsaint" which pings my other servers starts telling me I am losing packets (usually 1 of 5 is lost)! (It runs ping from a forked process, then in a shell (with spopen() ) . If I take out the mediaopt all runs well again (with just media 100baseTX) and it also works with full auto negotiation. The reason I was messing at all with it is a statement from another list about potential problems with auto-negotiation. So I am trying to disprove that. I learned that if you use the mediaopt full-duplex setting I had to program my switch to match (100baseTX full-duplex). It would not auto-detect the setting of the card (for duplex). This could be the root of the problem. Maybe someone else could correct me, but are there any know problems using auto negotiation with recent hardware/software? I think not! However, check the RMON stats on an intelligent switch, or run software on the client to monitor connections and errors (netstat -i, netstat -s). Hoep this helps, Ken > > > > ifconfig_fxp0="inet x.x.x.x netmask 255.255.255.0 media 100baseTX mediaopt > > full-duplex" > > > > in my /etc/rc.conf. Note that this system is connected to a 100Base-T > > ethernet switch with full-duplex capable ports.. > > > > louie > > > > Beware though. Autonegotiation != autodetection. If you manually set > any duplex settings on your switch or your NIC, autonegotiation is > disabled on your switch or your NIC respectively. Autonegotiation must be > set on both ends for it to work. I use autonegotiation religiously now, > as I hate having to keep reprogramming switch ports. All the hardware I > use works properly with auto. > > Tom > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message