From owner-freebsd-security Sun Sep 27 11:56:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28561 for freebsd-security-outgoing; Sun, 27 Sep 1998 11:56:32 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28547 for ; Sun, 27 Sep 1998 11:56:29 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id OAA04433; Sun, 27 Sep 1998 14:56:14 -0400 (EDT) (envelope-from wollman) Date: Sun, 27 Sep 1998 14:56:14 -0400 (EDT) From: Garrett Wollman Message-Id: <199809271856.OAA04433@khavrinen.lcs.mit.edu> To: Eivind Eklund Cc: Poul-Henning Kamp , andrew@squiz.co.nz, Heikki Suonsivu , freebsd-security@FreeBSD.ORG Subject: Re: ipfw In-Reply-To: <19980927201139.00803@follo.net> References: <11806.906905580@critter.freebsd.dk> <19980927201139.00803@follo.net> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: >> * per interface input list >> * per interface output list >> * packet forwarding list >> * ip_input() list >> * ip_output() list > I don't think it would have to be complex to configure it - we could > do this splitting automatically, based on what the users has > configured and an 'ipfw finalize' or similar. > Of course, I would rather have everything be explicit, but that has > been shouted down when I suggested it, too. int fast1/0 ip access-group nosmurf out ! int eth3/0 ip access-group mumblefrotz in ! line vty 0 3 access-class 27 ! ...sound familiar? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message