[EMAIL PROTECTED] writes: > It seems to work ! I have not found any mistake.
cool > A few comments: > > 1. I would recommend to add parameter for the name of local certificate. > Now I need different certificate for every server type entry. I'm not sure I understand. The local name is used exactly for that. If localname is linuxbox then : - two files are created /etc/openvpn/tls-linuxbox.conf and /etc/openvpn/linuxbox.up - this is not all because the above name will also be used for the local certificate. So, in this case this will assume that the local certificates are linuxbox.crt and linuxbox.key > 2. Option for use tap instead of tun device. this is ok now > 3. To be able to add tun or tap device to the bridge interface (to > configure openvpn bridging). I will have a look at this. > 4. In openvpn entry to add field for any optional parameters (they will be > appended to created .conf file). The architecture is quite limited here. tap0, tap1, tap2 and tap+ are now avaliable. If you use 4 tunnels ... with special zones for each if them ... well this is not possible with this interface. tap+ and tun+ is used for all tap0,1,2,3 ... > 5. In zones interfaces configuration to allow use any used tap or tun > device (not only tap0, tap1 and tun0). this should be ok now .. new packages are available now. thank you, -- Florin http://www.mandrakesoft.com http://people.mandrakesoft.com/~florin/
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
