Nebula - Revision history

Yesaslrocks: added node/client config for nebula mesh network.

2024-12-30T21:31:53Z

added node/client config for nebula mesh network.

@@ Line 10: / Line 10: @@
-A simple configuration may look like:
+A simple lighthouse configuration may look like:
 <syntaxhighlight lang="nix">
@@ Line 23: / Line 23: @@
 </syntaxhighlight>
 The configuration files in `/etc/nebula` need to be readable by the Nebula service:

Mic92: /* Lighthouse Node */

2024-10-30T22:30:34Z

Lighthouse Node

← Older revision		Revision as of 22:30, 30 October 2024
Line 15:		Line 15:
	environment.systemPackages = with pkgs; [ nebula ];		environment.systemPackages = with pkgs; [ nebula ];
	services.nebula.networks.mesh = {		services.nebula.networks.mesh = {
	enable = ~~false~~;		enable = true;
	isLighthouse = true;		isLighthouse = true;
	cert = "/etc/~~nebulanode~~.crt";		cert = "/etc/nebula/beacon.crt"; # The name of this lighthouse is beacon.
	key = "/etc/nebula/~~node~~.key";		key = "/etc/nebula/beacon.key";
	ca = "/etc/nebula/ca.crt";		ca = "/etc/nebula/ca.crt";
	};		};
			</syntaxhighlight>


			The configuration files in `/etc/nebula` need to be readable by the Nebula service:

			<syntaxhighlight lang="bash">
			sudo chmod --reference /etc/nix /etc/nebula
			sudo chmod --reference /etc/nix/nix.conf /etc/nebula/*
	</syntaxhighlight>		</syntaxhighlight>

Klinger at 21:15, 24 April 2024

2024-04-24T21:15:36Z

← Older revision		Revision as of 21:15, 24 April 2024
Line 36:		Line 36:
	Of these four files produced, you should do as much as you can to keep <code>ca.key</code> secure.		Of these four files produced, you should do as much as you can to keep <code>ca.key</code> secure.

	~~(...more coming soon...)~~		[[Category:Networking]]

Mic92: fix links

2024-04-01T13:49:27Z

fix links

← Older revision		Revision as of 13:49, 1 April 2024
Line 7:		Line 7:
	In Nebula, a "lighthouse" is a signaling node accessible through a public IP address, using UDP port 4242.		In Nebula, a "lighthouse" is a signaling node accessible through a public IP address, using UDP port 4242.

	Because you're likely using a cloud server option for your lighthouse, there is a chance you'll be unable to use NixOS on that node. Double check [~~https://nixos.wiki/wiki/~~NixOS_friendly_hosters your options for running NixOS in the cloud], or choose a secondary distribution and look for the <code>nebula</code> package, and go through [https://nebula.defined.net/docs/guides/quick-start/ the Quick Start guide].		Because you're likely using a cloud server option for your lighthouse, there is a chance you'll be unable to use NixOS on that node. Double check the [[NixOS_friendly_hosters\| NixOS friendly hosters article]] your options for running NixOS in the cloud], or choose a secondary distribution and look for the <code>nebula</code> package, and go through [https://nebula.defined.net/docs/guides/quick-start/ the Quick Start guide].

imported>C4lliope at 07:03, 25 December 2023

2023-12-25T07:03:09Z

← Older revision		Revision as of 07:03, 25 December 2023
Line 5:		Line 5:
	== Lighthouse Node ==		== Lighthouse Node ==

	In Nebula, a "lighthouse" is a signaling node accessible through a public IP address, using UDP port 4242. A simple configuration may look like:		In Nebula, a "lighthouse" is a signaling node accessible through a public IP address, using UDP port 4242.

			Because you're likely using a cloud server option for your lighthouse, there is a chance you'll be unable to use NixOS on that node. Double check [https://nixos.wiki/wiki/NixOS_friendly_hosters your options for running NixOS in the cloud], or choose a secondary distribution and look for the <code>nebula</code> package, and go through [https://nebula.defined.net/docs/guides/quick-start/ the Quick Start guide].


			A simple configuration may look like:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
Line 18:		Line 23:
	</syntaxhighlight>		</syntaxhighlight>

	Because you're likely using a VPS server for your lighthouse, there is a chance you'll be unable to use NixOS on that node. Check the package manager of your distribution for the <code>nebula</code> package, and go through the Quick Start guide: https://nebula.defined.net/docs/guides/quick-start/

	Here is a quick process for making a certificate authority (<code>ca</code>) and a certificate for a lighthouse node, called "<code>beacon</code>".		Here is a quick process for making a certificate authority (<code>ca</code>) and a certificate for a lighthouse node, called "<code>beacon</code>".
Line 33:		Line 37:

	(...more coming soon...)		(...more coming soon...)
	~~<syntaxhighlight lang="nix">~~
	~~</syntaxhighlight>~~
	~~<syntaxhighlight lang="nix">~~
	~~</syntaxhighlight>~~
	~~<syntaxhighlight lang="nix">~~
	~~</syntaxhighlight>~~

imported>C4lliope: Raise concerns around NAT and port forwarding.

2023-12-25T06:48:02Z

Raise concerns around NAT and port forwarding.

← Older revision		Revision as of 06:48, 25 December 2023
Line 1:		Line 1:
	[https://github.com/slackhq/nebula Nebula] is a meshing overlay network made as an open-source program by Slack. You can seamlessly mesh hundreds, thousands, or more machines across the globe, using minimal changes to your process.		[https://github.com/slackhq/nebula Nebula] is a meshing overlay network made as an open-source program by Slack. You can seamlessly mesh hundreds, thousands, or more machines across the globe, using minimal changes to your process.

	~~This guide assumes there are~~ a ~~couple~~ of ~~Nix machines you'd like to connect, though you can go through~~ the "~~Lighthouse Node~~" ~~section on~~ a ~~single~~ machine as a ~~sample~~.		Nebula runs by assigning a number of nodes the role of "lighthouse". These nodes should be assigned a public global IP address - any kind of NAT or port forwarding is likely to render your lighthouses useless. A minimal $5/mo cloud machine is good enough to run as a lighthouse node, and luckily no traffic passes through those nodes; they only broker the peer-to-peer connections of the other nodes in your mesh.

	== Lighthouse Node ==		== Lighthouse Node ==
Line 12:		Line 12:
	enable = false;		enable = false;
	isLighthouse = true;		isLighthouse = true;
	cert = "/~~home~~/~~user/mesh/node~~.crt";		cert = "/etc/nebulanode.crt";
	key = "/~~home~~/~~user/mesh~~/node.key";		key = "/etc/nebula/node.key";
	ca = "/~~home/user~~/~~mesh~~/ca.crt";		ca = "/etc/nebula/ca.crt";
	};		};
	</syntaxhighlight>		</syntaxhighlight>

	~~Please use~~ your ~~normal login username~~, ~~or choose some other place~~ on your ~~disk as you like~~.		Because you're likely using a VPS server for your lighthouse, there is a chance you'll be unable to use NixOS on that node. Check the package manager of your distribution for the <code>nebula</code> package, and go through the Quick Start guide: https://nebula.defined.net/docs/guides/quick-start/

	~~Before enabling the service, do you see those certificates referenced under~~ <code>~~cert~~</code>, <code>~~key~~</code>~~, and <code>ca</code>? They're easy enough to make.~~		Here is a quick process for making a certificate authority (<code>ca</code>) and a certificate for a lighthouse node, called "<code>beacon</code>".

	~~Be sure you make the certs on the filepath used in your nix config, and use the IP you'd like your lighthouse node to be assigned~~.

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	> mkdir ~/mesh && cd ~/mesh		> mkdir ~/mesh && cd ~/mesh
	> nebula-cert ca -name mesh		> nebula-cert ca -name mesh
	> nebula-cert sign -ca-crt ./ca.crt -ca-key ./ca.key -name ~~node~~ -ip 10.0.0.~~180~~		> nebula-cert sign -ca-crt ./ca.crt -ca-key ./ca.key -name beacon -ip 10.0.0.1
	> ls		> ls
	ca.crt ca.key node.crt node.key		ca.crt ca.key node.crt node.key
	</syntaxhighlight>		</syntaxhighlight>

	Of these four, you should do as much as you can to keep <code>ca.key</code> secure.		Of these four files produced, you should do as much as you can to keep <code>ca.key</code> secure.

	(...more coming soon...)		(...more coming soon...)

imported>C4lliope: Begin describing Nebula.

2023-12-22T00:06:04Z

Begin describing Nebula.

New page

[https://github.com/slackhq/nebula Nebula] is a meshing overlay network made as an open-source program by Slack. You can seamlessly mesh hundreds, thousands, or more machines across the globe, using minimal changes to your process.

This guide assumes there are a couple of Nix machines you'd like to connect, though you can go through the "Lighthouse Node" section on a single machine as a sample.

== Lighthouse Node ==

In Nebula, a "lighthouse" is a signaling node accessible through a public IP address, using UDP port 4242. A simple configuration may look like:

<syntaxhighlight lang="nix">
environment.systemPackages = with pkgs; [ nebula ];
services.nebula.networks.mesh = {
enable = false;
isLighthouse = true;
cert = "/home/user/mesh/node.crt";
key = "/home/user/mesh/node.key";
ca = "/home/user/mesh/ca.crt";
};
</syntaxhighlight>

Please use your normal login username, or choose some other place on your disk as you like.

Before enabling the service, do you see those certificates referenced under <code>cert</code>, <code>key</code>, and <code>ca</code>? They're easy enough to make.

Be sure you make the certs on the filepath used in your nix config, and use the IP you'd like your lighthouse node to be assigned.

<syntaxhighlight lang="bash">
> mkdir ~/mesh && cd ~/mesh
> nebula-cert ca -name mesh
> nebula-cert sign -ca-crt ./ca.crt -ca-key ./ca.key -name node -ip 10.0.0.180
> ls
ca.crt ca.key node.crt node.key
</syntaxhighlight>

Of these four, you should do as much as you can to keep <code>ca.key</code> secure.

(...more coming soon...)
<syntaxhighlight lang="nix">
</syntaxhighlight>
<syntaxhighlight lang="nix">
</syntaxhighlight>
<syntaxhighlight lang="nix">
</syntaxhighlight>