Add a warning a warning message when am_lighthouse is true and an an upstream lighthouse is configured.

What is Nebula?

Nebula is a scalable overlay networking tool with a focus on performance, simplicity and security. It lets you seamlessly connect computers anywhere in the world. Nebula is portable, and runs on Linux, OSX, Windows, iOS, and Android. It can be used to connect a small number of computers, but is also able to connect tens of thousands of computers.

Nebula incorporates a number of existing concepts like encryption, security groups, certificates, and tunneling, and each of those individual pieces existed before Nebula in various forms. What makes Nebula different to existing offerings is that it brings all of these ideas together, resulting in a sum that is greater than its individual parts.

Further documentation can be found here.

You can read more about Nebula here.

You can also join the NebulaOSS Slack group here.

Supported Platforms

Desktop and Server

Check the releases page for downloads or see the Distribution Packages section.

Linux - 64 and 32 bit, arm, and others
Windows
MacOS
Freebsd

Distribution Packages

Arch Linux
```
$ sudo pacman -S nebula
```
Fedora Linux
```
$ sudo dnf install nebula
```
Debian Linux
```
$ sudo apt install nebula
```
Alpine Linux
```
$ sudo apk add nebula
```
macOS Homebrew
```
$ brew install nebula
```
Docker
```
$ docker pull nebulaoss/nebula
```

Mobile

iOS
Android

Technical Overview

Nebula is a mutually authenticated peer-to-peer software defined network based on the Noise Protocol Framework. Nebula uses certificates to assert a node's IP address, name, and membership within user-defined groups. Nebula's user-defined groups allow for provider agnostic traffic filtering between nodes. Discovery nodes allow individual peers to find each other and optionally use UDP hole punching to establish connections from behind most firewalls or NATs. Users can move data between nodes in any number of cloud service providers, datacenters, and endpoints, without needing to maintain a particular addressing scheme.

Nebula uses Elliptic-curve Diffie-Hellman (ECDH) key exchange and AES-256-GCM in its default configuration.

Nebula was created to provide a mechanism for groups of hosts to communicate securely, even across the internet, while enabling expressive firewall definitions similar in style to cloud security groups.

Getting started (quickly)

To set up a Nebula network, you'll need:

1. The Nebula binaries or Distribution Packages for your specific platform. Specifically you'll need `nebula-cert` and the specific nebula binary for each platform you use.

2. (Optional, but you really should..) At least one discovery node with a routable IP address, which we call a lighthouse.

Nebula lighthouses allow nodes to find each other, anywhere in the world. A lighthouse is the only node in a Nebula network whose IP should not change. Running a lighthouse requires very few compute resources, and you can easily use the least expensive option from a cloud hosting provider. If you're not sure which provider to use, a number of us have used $5/mo DigitalOcean droplets as lighthouses.

Once you have launched an instance, ensure that Nebula udp traffic (default port udp/4242) can reach it over the internet.

3. A Nebula certificate authority, which will be the root of trust for a particular Nebula network.

./nebula-cert ca -name "Myorganization, Inc"

This will create files named ca.key and ca.cert in the current directory. The ca.key file is the most sensitive file you'll create, because it is the key used to sign the certificates for individual nebula nodes/hosts. Please store this file somewhere safe, preferably with strong encryption.

4. Nebula host keys and certificates generated from that certificate authority

This assumes you have four nodes, named lighthouse1, laptop, server1, host3. You can name the nodes any way you'd like, including FQDN. You'll also need to choose IP addresses and the associated subnet. In this example, we are creating a nebula network that will use 192.168.100.x/24 as its network range. This example also demonstrates nebula groups, which can later be used to define traffic rules in a nebula network.

./nebula-cert sign -name "lighthouse1" -ip "192.168.100.1/24"
./nebula-cert sign -name "laptop" -ip "192.168.100.2/24" -groups "laptop,home,ssh"
./nebula-cert sign -name "server1" -ip "192.168.100.9/24" -groups "servers"
./nebula-cert sign -name "host3" -ip "192.168.100.10/24"

5. Configuration files for each host

Download a copy of the nebula example configuration.

On the lighthouse node, you'll need to ensure am_lighthouse: true is set.
On the individual hosts, ensure the lighthouse is defined properly in the static_host_map section, and is added to the lighthouse hosts section.

6. Copy nebula credentials, configuration, and binaries to each host

For each host, copy the nebula binary to the host, along with config.yml from step 5, and the files ca.crt, {host}.crt, and {host}.key from step 4.

DO NOT COPY ca.key TO INDIVIDUAL NODES.

7. Run nebula on each host

./nebula -config /path/to/config.yml

Building Nebula from source

Make sure you have go installed and clone this repo. Change to the nebula directory.

To build nebula for all platforms: make all

To build nebula for a specific platform (ex, Windows): make bin-windows

See the Makefile for more details on build targets

Curve P256 and BoringCrypto

The default curve used for cryptographic handshakes and signatures is Curve25519. This is the recommended setting for most users. If your deployment has certain compliance requirements, you have the option of creating your CA using nebula-cert ca -curve P256 to use NIST Curve P256. The CA will then sign certificates using ECDSA P256, and any hosts using these certificates will use P256 for ECDH handshakes.

In addition, Nebula can be built using the BoringCrypto GOEXPERIMENT by running either of the following make targets:

make bin-boringcrypto
make release-boringcrypto

This is not the recommended default deployment, but may be useful based on your compliance requirements.

Credits

Nebula was created at Slack Technologies, Inc by Nate Brown and Ryan Huber, with contributions from Oliver Fross, Alan Lam, Wade Simmons, and Lining Wang.

	// CheckSignature verifies the signature against the provided public key
	func (nc *NebulaCertificate) CheckSignature(key ed25519.PublicKey) bool {
	b, err := proto.Marshal(nc.getRawDetails())
	if err != nil {
	return false
	}
	return ed25519.Verify(key, b, nc.Signature)
	}

slackhq / nebula Goto Github PK

nebula's Introduction

What is Nebula?

Supported Platforms

Desktop and Server

Distribution Packages

Mobile

Technical Overview

Getting started (quickly)

1. The Nebula binaries or Distribution Packages for your specific platform. Specifically you'll need nebula-cert and the specific nebula binary for each platform you use.

2. (Optional, but you really should..) At least one discovery node with a routable IP address, which we call a lighthouse.

3. A Nebula certificate authority, which will be the root of trust for a particular Nebula network.

4. Nebula host keys and certificates generated from that certificate authority

5. Configuration files for each host

6. Copy nebula credentials, configuration, and binaries to each host

7. Run nebula on each host

Building Nebula from source

Curve P256 and BoringCrypto

Credits

nebula's People

Contributors

Stargazers

Watchers

Forkers

nebula's Issues

The firewall is default deny. There is no way to write a deny rule.

Rules are comprised of a protocol, port, and one or more of host, group, or CIDR

Logical evaluation is roughly: port AND proto AND ca_sha AND ca_name AND (host OR group OR groups OR cidr)

- port: Takes 0 or any as any, a single number 80, a range 200-901, or fragment to match second and further fragments of fragmented packets (since there is no port available).

code: same as port but makes more sense when talking about ICMP, TODO: this is not currently implemented in a way that works, use any

proto: any, tcp, udp, or icmp

host: any or a literal hostname, ie test-host

group: any or a literal group name, ie default-group

groups: Same as group but accepts a list of values. Multiple values are AND'd together and a certificate would have to contain all groups to pass

cidr: a CIDR, 0.0.0.0/0 is any.

ca_name: An issuing CA name

ca_sha: An issuing CA shasum

Recommend Projects

Recommend Topics

Recommend Org

1. The Nebula binaries or Distribution Packages for your specific platform. Specifically you'll need `nebula-cert` and the specific nebula binary for each platform you use.

- port: Takes `0` or `any` as any, a single number `80`, a range `200-901`, or `fragment` to match second and further fragments of fragmented packets (since there is no port available).

code: same as port but makes more sense when talking about ICMP, TODO: this is not currently implemented in a way that works, use `any`

proto: `any`, `tcp`, `udp`, or `icmp`

host: `any` or a literal hostname, ie `test-host`

group: `any` or a literal group name, ie `default-group`

cidr: a CIDR, `0.0.0.0/0` is any.