Dear Turris community,
I would like to operate with my Turris Omnia (access applications, manage virtual machines) remotely.
My first Turris Omnia has public IPv4 address and OpenVPN works perfectly.
My second Turris Omnia elsewhere doesn’t have a public IPv4.
My question is simple: What are the options to bypass this limitation?
Some possible solutions (I have no idea if this going to work, please, correct me if not):
Port redirections
- Server usually sits on port 1194, but it can be changed in reForis web interface.
- You can forward traffic for certain port to whatever port is used by OpenVPN server on your Omnia.
- You need to update the line
remote ISP_public_IP Port_forwared_by_ISP
, e.g.,11.22.33.44 54321
. - Not tested by me, theoretically it should work.
IPv6 public IP
- My ISP should have enough IPv6 addresses.
- Does OpenVPN server works with IPv6 only? Is the connection somehow limited?
1st party VPN with public IP via OpenVPN
- If you have an access to another Turris Omnia with public IP, you can connect it via OpenVPN.
- Omnia with public IP will be a server.
- Omnia with non-public IP will be a client.
- Be aware of traffic setup. Server could dictate to route all client traffic to VPN, so all client of non-public Omnia could be redirected to VPN. This can be address with WireGuard.
3rd party DDNS service + CLI client for LXC
Maybe there is a DDNS service that has a CLI client that could be automatically connected after start and accessed from outside and used as an access point for LAN operated by Omnia.Maybe this is a complete nonsense.Possible security risk.