Huzzah! About a month after the grand unveiling of DxConnect, we have now hosted our first webinar presentation covering the topic.
We’ve listed all the questions that were asked and the answers Connor provided below. I highly encourage you to click through and view the PDF in question #8. That comprises a lot of the meat of the story and why DH2i’s SDP approach is so unique and effective compared to other industry offerings.
- Does it support IPv6?
Yes, all the examples you saw today were IPv4, but DxOdyssey also supports IPv6.
- If we have a direct link between our sites and a public cloud, would we still need something like this?
If you have a direct link, you can certainly layer this on top of that infrastructure to provide more granular tunnels than just having things wide open and having to set up various rules to restrict access. You can add this for more robust security between sites and clouds.
- Is there a contract term or do you pay for usage?
Licensing involves a 1-year term, and it functions like a subscription model. You can either license DxOdyssey and run as many clients as you want, or you can license DxOdyssey and license for each one of your users. If you have a lot of users, it’s easiest to just license those DxOdyssey gateways and run unlimited users.
- How are you administering the gateways/routers?
The gateways themselves are just physical or virtual machines running Windows or Linux. It’s up to you because it’s all software based. You can administer using the DxOdyssey UI, or you can do things via CLI and scripting. You can also interact with it using the API. We also have a client version of the admin console that you can use to administer the gateways remotely as well.
- Does it still work if my gateways have no access to the Internet?
No, your gateways have to have access to the Internet so that they can communicate with one another and to register with the matchmaking service.
- Do clients need to install something on their machines to access these tunnels?
It depends. If your clients are on-premises where one of the gateways resides they do not need to install anything—as seen in the demo where the Lab4 machine simply went out and hit the Lab5 machine. So if you have network connectivity between your users and one of your gateways you don’t necessarily need to install anything. However, in the case of a remote user you do need to install the DxConnect agent on those machines.
- What are the installation prerequisites for a DxOdyssey gateway?
For Windows you will need .NET 4.5 to run the software, and on Linux you need .NET Core 2.1 in order to install on a Linux box. As far as Linux flavors, we support Red Hat and Red Hat derivatives such as CentOS. You can also run the gateway software on Ubuntu.
- What is the difference between DxOdyssey and DxConnect, and any other SDP vendors out there?
Click here to view the informative PDF that Connor shared to answer this question.
- How would you generally size the gateway machine? I know you can scale up or out, but where is a good starting place?
You can start small, so any servers of any particular class would work just fine. I’d say start around 3.5 gigs of RAM and that should be plenty of performance to start. That would start you with more horsepower than any VPN router anyway, and you can scale from there as needed.
Thanks for taking the time to read through the blog today. You can view the full recording of the webinar at: https://dh2i.com/webinars/dxconnect-bridging-gap-zero-trust-security-amidst-changing-network-landscape/.