From owner-freebsd-bugs@FreeBSD.ORG  Mon Jul  7 14:36:57 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4CF9344D
 for <freebsd-bugs@FreeBSD.org>; Mon,  7 Jul 2014 14:36:57 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1B4332C4F
 for <freebsd-bugs@FreeBSD.org>; Mon,  7 Jul 2014 14:36:57 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s67Eaur5051762
 for <freebsd-bugs@FreeBSD.org>; Mon, 7 Jul 2014 15:36:56 +0100 (BST)
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 191700] New: CARP does not work on interface which belongs to a
 bridge
Date: Mon, 07 Jul 2014 14:36:57 +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: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: vivek@khera.org
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-191700-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 14:36:57 -0000

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

            Bug ID: 191700
           Summary: CARP does not work on interface which belongs to a
                    bridge
           Product: Base System
           Version: 10.0-RELEASE
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Some People
          Priority: Normal
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: vivek@khera.org

If an interface participating in a CARP cluster becomes a member of a bridge,
it loses the ability to communicate on the CARP IP when it becomes the master.

Environment:
System: FreeBSD lorax.kcilink.com 10.0-RELEASE-p6 FreeBSD 10.0-RELEASE-p6 #2
r267868: Wed Jun 25 09:49:14 EDT 2014
vivek@lorax.kcilink.com:/u/lorax1/usr10/obj/u/lorax1/usr10/src/sys/KCI64 amd64

How-To-Repeat:
ifconfig em0 alias vhid 205 advskew 100 pass dnsprv 192.168.97.97/23

 -> on other host, bring down CARP or set the advskew to 200 to allow this
 host to become master.

at the point, you are able to ping and access services on 192.168.97.97 just
fine.

Restore the other member as the CARP master by adjusting advskew on the other
host back to below 100.

Now, do this:

ifconfig tap0 create
ifconfig bridge0 create
ifconfig bridge0 addm tap0 addm em0 up

And again, bring this host to be the master by adjusting advskew on the other
host > 100.  The CARP member of em0 will show it is MASTER, but you cannot
ping or access 192.168.97.97 on this machine at all.

Fix:
none known. workaround is to avoid using a bridge, but I need that for a bhyve
guest OS.

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