From nobody@FreeBSD.org  Thu May 19 13:55:37 2011
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 52FF21065673
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 19 May 2011 13:55:37 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 42C3D8FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 19 May 2011 13:55:37 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p4JDtaLA047089
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 19 May 2011 13:55:36 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id p4JDta7U047088;
	Thu, 19 May 2011 13:55:36 GMT
	(envelope-from nobody)
Message-Id: <201105191355.p4JDta7U047088@red.freebsd.org>
Date: Thu, 19 May 2011 13:55:36 GMT
From: Frank Razenberg <frank@zzattack.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: lagg interface not working together with epair interface on bridge
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         157182
>Category:       kern
>Synopsis:       [lagg] lagg interface not working together with epair interface on bridge
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-net
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 19 14:00:24 UTC 2011
>Closed-Date:    
>Last-Modified:  Sat May 21 22:38:23 UTC 2011
>Originator:     Frank Razenberg
>Release:        8.2-STABLE
>Organization:
>Environment:
FreeBSD laggtest.zzattack.org 8.2-STABLE FreeBSD 8.2-STABLE #1: Thu May 19 13:18:35 UTC 2011 root@laggtest.zzattack.org:/usr/obj/usr/src/sys/ZZAT amd64

KERNCONF ZZAT is jsut GENERIC with options VIMAGE
>Description:
The combination of an epair and lagg interface on a bridge seems to cause
problems. When both types of interfaces are added to a bridge, dmesg first
outputs 

 >> error setting interface capabilities on lagg0
 
 The bridge can still be used and it both interfaces are on placed on
 the bridge. It seems however that the epair and lagg do not communicate.
 
 Initially I believed this to be an epair problem and posted on freebsd-
 virtualization instead. For reference:
 http://lists.freebsd.org/pipermail/freebsd-virtualization/2011-May/thread.html#707
 
 >> bound to 10.31.45.194
 
 ifconfig epair create
 ifconfig bridge create 
 ifconfig bridge0 addm lagg0 
 ifconfig bridge0 addm epair0a
 >> error setting interface capabilities on lagg0
 ifconfig epair0a up
 
 dhclient epair0b
 >> no DHCPOFFERS received
 
 ifconfig bridge0 destroy
 
 ifconfig lagg0 destroy
 
 dhclient em0
 >> bound 10.31.45.194
 
 ifconfig bridge0 addm em0
 ifconfig bridge0 addm epair0a
 ifconfig bridge0 up
 dhclient epair0b
 >> works
 
 # Note that simply removing lagg0 from the bridge and adding em0 to it instead
 # does NOT work. We need to use a completely new bridge.
>How-To-Repeat:
csup 8.2-STABLE
build/install/boot into kernel with options VIMAGE
have dhcp server on network
I had a em0 interface, not sure if it works better with others.

ifconfig lagg create laggproto lacp laggport em0
ifconfig em0 up
dhclient lagg0
>Fix:
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sat May 21 22:36:21 UTC 2011 
Responsible-Changed-Why:  
Fix up formatting and assign. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=157182 
>Unformatted:
