I've noticed that every time I specify a member's IPv4 in the console, the modified member device loses connection. It only regains connectivity after restarting ZeroTier on that device to obtain a new IP. This doesn't happen with the ztncui image. Of course, your project can automatically generate planets, which is more powerful and convenient.
I tried to make the main controller join the network by entering the container and using the command zerotier-cli join xxxx. It did join and was assigned an IP in the console. I then restarted ZeroTier inside the container, but no new network interface appeared in the container, and it didn't obtain an IP. However, listpeers can show the online information of other nodes.
I've noticed that every time I specify a member's IPv4 in the console, the modified member device loses connection. It only regains connectivity after restarting ZeroTier on that device to obtain a new IP. This doesn't happen with the ztncui image. Of course, your project can automatically generate planets, which is more powerful and convenient.
I tried to make the main controller join the network by entering the container and using the command zerotier-cli join xxxx. It did join and was assigned an IP in the console. I then restarted ZeroTier inside the container, but no new network interface appeared in the container, and it didn't obtain an IP. However, listpeers can show the online information of other nodes.