From owner-freebsd-bugs@freebsd.org  Wed Nov  9 11:59:29 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78581C38E16
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed,  9 Nov 2016 11:59:29 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 67C29674
 for <freebsd-bugs@FreeBSD.org>; Wed,  9 Nov 2016 11:59:29 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uA9BxTu1010412
 for <freebsd-bugs@FreeBSD.org>; Wed, 9 Nov 2016 11:59:29 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 214359] [vxlan] [patch] make if_vxlan(4) compatible with
 if_bridge(4)
Date: Wed, 09 Nov 2016 11:59:29 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: ports@grosbein.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status keywords bug_severity priority component assigned_to
 reporter attachments.created
Message-ID: <bug-214359-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2016 11:59:29 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214359

            Bug ID: 214359
           Summary: [vxlan] [patch] make if_vxlan(4) compatible with
                    if_bridge(4)
           Product: Base System
           Version: 11.0-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: ports@grosbein.net
          Keywords: patch

Created attachment 176815
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176815&action=
=3Dedit
sumulate full-duplex link to please if_bridge

Currently, if_vxlan(4) can be used as port of if_bridge(4) with STP disabled
only because STP-enabled bridge keeps such port disabled/discarding
permanently. The reason is vxlan fails to show working link state.

Attached patch fixes this by simulating 10G full-duplex link for vxlan. With
this patch applied, STP-enabled bridge is able to configure vxlan port(s) as
designated/forwarding.

--=20
You are receiving this mail because:
You are the assignee for the bug.=