From owner-freebsd-sparc64@FreeBSD.ORG Fri Mar 5 11:21:58 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C4D116A4CE for ; Fri, 5 Mar 2004 11:21:58 -0800 (PST) Received: from mail.b0rken.org (beastie.b0rken.org [213.48.48.213]) by mx1.FreeBSD.org (Postfix) with SMTP id 4215D43D54 for ; Fri, 5 Mar 2004 11:21:57 -0800 (PST) (envelope-from jason-freebsdlists@freebsd.org) Received: (qmail 49991 invoked from network); 5 Mar 2004 19:21:56 -0000 Received: from localhost (HELO beastie.b0rken.org) (127.0.0.1) by mail.b0rken.org with SMTP; 5 Mar 2004 19:21:56 -0000 Received: (from jason@localhost) by beastie.b0rken.org (8.12.10/8.12.10/Submit) id i25JLt9n049989 for freebsd-sparc64@freebsd.org; Fri, 5 Mar 2004 19:21:55 GMT (envelope-from jason-freebsdlists@freebsd.org) X-Authentication-Warning: beastie.b0rken.org: jason set sender to jason-freebsdlists@freebsd.org using -f Date: Fri, 5 Mar 2004 19:21:55 +0000 From: Jason Mann To: freebsd-sparc64@freebsd.org Message-ID: <20040305192155.GD47394@beastie.b0rken.org> Mail-Followup-To: freebsd-sparc64@freebsd.org References: <20040305164638.GA47394@beastie.b0rken.org> <20040305105639.K470@light.sdf.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040305105639.K470@light.sdf.com> User-Agent: Mutt/1.4.2.1i Subject: Re: hme driver acting strangely X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2004 19:21:58 -0000 I have further information on this issue now. I've just fitted a Sun qfe card to the machine, and the 4 ports are detected as hme2 thru hme5. This card does appear to negotiate full-duplex mode with the switch, and my services can still listen on udp ports on that interface when it is in this mode. If I try forcing full-duplex, the problem comes back. So, to summarise: - Old hme's won't auto negotiate, confirming Tom's comment. Only way to get them in full-duplex mode is to force it. - New hme's/qfe's DO auto negotiate, so theres no need to force them to full-duplex. - Any time you force full-duplex on an hme driven interface, udp ports can't be listened on. So, it's not a problem for me anymore, but theres still something odd going on. Regards, Jason