From owner-freebsd-current@FreeBSD.ORG Fri Jun 13 02:18:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C14037B401 for ; Fri, 13 Jun 2003 02:18:45 -0700 (PDT) Received: from netlx014.civ.utwente.nl (netlx014.civ.utwente.nl [130.89.1.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2340343FA3 for ; Fri, 13 Jun 2003 02:18:44 -0700 (PDT) (envelope-from r.s.a.vandomburg@student.utwente.nl) Received: from gog (gog.student.utwente.nl [130.89.165.107]) by netlx014.civ.utwente.nl (8.11.4/HKD) with ESMTP id h5D9Ifi19647 for ; Fri, 13 Jun 2003 11:18:41 +0200 Message-Id: <200306130918.h5D9Ifi19647@netlx014.civ.utwente.nl> From: "Roderick van Domburg" To: Date: Fri, 13 Jun 2003 11:18:45 +0200 Organization: University of Twente MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook, Build 11.0.4920 Thread-Index: AcMxjMnuSb+dj2FHQRe8vjD4WqS1qw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 X-UTwente-MailScanner: Found to be clean Subject: Support DHCP in rc.firewall by default? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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: Fri, 13 Jun 2003 09:18:45 -0000 Right now, rc.firewall isn't set up to support DHCP configurations although it could easily be done so. Googling comes up with many references, for example http://www.freebsddiary.org/firewall.php (section "ipfw with DHCP etc" at the bottom of the page). Are there any reasons against having rc.firewall contain such lines? I reckon it would even come in handy for statically configured users: they'd only need to specify their network interface(s) once. Roderick