From owner-freebsd-net@freebsd.org Wed May 4 14:48:55 2016 Return-Path: Delivered-To: freebsd-net@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 87294B2D165 for ; Wed, 4 May 2016 14:48:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F33A1B9E for ; Wed, 4 May 2016 14:48:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ob0-x236.google.com with SMTP id x1so21689318obt.0 for ; Wed, 04 May 2016 07:48:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=sQF6EoGltYGKllfjpKp7TjopP0LJFYj3jsDP8J9xi6M=; b=BvlT6m7vjKB2ePEpLF35TvcMEhbVHaLn3/xGkpSd/hD7P/rskZaMNhtBdFwPWr6v9C R4PMdpPV/d+/StO8wO6ReiFZGIJNzUNTYDx3DkMgTl2HOEZbAxoVTcIEbVJSnK9RWEF/ +Z+UoZR1U1lvRkCpodEuxK4vyb9E6AY4KDcMSR3/rbfWvgjhEP6PL9VAq6MkLasI79/G JMfTJe5hboBCzYuOggYDdrleEJ1klwQP/BHDyjO0khrrfLMWVMoJI6Cl/A4jZ6ElHVwl w3Lec/n5F0z5Int4AYBH+MQBXVH0fouNobf3hJBRHPEG2yHLWLMvJgPkuwIgU/US/QN3 qnEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=sQF6EoGltYGKllfjpKp7TjopP0LJFYj3jsDP8J9xi6M=; b=Z5gvbwc3mJpcI/CCJpA9qkx/ZqJxnpxRZeNeP79Uue03kaqVeuHHQS2XcIHxFYSx7H a16UucBE7MPQ0p072b+1930rYOVjs9dZuoGhqgwOyq8UypzkonrmYAXuhp68bZ/ecI3N V7mbuTSbo3qN5KxauJ13KZl0guj6fCQxL6xXP9cVfJmbQVZmGHdLoamVbjZiQLXN9UIl gZe2eXkPE606773fBVBaA+rn8UoGbWAOxrBGAPM5viYf7avl8ZgSzczY3ODUHDrHAU3p GyXmHWsM2sl3C1JpNblL0NrmzhDhSiRjIxZ4P3mYfc3oLCKcnB2dzDdNe3aZ58wAeURB +9Uw== X-Gm-Message-State: AOPr4FXpGY0u3FoBhjxJUUEmB7NXWcqUjZtajtL9KdRsT+CD0iKr+Nb3apSe9iwiDL7ScerrVY5ApZsvw3UKZg== MIME-Version: 1.0 X-Received: by 10.182.232.168 with SMTP id tp8mr4226012obc.65.1462373334428; Wed, 04 May 2016 07:48:54 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.64.138 with HTTP; Wed, 4 May 2016 07:48:54 -0700 (PDT) In-Reply-To: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> References: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> Date: Wed, 4 May 2016 08:48:54 -0600 X-Google-Sender-Auth: sagLvvmS_iXhYgVWSRs8M2yXNNA Message-ID: Subject: Re: How to use pf with vimage jails? From: Alan Somers To: Kristof Provost Cc: FreeBSD Net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2016 14:48:55 -0000 On Wed, May 4, 2016 at 4:23 AM, Kristof Provost wrote: > > > On 04 May 2016, at 04:55, Alan Somers wrote: > > > > Is there any documentation on how to run pf on a host, using it to > control > > access to vimage jails? I see that only ipfw can be run from _inside_ = of > > the jail, but I'm interested in running pf _outside_ of the jail. > > That=E2=80=99s supported, and really no different from configuring pf oth= erwise. > Just treat the vimage jails as if they were on different machines, behind > your firewall. > > Regards, > Kristof > > Then maybe it's the bridged aspect that's screwing me up. Is there a guide for using pf on bridged interfaces? All I can find is this guide for ipfw. https://www.freebsd.org/doc/en/articles/filtering-bridges/article.html -Alan