From owner-freebsd-net@FreeBSD.ORG  Fri Dec  3 18:44:11 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 407691065672
	for <freebsd-net@freebsd.org>; Fri,  3 Dec 2010 18:44:11 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221])
	by mx1.freebsd.org (Postfix) with ESMTP id 9288C8FC0A
	for <freebsd-net@freebsd.org>; Fri,  3 Dec 2010 18:44:10 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
	by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id oB3Ii7lH018772;
	Sat, 4 Dec 2010 00:44:07 +0600 (NOVT)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4CF93A77.30804@rdtc.ru>
Date: Sat, 04 Dec 2010 00:44:07 +0600
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
	rv:1.9.1.10) Gecko/20100712 Thunderbird/3.0.5
MIME-Version: 1.0
To: Jack Vogel <jfvogel@gmail.com>
References: <AANLkTimWVJhtu8LrZ_tn0Tdr-vs9PmPnW9SjebT7jnyM@mail.gmail.com>	<AANLkTik+4Ag1HYXDWJvn2fTx6M+pa9o29-A8j6qVRhZ_@mail.gmail.com>	<AANLkTikwcRW+dqY=NTSbJsr3daEd-8usPo0Rw+hA_D-8@mail.gmail.com>	<AANLkTin3+bCaXoPxTQsvzmqgtpA1zSY8f17Qh-nqymPw@mail.gmail.com>	<201011270946271408828@yahoo.com.cn>	<AANLkTikG8RJQw+h1SHZPs1cHGrM+3LfniZrdLqVoPVtr@mail.gmail.com>	<AANLkTi=YjG40+Dj7471wyv3aeXGJgoL1GC33iNaypsrW@mail.gmail.com>	<AANLkTi=LgejYxRXnxLtkvB-Qfp2u+tySdriWHfGWPQjL@mail.gmail.com>	<20101128081617.GA90332@zibbi.meraka.csir.co.za>	<AANLkTinF1fovumkeXxWgaKi_bNiUCnqgWAtdaCaXELzO@mail.gmail.com>	<4CF73A2C.7000802@rdtc.ru>	<4CF89EE7.8020807@rdtc.ru>
	<AANLkTi=6N3Rz57YVNF1ZiDGEexnEXWr6oNPz9F=c2GpA@mail.gmail.com>
In-Reply-To: <AANLkTi=6N3Rz57YVNF1ZiDGEexnEXWr6oNPz9F=c2GpA@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-net <freebsd-net@freebsd.org>
Subject: Re: Problem with igb(4) updated to version 2.0.7
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
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: Fri, 03 Dec 2010 18:44:11 -0000

On 03.12.2010 23:49, Jack Vogel wrote:
> It has never been the case that 'down'ing an interface brings link down,
> not on em
> or igb. So this isn't problem with the release.
> 
> Jack

Now I see, thanks.

Is it technically possible to bring link down
for distinct port of dual-port em/igb-supported NICs using software?

If yes, I'd like to patch my source tree.
For EtherChannel this kind of management should be possible.

Eugene Grosbein