I heard about it and would like to wish your country good luck in this hard situation!
There are no restrictions. You may use flag --port during configuration by tinc-boot
You may restrict connections from home to node 1, from node 1 to node 2 and so on by removing ConnectTo parameter in host file. However you also should to disable tinc-boot because it will overwrite configuration. So in this case tinc-boot will be used only as configuration wizard) However, I should remind, that it could be useful only in case you are caring of traffic detection, because tinc by itself can detect blocked connections (edges) and re-route traffic automatically.
Not sure that I can help with it, however you only need to allow udp and tcp traffic for specified port chosen on step 1
Donating always welcome)
ETH: 0xA4eD4fB5805a023816C9B55C52Ae056898b6BdBC
BTC: bc1qlj4v32rg8w0sgmtk8634uc36evj6jn3d5drnqy
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I heard about it and would like to wish your country good luck in this hard situation!
--portduring configuration bytinc-boothometonode 1, fromnode 1tonode 2and so on by removingConnectToparameter in host file. However you also should to disabletinc-bootbecause it will overwrite configuration. So in this casetinc-bootwill be used only as configuration wizard) However, I should remind, that it could be useful only in case you are caring of traffic detection, becausetincby itself can detect blocked connections (edges) and re-route traffic automatically.0xA4eD4fB5805a023816C9B55C52Ae056898b6BdBCbc1qlj4v32rg8w0sgmtk8634uc36evj6jn3d5drnqy