|
|
Hi, JP M, JP M disse: > Hi, > I am sort of following up expecting someone can bring > me light on the way tun device creation is handled in > recent (debian ?) kernels. > **Obviously this is not an OpenVPN issue** > > I use the debian network configuration scheme in > /etc/network : ./interfaces, ./pre-up.d, ... > > Some time ago I was using the ethertap module to have > tun/tap capability. At that time I was able to write > in the ./interfaces file something like: > > auto tap0 > iface tap0 static > address X.X.X.X > ... > > And starting the network would make tap0 come alive. > > Since I moved to the tun module, this is not true > anymore in my experience. My current turnaround is > call OpenVPN for rescue adding stanzas like: > > ... > pre-up /sbin/run_openvpns_mktun.sh tap0 > post-down /sbin/run_openvpns_deltun.sh tap0 > > I am using tap devices for running apache ip-based > virtual hosts (and for openvpn of course). Well, I use to manage some VirtualHost entries binding the VirtualHost ip number to an alias, as eth0:0, etho:1, eth0:2 ... As in: ifconfig eth0 netmask 255.255.255.0 192.168.10.1 ifconfig eth0:0 netmask 255.255.255.0 192.168.10.2 ... > If it is totally sick to use tun/tap devices outside > openvpn, uml and the like, just let me know :-) > > --JP > Note also that all this stuff is handled by config files at boot time. HTH, RSalles -- "A well-written program is its own heaven; a poorly-written program is its own hell." TAO of Programming - Book 4 ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |