Teamwiever Host on Torizon OS

Technical Support
1

Hello together

We are trying to our use of Toradex in our Company and therefore we are seeking to support Teamviewer as its the company standard.

If we would like to have teamviewer host module installed on Toriozon OS to get the VPN functionality running (Graphical UI is not a relevant), what would be the recommendet way to do this?

Plain and simple docker and hope it works? My assumption is having the VPN functionality from Teamviewer working from withing the container could be difficult.

Basically we use the Torizon Device as a HMI, but there are also other devices like a camera and other devices “behind” the Torizon Device inside the remote network. We want to connect to the Toradex device for beeing able to connect to the device itself offcourse, but also to connect to other devices in the network. And as Teamviewer is the company standard and has also VPN support we want to give it a try.

Thanks for your help.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

TeamViewer VPN on Torizon OS

While I understand your need to use TeamViewer as your company standard for VPN functionality, the available Toradex documentation doesn’t specifically cover TeamViewer integration(1). However, I can provide guidance on VPN solutions and container networking that are officially supported.

Officially Supported VPN Solutions

For Torizon OS, Toradex officially supports WireGuard as the primary VPN solution(1). The documentation specifically mentions:

  • WireGuard: Enabled and supported by default on Torizon OS(1)
  • OpenVPN: Available as an alternative, though not officially supported but with provided instructions(1)

Container Networking Considerations

Your concern about VPN functionality within containers is valid. For networking scenarios like yours, Torizon OS provides several options(2):

Host Network Mode

For VPN applications that need low-level network access, you might need to use host network mode(2). This mode allows containers to access the network with the same IP and configuration used by processes running natively on the host OS(2). However, this method is the least recommended since you expose the entire container networking to the outside, and you should only choose it if it is really required(2).

Inter-container Communication

If you need to connect to other devices behind your Torizon device, you can set up private networks for inter-container communication(2). This allows containers to communicate with each other while controlling external access(2).

Recommended Approach

Given your requirements for accessing both the Torizon device and other network devices:

  1. Consider WireGuard first: Since it’s officially supported and enabled by default(1)
  2. Use host network mode if necessary: For VPN functionality that requires direct network access(2)
  3. Evaluate OpenVPN as alternative: If WireGuard doesn’t meet your needs(1)

Container Implementation

If you proceed with a container-based approach for any VPN solution, you’ll likely need to use host network mode to ensure proper VPN functionality(2). Standard container networking may not provide the necessary network-level access for VPN operations.

I recommend starting with the officially supported WireGuard solution and evaluating if it can meet your company’s VPN requirements alongside or instead of TeamViewer.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Hello @buhler,

Great to see you in our community and thank you for posing your question here.
I believe you are indeed correct that this should work from a container. Please beware, that you might have to use network host in that case. I have added some resources for that below.

Accessing the device itself can be resolved by the remote access capability of Torizon. However, this does not exactly behave like a VPN as you mentioned. Information on remote access can be found at the following developer page:

Best regards,
Collin

4

@collin.tx Having the possibility to use Teamviewer in Torizon OS would be a nice option.

I don’t have any bad feelig against WireGuard (or other alternatives).

The only important thing is that the supported solution is chosen not because it’s easy to implement, but because it’s secure.

And security is something that must be considered as a continuous improvement journey.

As an example, nowadays MFA (Multi-Factor Authenticator) is a must-have.

Not clear to me if WireGuard has this option or not.

@ToradexAI can you provide details?

5

Security Considerations for VPN Solutions on Torizon OS

Thank you for raising this important security question. Let me address the security aspects of the VPN solutions available for Torizon OS.

WireGuard Security Features

Torizon OS enables and supports WireGuard by default(1). While the available documentation doesn’t specifically detail Multi-Factor Authentication (MFA) capabilities for WireGuard in the Torizon context, WireGuard itself uses modern cryptographic principles and has been designed with security as a primary focus.

OpenVPN as an Alternative

For scenarios requiring specific security features like MFA, OpenVPN might be worth considering. The documentation shows that OpenVPN is available as an alternative to WireGuard, though it’s not officially supported but instructions are provided(1). OpenVPN has extensive support for various authentication methods including MFA through plugins and integrations.

Torizon Remote Access Security

The Torizon platform includes built-in remote access capabilities that implement a zero-trust architecture(2). All provisioned devices under Torizon OS come with out-of-the-box, zero-trust architecture, SSH-based remote access with no configuration required(2). This approach provides security benefits compared to traditional VPN solutions that might require additional configuration.

Container Network Security

When implementing any VPN solution in containers, you’ll need to consider the network security implications. As mentioned in the previous response, using host network mode exposes the entire container networking to the outside, and you should only choose it if really required(3).

Recommendation for Security-First Approach

For a security-focused implementation, I recommend:

  1. Evaluate Torizon’s built-in remote access first, as it provides zero-trust architecture out of the box(2)
  2. Consider OpenVPN if you specifically need MFA capabilities, as it has broader authentication plugin support
  3. Assess WireGuard for its modern cryptographic approach, though you may need to implement MFA at the application layer

The choice between VPN solutions should indeed be based on security requirements rather than implementation ease. I recommend evaluating each solution against your specific security policies, including MFA requirements, before making a decision.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.