From owner-freebsd-questions@FreeBSD.ORG Mon Oct 10 08:10:58 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73A36106566B for ; Mon, 10 Oct 2011 08:10:58 +0000 (UTC) (envelope-from sudakov@sibptus.tomsk.ru) Received: from relay2.tomsk.ru (relay2.tomsk.ru [212.73.124.8]) by mx1.freebsd.org (Postfix) with ESMTP id A208A8FC0C for ; Mon, 10 Oct 2011 08:10:57 +0000 (UTC) X-Virus-Scanned: by clamd daemon 0.93.1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.tomsk.ru (account sudakov@sibptus.tomsk.ru [212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.13) with ESMTPSA id 20883291 for freebsd-questions@freebsd.org; Mon, 10 Oct 2011 14:10:54 +0700 Received: from admin.sibptus.tomsk.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.tomsk.ru (8.14.3/8.14.3) with ESMTP id p9A7AsH7024629 for ; Mon, 10 Oct 2011 14:10:54 +0700 (OMSST) (envelope-from sudakov@sibptus.tomsk.ru) Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.14.3/8.14.3/Submit) id p9A7ArVU024628 for freebsd-questions@freebsd.org; Mon, 10 Oct 2011 14:10:54 +0700 (NOVT) (envelope-from sudakov@sibptus.tomsk.ru) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to sudakov@sibptus.tomsk.ru using -f Date: Mon, 10 Oct 2011 14:10:53 +0700 From: Victor Sudakov To: FreeBSD Questions Message-ID: <20111010071053.GB23778@admin.sibptus.tomsk.ru> Mail-Followup-To: Victor Sudakov , FreeBSD Questions References: <20111008235238.GB3136@hs1.VERBENA> <20111009015141.GA60380@hs1.VERBENA> <20111009051554.GA91440@admin.sibptus.tomsk.ru> <20111009083855.0e9879f6@davenulle.org> <20111009073910.GB92531@admin.sibptus.tomsk.ru> <4E91890D.7050105@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E91890D.7050105@gmx.com> User-Agent: Mutt/1.4.2.3i Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.livejournal.com/pubkey.bml?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 Subject: Re: need help with pf configuration X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2011 08:10:58 -0000 Nikos Vassiliadis wrote: > >> > >>>I have a configuration with 2 inside interfaces, 1 outside and 1 dmz > >>>interface. The traffic should be able to flow > >>> > >>>1) from inside1 to any (and back) > >>>2) from inside2 to any (and back) > >>>3) from dmz to outside only (and back). > >>> > >>>I need no details, just a general hint how to setup such security > >>>levels, preferably independent of actual IP addressses behind the > >>>interfaces (a :network macro is not always sufficient). > >> > >>You may use urpf-failed instead :network > >>urpf-failed: Any source address that fails a unicast reverse path > >>forwarding (URPF) check, i.e. packets coming in on an interface other > >>than that which holds the route back to the packet's source address. > > > >Excuse me, I do not see how this is relevant to my question (allowing > >traffic to be initiated from a more secure interface to a less secure > >interface and not vice versa). > > > > What if you combine macros and lists? > The ruleset below seems "scalable" to any number of interfaces. > > inside1 = em1 > inside2 = em2 > dmz = em0 > insides = "{" $inside1:network $inside2:network "}" The problem is, there could be several routed networks behind the inside interfaces. Not all inside networks are directly connected, and the :network macro works only for directly connected interfaces, right? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru