[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Web openvpn.net

Re: [Openvpn-users] tap device at boot time

  • Subject: Re: [Openvpn-users] tap device at boot time
  • From: Willy Offermans <Willy@xxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 16 Mar 2007 08:53:32 +0100

On Thu, Mar 15, 2007 at 11:50:00PM +0900, Hajimu UMEMOTO wrote:
> Hi,
> >>>>> On Thu, 15 Mar 2007 15:33:22 +0100
> >>>>> Willy Offermans <Willy@xxxxxxxxxxxxxxxxxxx> said:
> Willy> Thank you for the information. So this is _not_ the way to go with
> Willy> FreeBSD 6.1-RELEASE #5. Naturally the following question
> Willy> would be: how then to proceed with FreeBSD 6.1-RELEASE? and most
> Willy> important is cloned_interfaces="tap0" generally meant to do the things I have
> Willy> asked for: initialisation and configuration of a tap device during boot.
> The cloned_interfaces variable is for a cloned interface.  The tap is
> not a cloned interface on 6.1-RELEASE, yet.  However, still you can
> create tap0 by opening /dev/tap0.  Try putting
> 	cp /dev/null /dev/tap0
> into your /etc/rc.early.
> Sincerely,

Hello Hajimu,

If I load the tap kernel_module, then it is quite obvious that I want to use the tap
device. Why should I perform `cp /dev/null /dev/tap0` to create tap0.
It does not sound logic. Is this the same for, let say, the xl0 device?
Again the fundamental question why is the handling of the tap device so
much different from the handling of a normal NIC? One would expect a
similar procedure for initialising NICs! Please correct me if I'm too

To be more practical, where should I put `cp /dev/null /dev/tap0`? I
don't have anything like /etc/rc.early. Should there be a trailing dot?
Should I create rc.early? Probably I need to google again and maybe to
read the handbook again. 

Met vriendelijke groeten,
With kind regards,
Mit freundlichen Gruessen,
De jrus wah,


W.K. Offermans
Home:   +31 45 544 49 44
Mobile: +31 653 27 16 23
e-mail: Willy@xxxxxxxxxxxxxxxxxxx

                                       Powered by ....

                                           \/  \ ^

OpenVPN mailing lists