From owner-freebsd-stable Tue Jan 4 16:37:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.vr.IN-Berlin.DE (gnu.in-berlin.de [192.109.42.4]) by hub.freebsd.org (Postfix) with ESMTP id BFAEB14D4F for ; Tue, 4 Jan 2000 16:37:15 -0800 (PST) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: from hirsch.in-berlin.de (root@hirsch.in-berlin.de [192.109.42.6]) by mail.vr.IN-Berlin.DE (8.9.3/8.9.3) with ESMTP id BAA03057 for ; Wed, 5 Jan 2000 01:37:07 +0100 (CET) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: by hirsch.in-berlin.de (Smail3.2) id ; Wed, 5 Jan 2000 01:37:05 +0100 (CET) Received: by dva.in-berlin.de (Postfix, from userid 200) id 121EF10F72; Wed, 5 Jan 2000 00:54:14 +0100 (CET) Date: Wed, 5 Jan 2000 00:54:13 +0100 From: Boris Staeblow To: freebsd-stable@freebsd.org Subject: Re: enabling bridge-support in rc.conf? Message-ID: <20000105005413.A95924@dva.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Sittig wrote: >No. One principle of routing packets between interfaces is that >this should never happen by default but instead ALWAYS demands an >admin to conciously activate this feature. That's what the RFC >says about "requirements for networked computers" (don't have the >number at hand). So if you happen to boot a kernel with bridging >support compiled in, it still should be your explicit decision to >forward packets to a different interface. Agree. But there´s no possibility to configure exactly this directly in /etc/rc.conf. The alternate is to create a script in /usr/local/etc/rc.d. Boris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message