Date: Thu, 20 Jun 2002 09:07:52 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: IPFW rules on tunX devices Message-ID: <20020620090752.E438@gsmx07.alcatel.com.au> In-Reply-To: <20020619010325.A29725@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Wed, Jun 19, 2002 at 01:03:26AM -0700 References: <20020619165721.B438@gsmx07.alcatel.com.au> <20020619010325.A29725@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-Jun-19 01:03:26 -0700, Brooks Davis <brooks@one-eyed-alien.net> wrote: >On Wed, Jun 19, 2002 at 04:57:21PM +1000, Peter Jeremy wrote: >> In 4.6-RELEASE, the tun devices are created on demand and so tun0 >> doesn't exist don't exist when the firewall rules are added. Other >> than starting ppp(8), how do I create tun0? I thought >> ifconfig tun0 create >> would work, but that returns: >> ifconfig: SIOCIFCREATE: Invalid argument ... >On current the following signficantly less gross shell >works: > >echo "" >> /dev/tun0 I did some further experimenting and independently came to the same conclusion. I also think this is a hack. >IMO, the long term solution it to fix the tun(4) driver to use interface >cloning like gif(4) so you can do "ifconfig tun0 create" as necessicary. Agreed. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020620090752.E438>