From 045f6a7386f7165fd228ca2168f61990ab47a344 Mon Sep 17 00:00:00 2001 From: Logan oos Even <46396513+Logan007@users.noreply.github.com> Date: Tue, 20 Jul 2021 22:38:23 +0545 Subject: [PATCH] updated Faq.md --- doc/Faq.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/doc/Faq.md b/doc/Faq.md index 9e13e75..e05d07f 100644 --- a/doc/Faq.md +++ b/doc/Faq.md @@ -26,11 +26,7 @@ You can request the current status by just sending a new line, i.e. pressing [EN ### Is there support for multiple supernodes? -As of now, one additional supernode is supported. The additional supernode is handled in a backup-fashion: A reserve-supernode can be started if one fails. The reserve-supernode just has to be known to the edges beforehand (simply by an additional `-l ` at the edge). - -Actively using several supernodes in parallel will have the network fall apart (partitioned – some edges connected to one supernode, some to another). - -Considering these known limitations, current discussions however seem to include thoughts on increasing supernode reliability as well as fall-back mechanisms and might even shift more towards a full p2p-approach which then would not require a supernode at all, every node could be equal highly increasing network resilience. +Yes, there is. Please [read](https://github.com/ntop/n2n/blob/dev/doc/Federation.md) about how several supernodes can form a Federation to increase network resilience. ### Can a supernode listen on multiple ports? @@ -73,4 +69,4 @@ If you use a MAC or IP address that already is in use, just change those paramet If the edge prematurely has ended in a non-regular way, i.e. by killing it using `kill -9 ...` or `kill -SIGKILL ...`, it did not have a chance to un-register with the supernode which still counts the edge for online. A re-registration with the same MAC or IP address will be unsuccessful then. After two minutes or so the supernode will have forgotten. A new registration with the same parameters will be possible then. So, either wait two minutes or chose different parameters to restart with. -And, as a matter of principal, always end an edge by either pressing `CTRL` + `C` or by sending SIGTERM or SIGINT by using `kill -SIGTERM ...` or `kill -SIGINT ...`! A plain `kill ...` without `-9` will do, too. And finally, a `stop` command to the management port peacefully ends the edge as well. \ No newline at end of file +And, as a matter of principal, always end an edge by either pressing `CTRL` + `C` or by sending SIGTERM or SIGINT by using `kill -SIGTERM ...` or `kill -SIGINT ...`! A plain `kill ...` without `-9` will do, too. And finally, a `stop` command to the management port peacefully ends the edge as well.