Hello, Today there are lots of VPN implementations, each having their strengths and weaknesses. In particular, OpenVPN has focussed on creating tunnels using standards such as SSL/TLS and ESP and provides better security than many other VPN implementations. Tinc on the other hand is probably the only VPN daemon that handles multiple tunnels on one tun/tap device, using built-in routing. In order to allow both projects (and maybe others) to combine their efforts in a manageable way, their should be a standardised API, so that code can be reused without having to change it. You can find a concept here: http://sliepen.eu.org/~guus/vpnsplit.html This is by no means finished, your input is greatly appreciated. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus@sliepen.eu.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://brouwer.uvt.nl/pipermail/tinc-devel/attachments/20031027/5d9ce0fe/attachment.pgp