From owner-freebsd-current@freebsd.org  Tue Aug  9 08:55:36 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 780DCBB234D
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  9 Aug 2016 08:55:36 +0000 (UTC)
 (envelope-from prvs=022e014eb=roger.pau@citrix.com)
Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63])
 (using TLSv1.2 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "DigiCert SHA2 Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2BAAD130D
 for <freebsd-current@freebsd.org>; Tue,  9 Aug 2016 08:55:35 +0000 (UTC)
 (envelope-from prvs=022e014eb=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.28,494,1464652800"; d="scan'208";a="378570497"
Date: Tue, 9 Aug 2016 10:55:32 +0200
From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
To: Miguel C <miguelmclara@gmail.com>
CC: freebsd-current <freebsd-current@freebsd.org>
Subject: Re: FreeBSD 11 - BETA-1 Xen DOMU loses network when jail (VIMAGE)
 starts
Message-ID: <20160809085523.kow2qbpirzppytv6@mac>
References: <CADGo8CUmcR6KRhV4RPxij=Ve8oBkazjebJAEvKV2gm6+G-c1eQ@mail.gmail.com>
 <CADGo8CWx05Lq5+Absoiaby2R8eyVYbZpMcJFFoR5wC76rd_1sg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CADGo8CWx05Lq5+Absoiaby2R8eyVYbZpMcJFFoR5wC76rd_1sg@mail.gmail.com>
User-Agent: Mutt/1.6.2-neo (2016-06-11)
X-DLP: MIA2
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 08:55:36 -0000

On Sat, Jul 23, 2016 at 08:46:49PM +0100, Miguel C wrote:
> Just as a note using netgraph (with jng script as a workaround) works....
> 
> Also manually creating a bridge in the domu and adding xn0 as a member
> makes this fail.... so the issue is indeed related to the bridge.
> 
> I'll open a PR later in case someone want to look into it, but I'm happy it
> works with netgraph.

I seem to be able to use xn* interfaces with bridges without problems:

xn0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 00:16:3e:74:3d:76
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet manual
        status: active
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:77:3d:4a:18:00
        inet 172.16.1.140 netmask 0xffffff00 broadcast 172.16.1.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        groups: bridge
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: xn0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 2 priority 128 path cost 2000000

Is this a GENERIC kernel or are you using some custom configuration/patches? 
Can you provide some more information about how to reproduce this?

Roger.