andreacv98
commented
1 month ago Hi @cheina97,
We originally had the idea of running the Ansible script from a centralized location. Since the machines intended to be the target of the script would most likely be behind a NAT and with a dynamic public IP (typical home network exposure to the Internet), we cannot have a static IP to use at any time to run/update Ansible. Also, we were interested in maintaining an access to the machine through an SSH connection, we would have the same problem.
Since then, the design and idea have evolved to avoid too much user configuration (such as port-forwarding on the router, etc.), and now the script is intended to be executed directly by the user in the machine, which automatically establishes peering with the central control point thanks to Liqo. Because of all these factors, we now have knowledge of “registered” machines (they have Liqo peering with the central control point) and a communication channel through which we assume we can gain SSH access to the machine.
We are thinking at this point to make the installation of DDNS optional, which would eventually become just something useful to identify the machine in the Internet network, outside the Liqo communication channel.
As you can see, this part is not entirely clear and we are still trying to figure out the best way to achieve our goals, so any feedback is welcome!
cheina97
Could someone provide insight into why a DDNS setup is recommended or required? Understanding the underlying reasons would help in grasping its importance and potential implications.