![]() You can even use an OpenVPN2 client against an OpenVPN3 server and vice-versa - they are protocol compatible, so we support both OpenVPN2 and OpenVPN3 at the same time. OpenVPN3 is a new generation program that you don't have to use. The last update it got was like 2 weeks ago. It supports bridging and will continue to do so. My point of view is that your application should learn how to do IP packets, that's where it should actually be solved. OpenVPN2 bridging is in effect a workaround for the inherent problem that your application has - it doesn't know how to send IP packets that can travel over the Internet so you use OpenVPN2's bridging capability to work around this issue. The data sent and received even if it is not IP packets is encapsulated into IP packets so that it can be transported over the Internet, which actually solves or rather works around the problem that your application has at its very heart. It can even bridge entire networks together. It can bridge remote VPN clients to a local network. Fortunately for you, OpenVPN2 supports this. Layer 2 is part of the OSI model that explains how network layers work and means that it works at a lower more basic level than Layer 3 IP packets. What you have however is an application that does not use IP packets, but something else, which will apparently only work on a layer 2 network. And then there is no problem and you can use OpenVPN3 just fine without bridging. If the primary use-case of this program is indeed to use it over the Internet, it should be using IP packets. So let me highlight that point you are using a program that does not use IP packets over a network that transports IP packets. And you and your group of fellow audio engineers use this program over the Internet, which is primarily an IP network. You have an application that does not use IP packets. Let me try to show my point of view on this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |