From owner-freebsd-stable Mon May 8 23:38:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D4A0037B9AF; Mon, 8 May 2000 23:38:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA76317; Mon, 8 May 2000 23:38:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 8 May 2000 23:38:13 -0700 (PDT) From: Kris Kennaway To: "Dan O'Connor" Cc: phthin@club-internet.fr, freebsd-stable@FreeBSD.ORG Subject: Re: ipfw: warning: interface ``tun0'' does not exist with ipfw under 4.0 In-Reply-To: <01d801bfb849$15e64880$0200000a@danco> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 May 2000, Dan O'Connor wrote: > >ipfw: warning: interface ``tun0'' does not exist > > Under 4.0, the 'tun0' device doesn't exist until you start ppp(8). > > Your choices are to either use ppp(8)'s built-in NAT and filters, or use > kernel-ppp with IPFW and NATD. Not true. As far as I can tell, these warnings are harmless - the filters will be added as normal and will take effect once the tun0 device actually is created. You can also create the tun0 device by doing something like: echo < /dev/tun0 prior to the ipfw add - the tun# devices are created at first open. Probably something like this should be added to rc.firewall. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message