reserved
How do I add my server as an Device as I cant open syncthing as it need to use 127.0.0.1 address instead of my machine IP ?On my main local node added ID of my second Device but can add it on my hosted remote one, any advice ?
Also does My hosted works like backup will keep my node working all time even if my local is off ?
and can you get my ID from https://transfer.sh/GRfOqv/JustMineItIDNO.bloq
and upload yours so I can be with contact with you on the EUD ?
Firstly never mess with the settings in syncthing gui - it is there purely for debug viewing. If you changed any settings there you should:
n) Refresh network
and
i) Reinitialise network
from the main menu. Syncthing is fully managed by the eudaemon.
Multi device does work but it does not yet conform exactly to the protocol specification. New devices should create a discrete device key. Currently any additional devices added will use the same device key. They already properly create independent fresh syncthing transport keys at least..
Your first device will be your master device. Any additional devices added will be set to "slave / follow" mode where they cannot form bloqs, however they will propagate your new bloqs created by your master device and collect messages from your peers - AND propagate their bloqs as well. So you will be helping all your friends when you make your second device an always on server.
If you re-enable lines 207 and 529 in eud-tui.bash then you will have the options to add multiple devices.
#echo "a) Add this device to an existing identity" #TODO re-enable in version 2 - currently too unstable
#echo "a) Add device - add additional devices that you control." #TODO re-enable in version 2 - currently too unstable
I did re-stabilise the code before launch - it is working fine. I left in disabled because it does not perfectly reflect the protocol specification.
Does daemin need any specified ports to be open for nice communication between nodes ?
This is purely related to syncthing which is the transport layer that Eudaemon currently uses. It generally works well out of the box with no configuration. It will use syncthing's public relays and discovery system.
Syncthing port information:
https://docs.syncthing.net/users/firewall.html
Discussion on syncthing NAT hole punching turn and stun:
https://forum.syncthing.net/t/a-few-questions-about-quic-hole-punching-and-stun/16490
Ok so as you said Syncthing is just for debug and better to not do anything there what if I get a loot of messegaes that others want to share some folders :
motions wants to share folder "JustMineIt mempool" (6524844D6D045FDB5AF52713B5AF9B3225078F93mempool). Share this folder?
RichManUbuntu wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?
plateau wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?
motions wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?
con1 wants to share folder "motions mempool" (FCD2DBD62FC64E8C4C7AD2833E5E5A787A726327mempool). Add new folder?
There is option to add but the folder field is empty should I just ignore that messages or add those folders ? and leave Syncthing without a touch
Ha cool! These are all people wanting to be your friend. They have imported and verified your identity bloq.
In order to complete the pairing you need to also add them as a friend in the eud menu which will lead you to import their identity bloqs.
This is because the idenity bloq contains the friend's public key. You need that to do a complete connection on the protocol. If you just accept their syncthing connection via the syncthing gui nothing will work - you may even break your node...
I will post my identity bloq in the near future and join in the fun....
The thing is they are already my friends mean most of them but syncthing shows that asks
