From owner-freebsd-bugs@freebsd.org  Tue Sep  8 20:34:22 2015
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 DBB9FA00721
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  8 Sep 2015 20:34:22 +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 C7C6919AB
 for <freebsd-bugs@FreeBSD.org>; Tue,  8 Sep 2015 20:34:22 +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 t88KYMxV087229
 for <freebsd-bugs@FreeBSD.org>; Tue, 8 Sep 2015 20:34:22 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 202978] After upgrade of net/syncthing 0.11.18 -> 0.11.23 in
 jail, the jail causes entire host to crash
Date: Tue, 08 Sep 2015 20:34:22 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: peter@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-202978-8-DZx3o1QBhk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202978-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-202978-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.20
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: Tue, 08 Sep 2015 20:34:23 -0000

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

--- Comment #3 from Peter Wemm <peter@FreeBSD.org> ---
There's several upstream bugs, but this one has discussion of using the wrong
address: https://github.com/syncthing/syncthing/issues/2090 

There's a few others.. if you search the issues list for multicast, you'll see
that you can also delete the contents of <localAnnounceMCAddr> and leave
localannounce enabled - that limits syncthing local announce on ipv4, and as a
side effect to one daemon per machine - and it can't run like that in a jail
anyway as jails can't bind to interface broadcast addresses.

Anyway, I'm mentioning it here because it is possible to do limited ipv4 local
announce if you need it.

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