From owner-freebsd-net@FreeBSD.ORG  Tue Mar 15 06:14:48 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CB38D16A4CE
	for <freebsd-net@freebsd.org>; Tue, 15 Mar 2005 06:14:48 +0000 (GMT)
Received: from sb.santaba.com (sb.santaba.com [207.154.84.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5CFB943D48
	for <freebsd-net@freebsd.org>; Tue, 15 Mar 2005 06:14:48 +0000 (GMT)
	(envelope-from anon1@santaba.com)
Received: from [192.168.1.3] (ip68-6-38-163.sb.sd.cox.net [68.6.38.163])
	by sb.santaba.com (Postfix) with ESMTP id 1993B28483;
	Mon, 14 Mar 2005 22:14:48 -0800 (PST)
Message-ID: <42367D57.30009@santaba.com>
Date: Mon, 14 Mar 2005 22:14:47 -0800
From: Jeff Behl <anon1@santaba.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <4235E6CC.7040909@santaba.com>
	<200503141747.57487.jkim@niksun.com> <42362D37.6010202@santaba.com>
	<42364E75.8030205@elischer.org>
In-Reply-To: <42364E75.8030205@elischer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-net@freebsd.org
cc: Jung-uk Kim <jkim@niksun.com>
Subject: Re: IPMI doesn't work...
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2005 06:14:48 -0000

Julian Elischer wrote:

>
>
> Jeff wrote:
>
>>
>>>
>>>
>>>  
>>>
>> I'm not sure what you mean by in band.  The IP address of the BMC is 
>> assigned via the bios and is different from what the OS later 
>> assigns.  With imiptool we can turn on/powercycle/monitor via the BMC 
>> assigned address up until the point where the kernel loads.  Once it 
>> does, the BMC no longer responds.  This doesn't happen with the two 
>> linux distros we've tried it on.  Wtih both, including SuSE, we can 
>> still query/control via the BMC using ipmitool.  It seems to be some 
>> sort of driver issue to me.  I find it confusing that the NIC is 
>> shared between the BMC and the OS, but I guess that's just how it's 
>> done.  Perhaps the bsd broadcomm driver is simply blocking this 
>> somehow...
>
>
>
> you have to assign it the same address!
>
that's not the way it's supposed to work, afaik.  it'd be silly to tie 
the BMC address and the OS assigned address together.  you give the BMC 
an ip address via a little program that comes from IBM and this address 
is independent of the ip address that whatever os you use on the system 
assigns to the nic.  the redbook that Jung-uk sent a link for shows this 
process if you're interested.

like i said earlier, having different ip addresses (the BMC's being in 
private address space) works fine with the linux kernel...