Misunderstading instructions

[bmullan]

The README says:

2. On the first node:

# ./wesher

Running the command above on a terminal will currently output a generated cluster key as follows:

new cluster key generated: XXXXX

Note: the created key will only be shown if running on a terminal, to avoid keys leaking via logs.

3. Lastly, on any further node:

# wesher --cluster-key XXXXX --join x.x.x.x

Where XXXXX is the base64 encoded 256 bit key printed by the step above, and x.x.x.x is the hostname or IP of any of the nodes already joined to the mesh cluster.

I have wireguard installed on all 3 nodes.

• wget installed wesher
• chmod a+x ./wesher
• sudo ./wesher
• saved key

But Step #3 above stumps me... If I just generated the "cluster-key" how can the next step say:

# wesher --cluster-key XXXXX --join x.x.x.x

Where XXXXX is the base64 encoded 256 bit key printed by the step above, and x.x.x.x is the hostname or IP of any of the nodes already joined to the mesh cluster.

How do you get a first node into the cluster? so additional nodes can be added like that?

Is step #2 supposed to to that? When I run:

# ./wesher

I get the...

new cluster key generated: XXXXX

but the command never completes or goes back to a prompt?

[costela]

the command never completes or goes back to a prompt?

yes, because wesher is a daemon and currently doesn't have any separate CLI tool. When you start it, you effectively just started your cluster with a single node (the current one).

The quick start is just supposed to show how wesher generally works. A "proper" installation probably also entails integrating it with whatever distribution you are using by, e.g., using the provided systemd integration.

[bmullan]

@costela
thanks.. that "the provided systemd integration" I hadn't looked at yet because I was just testing

However, as I said in my 1st post.. when I execute:

# ./wesher

Running the command above on a terminal will currently output a generated cluster key as follows:

new cluster key generated: XXXXX

On my machine(s) I get the new cluster key generated as above but it never comes back to the Terminal prompt. Cursor just keeps blinking after XXXXX

[costela]

Yes, and as I said: wesher is a daemon. It's meant to run indefinitely. Compare it with, for instance, openvpn: if you start in on the console, it runs for as long as the VPN connection is up, and if you kill it the connection breaks. Under realistic usage, it's meant to be started/managed by a different process, like your desktop session manager or systemd.

[bmullan]

okay ... now I understand what you meant... sorry but thanks for the answer!

…

On Fri, Jan 10, 2020 at 11:27 AM Leo Antunes ***@***.***> wrote: Yes, and as I said: wesher is a daemon. It's *meant* to run indefinitely. Compare it with, for instance, openvpn: if you start in on the console, it runs for as long as the VPN connection is up, and if you kill it the connection breaks. Under realistic usage, it's meant to be started/managed by a different process, like your desktop session manager or systemd. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16?email_source=notifications&email_token=AAM23JY64IBJSSR5P7TO2DDQ5COWTA5CNFSM4KEQYZPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIUOKMQ#issuecomment-573105458>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM23JYLWPWCQL2JRXAD7PLQ5COWTANCNFSM4KEQYZPA> .