From owner-freebsd-current@FreeBSD.ORG Mon Sep 29 15:25:44 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 76DCCD8F for ; Mon, 29 Sep 2014 15:25:44 +0000 (UTC) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 3C24EA83 for ; Mon, 29 Sep 2014 15:25:43 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 16AE47302B; Mon, 29 Sep 2014 17:30:43 +0200 (CEST) Date: Mon, 29 Sep 2014 17:30:43 +0200 From: Luigi Rizzo To: current@freebsd.org Subject: capsicum and netmap ? Message-ID: <20140929153043.GA78397@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 15:25:44 -0000 Hi, while trying the netmap-enabled libpcap library with tcpdump, i noticed it fails to return data on a kernel with capsicum (the string "capability mode sandbox enabled" made me suspicious, and removing the cap_*() calls from tcpdump.c seems to make things work again). Would anyone be able to point me what should be done in the netmap kernel module to make it work with capsicum ? I am sure the cambridge folks are very interested in this :) cheers luigi