From owner-freebsd-net@FreeBSD.ORG Tue Oct 18 17:55:53 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A196F106564A; Tue, 18 Oct 2011 17:55:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 75AB58FC0A; Tue, 18 Oct 2011 17:55:53 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 2491546B0A; Tue, 18 Oct 2011 13:55:53 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A35C58A02E; Tue, 18 Oct 2011 13:55:52 -0400 (EDT) From: John Baldwin To: freebsd-net@freebsd.org Date: Tue, 18 Oct 2011 13:04:16 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <1318018310.27029.10.camel@hitfishpass-lx.corp.yahoo.com> <20111011181219.GB5661@michelle.cdnetworks.com> <1318362745.2724.22.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: <1318362745.2724.22.camel@hitfishpass-lx.corp.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201110181304.16746.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 18 Oct 2011 13:55:52 -0400 (EDT) Cc: "pyunyh@gmail.com" , David Christensen , Pyun YongHyeon , Sean Bruno , "davidch@freebsd.org" Subject: Re: bce(4) with IPMI X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2011 17:55:53 -0000 On Tuesday, October 11, 2011 3:52:25 pm Sean Bruno wrote: > In addition, the IPMI driver attaches to "something" and I can poke at > it via ipmitool. So, from the driver perspective, the attempt to detect > MFW enabled doesn't work as the chipset still thinks that its "on". The ipmi driver attaching to the BMC is independent. You can have the BMC active even though it's network channel is unavailable, so I wouldn't count on that datapoint being meaningful. -- John Baldwin