From owner-freebsd-jail@FreeBSD.ORG Thu Oct 2 15:35:31 2014 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65DD9196; Thu, 2 Oct 2014 15:35:31 +0000 (UTC) Received: from m2.gritton.org (gritton.org [63.246.134.121]) (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 339F3350; Thu, 2 Oct 2014 15:35:30 +0000 (UTC) Received: from [192.168.0.34] (c-50-168-192-61.hsd1.ut.comcast.net [50.168.192.61]) (authenticated bits=0) by m2.gritton.org (8.14.9/8.14.9) with ESMTP id s92FZRMP060453; Thu, 2 Oct 2014 09:35:27 -0600 (MDT) (envelope-from jamie@gritton.org) Message-ID: <542D70B8.1090603@gritton.org> Date: Thu, 02 Oct 2014 09:35:20 -0600 From: James Gritton User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-jail@freebsd.org, freebsd-stable@freebsd.org Subject: Re: no network connection from inside a jail References: <20141002180506.4965760b@X220.alogt.com> In-Reply-To: <20141002180506.4965760b@X220.alogt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 15:35:31 -0000 On 10/2/2014 4:05 AM, Erich Dollansky wrote: > Hi, > > I recently upgraded to 10.1 BETA3 via sources. All seemed to be fine > until I started jails which connect to the Internet. It simply does not > work anymore. When the browser from the jail connects to another jail > on the same machine via HTTP, it all works. Accesses to the ouside of > the machine fails. > > Even a ping to a local device does not work. > > ping 192.168.yyy.xxx > ping: socket: Operation not permitted > > despite having > > security.jail.allow_raw_sockets: 1 > > Just to make sure, I upgraded also the world in all jails without any > difference. > > UPDATING did not mention any changes since BETA1. > > I feel a bit lost now. > > What could have caused the problems? > > Erich Having looked at an svn diff between BETA1 and BETA3, I'm at a loss. The only change involving jails was a few lines that tested a condition for a locking issue in the kernel (r271622). I also looked for any changes to lagg, on a hunch the problem might be there, but found nothing changed there either. - Jamie