From owner-freebsd-current@FreeBSD.ORG Tue May 22 16:34:15 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE60516A421 for ; Tue, 22 May 2007 16:34:15 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.235]) by mx1.freebsd.org (Postfix) with ESMTP id 5934513C45D for ; Tue, 22 May 2007 16:34:15 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nz-out-0506.google.com with SMTP id s1so2661447nze for ; Tue, 22 May 2007 09:34:14 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OUUimaRzSOv/QWXkNoBAoDHPTMepNC1fFEkP4H7+fpYI8gWUtVED13AzeoCzINthBZqxLYpcOIqyHRWln1XjxvriyWroIKo01uwClj91U5YIwOjDn7XWlVt1fkORmPNXtdsCsebbu91rBohXhIJSYL7RYegOrcHa+MoV1dULSc4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=T8TwRGcwa3MQwSboHHi1dgNVlTFnA5ApvZBT3EzChswxbJFiKn23Mc2Yo0uf8LXqZPGW6LCkeZzRTV1nwHSS10mzw0pwBVxtByiJna0HA0rHBAdjJpEGVxCtjTGwuit0F1C5kZkLpgwBtMnZXsDuradNXImWcrNZfIXVyLeUHiw= Received: by 10.114.110.1 with SMTP id i1mr3351804wac.1179851653925; Tue, 22 May 2007 09:34:13 -0700 (PDT) Received: by 10.114.126.10 with HTTP; Tue, 22 May 2007 09:34:13 -0700 (PDT) Message-ID: <2a41acea0705220934g666dfc56kaac4ac43ab325352@mail.gmail.com> Date: Tue, 22 May 2007 09:34:13 -0700 From: "Jack Vogel" To: "Ian FREISLICH" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0705220049w32b50fc6m37a2e2fef5c8837e@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: em0 hijacking traffic to port 623 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 16:34:15 -0000 On 5/22/07, Ian FREISLICH wrote: > "Jack Vogel" wrote: > > On 5/21/07, Ian FREISLICH wrote: > > > Looking at the new source, I'm not sure it will stop this adaptor > > > gobbling port 623. It's a 82546EB, e1000_82546_rev_3 e1000_mac_type. > > > In em_init_manageability(), it looks like it's only disabled for > > > e1000_mac_type >= e1000_82571 which excludes this adaptor: > > > > > > /* enable receiving management packets to the host */ > > > if (adapter->hw.mac.type >= e1000_82571) { > > > manc |= E1000_MANC_EN_MNG2HOST; > > > #define E1000_MNG2HOST_PORT_623 (1 << 5) > > > #define E1000_MNG2HOST_PORT_664 (1 << 6) > > > manc2h |= E1000_MNG2HOST_PORT_623; > > > manc2h |= E1000_MNG2HOST_PORT_664; > > > E1000_WRITE_REG(&adapter->hw, E1000_MANC2H, manc2h) > ; > > > } > > > > > > I'll give the driver a whirl anyway. If it doesn't, is it safe to write > > > 'manc |= E1000_MANC_EN_MNG2HOST' for adapter->hw.mac.type >= e1000_82546? > > > > If you can test that would be useful. > > FWIW, the new driver doesn't disable RCMP filtering on this NIC. :( > > But, doing this to the new driver solves the immediate problem for me: > > diff -u -d -r1.3 e1000_82540.c > --- e1000_82540.c 16 May 2007 00:14:23 -0000 1.3 > +++ e1000_82540.c 22 May 2007 11:21:02 -0000 > @@ -316,6 +316,7 @@ > /* Disable HW ARPs on ASF enabled adapters */ > manc = E1000_READ_REG(hw, E1000_MANC); > manc &= ~E1000_MANC_ARP_EN; > + manc &= ~(E1000_MANC_RMCP_EN | E1000_MANC_0298_EN); > E1000_WRITE_REG(hw, E1000_MANC, manc); > > E1000_WRITE_REG(hw, E1000_IMC, 0xffffffff); > > If you can point me to the propper place or way to effect this. I > can see situations where someone would not want to turn this filtering > off - if they have the IPMI daughterboard on their motherboard. This is in shared code, so let me forward the issue to the owners of same here and see what they say. Cheers, Jack