-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
FAQ #31
Comments
What is the root node, isn't that centralisation? How does my traffic move on the map? Why do I only have one link while I have more peers? |
Why are there so many public/private keys in yggdrasil.conf? What do they do / How do they differ? |
Do I need a firewall with Yggdrasil? What is peering? How do I get puurs? How should I pick them, where should they be located? How many do I need? How does autopeering work? |
Optimal node amount and peering policy was discussed again and I found these links, but they should be in FAQ |
I hope I got to at least to the correct direction 😁
The root node is the node with the strongest key and the network is arranged around it. If it changes, there will be a moment while the network readjusts.
The map only shows the tree which is the worst case scenario. Generally the traffic jumps to the closest peer to the destination taking shortcuts across the tree.
Yggdrasil includes a session firewall that is disabled by default, but running an IPv6 firewall is generally recommended or all ports on your system may be open to the network.
Peers are connections between nodes in the network. You can find public peers on https://github.com/yggdrasil-network/public-peers, three to four would be a good amount and they should be located as close as possible. It's recommended that public peers peer with each other. |
(This is an untested configuration.) |
I think we should work on improving the FAQ page. We tend to repeat ourselves a lot when answering people's questions, and it would be good if we had that in shape where we could point people to it first.
Maybe we can collect questions (and start working on answers) as comments to this issue.
The text was updated successfully, but these errors were encountered: