[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-4846":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":27,"readmeContent":28,"aiSummary":29,"trendingCount":16,"starSnapshotCount":16,"syncStatus":30,"lastSyncTime":31,"discoverSource":32},4846,"nebula","slackhq\u002Fnebula","slackhq","A scalable overlay networking tool with a focus on performance, simplicity and security","",null,"Go",17391,1146,236,51,0,1,17,93,7,88.98,"MIT License",false,"master",true,[],"2026-06-12 04:00:23","## What is Nebula?\nNebula is a scalable overlay networking tool with a focus on performance, simplicity and security.\nIt lets you seamlessly connect computers anywhere in the world. Nebula is portable, and runs on Linux, OSX, Windows, iOS, and Android.\nIt can be used to connect a small number of computers, but is also able to connect tens of thousands of computers.\n\nNebula incorporates a number of existing concepts like encryption, security groups, certificates,\nand tunneling.\nWhat makes Nebula different to existing offerings is that it brings all of these ideas together,\nresulting in a sum that is greater than its individual parts.\n\nFurther documentation can be found [here](https:\u002F\u002Fnebula.defined.net\u002Fdocs\u002F).\n\nYou can read more about Nebula [here](https:\u002F\u002Fmedium.com\u002Fp\u002F884110a5579).\n\nYou can also join the NebulaOSS Slack group [here](https:\u002F\u002Fjoin.slack.com\u002Ft\u002Fnebulaoss\u002Fshared_invite\u002Fzt-39pk4xopc-CUKlGcb5Z39dQ0cK1v7ehA).\n\n## Supported Platforms\n\n#### Desktop and Server\n\nCheck the [releases](https:\u002F\u002Fgithub.com\u002Fslackhq\u002Fnebula\u002Freleases\u002Flatest) page for downloads or see the [Distribution Packages](https:\u002F\u002Fgithub.com\u002Fslackhq\u002Fnebula#distribution-packages) section.\n\n- Linux - 64 and 32 bit, arm, and others\n- Windows\n- MacOS\n- Freebsd\n\n#### Distribution Packages\n\n- [Arch Linux](https:\u002F\u002Farchlinux.org\u002Fpackages\u002Fextra\u002Fx86_64\u002Fnebula\u002F)\n    ```sh\n    sudo pacman -S nebula\n    ```\n\n- [Fedora Linux](https:\u002F\u002Fsrc.fedoraproject.org\u002Frpms\u002Fnebula)\n    ```sh\n    sudo dnf install nebula\n    ```\n\n- [Debian Linux](https:\u002F\u002Fpackages.debian.org\u002Fsource\u002Fstable\u002Fnebula)\n    ```sh\n    sudo apt install nebula\n    ```\n\n- [Alpine Linux](https:\u002F\u002Fpkgs.alpinelinux.org\u002Fpackages?name=nebula)\n    ```sh\n    sudo apk add nebula\n    ```\n\n- [macOS Homebrew](https:\u002F\u002Fgithub.com\u002FHomebrew\u002Fhomebrew-core\u002Fblob\u002FHEAD\u002FFormula\u002Fn\u002Fnebula.rb)\n    ```sh\n    brew install nebula\n    ```\n\n- [Docker](https:\u002F\u002Fhub.docker.com\u002Fr\u002Fnebulaoss\u002Fnebula)\n    ```sh\n    docker pull nebulaoss\u002Fnebula\n    ```\n\n#### Mobile ([source code](https:\u002F\u002Fgithub.com\u002FDefinedNet\u002Fmobile_nebula))\n\n- [iOS](https:\u002F\u002Fapps.apple.com\u002Fus\u002Fapp\u002Fmobile-nebula\u002Fid1509587936?itsct=apps_box&itscg=30200)\n- [Android](https:\u002F\u002Fplay.google.com\u002Fstore\u002Fapps\u002Fdetails?id=net.defined.mobile_nebula&pcampaignid=pcampaignidMKT-Other-global-all-co-prtnr-py-PartBadge-Mar2515-1)\n\n## Technical Overview\n\nNebula is a mutually authenticated peer-to-peer software-defined network based on the [Noise Protocol Framework](https:\u002F\u002Fnoiseprotocol.org\u002F).\nNebula uses certificates to assert a node's IP address, name, and membership within user-defined groups.\nNebula's user-defined groups allow for provider agnostic traffic filtering between nodes.\nDiscovery nodes (aka lighthouses) allow individual peers to find each other and optionally use UDP hole punching to establish connections from behind most firewalls or NATs.\nUsers can move data between nodes in any number of cloud service providers, datacenters, and endpoints, without needing to maintain a particular addressing scheme.\n\nNebula uses Elliptic-curve Diffie-Hellman (`ECDH`) key exchange and `AES-256-GCM` in its default configuration.\n\nNebula 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.\n\n## Getting started (quickly)\n\n**Don't want to manage your own PKI and lighthouses?** [Managed Nebula](https:\u002F\u002Fwww.defined.net\u002F) from Defined Networking handles all of this for you.\n\nTo set up a Nebula network, you'll need:\n\n#### 1. The [Nebula binaries](https:\u002F\u002Fgithub.com\u002Fslackhq\u002Fnebula\u002Freleases) or [Distribution Packages](https:\u002F\u002Fgithub.com\u002Fslackhq\u002Fnebula#distribution-packages) for your specific platform. Specifically you'll need `nebula-cert` and the specific nebula binary for each platform you use.\n\n#### 2. (Optional, but you really should..) At least one discovery node with a routable IP address, which we call a lighthouse.\n\nNebula 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 $6\u002Fmo [DigitalOcean](https:\u002F\u002Fdigitalocean.com) droplets as lighthouses.\n\nOnce you have launched an instance, ensure that Nebula udp traffic (default port udp\u002F4242) can reach it over the internet.\n\n#### 3. A Nebula certificate authority, which will be the root of trust for a particular Nebula network.\n\n```sh\n.\u002Fnebula-cert ca -name \"Myorganization, Inc\"\n```\n\nThis 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\u002Fhosts. Please store this file somewhere safe, preferably with strong encryption.\n\n**Be aware!** By default, certificate authorities have a 1-year lifetime before expiration. See [this guide](https:\u002F\u002Fnebula.defined.net\u002Fdocs\u002Fguides\u002Frotating-certificate-authority\u002F) for details on rotating a CA.\n\n#### 4. Nebula host keys and certificates generated from that certificate authority\n\nThis 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\u002F24 as its network range. This example also demonstrates nebula groups, which can later be used to define traffic rules in a nebula network.\n```sh\n.\u002Fnebula-cert sign -name \"lighthouse1\" -ip \"192.168.100.1\u002F24\"\n.\u002Fnebula-cert sign -name \"laptop\" -ip \"192.168.100.2\u002F24\" -groups \"laptop,home,ssh\"\n.\u002Fnebula-cert sign -name \"server1\" -ip \"192.168.100.9\u002F24\" -groups \"servers\"\n.\u002Fnebula-cert sign -name \"host3\" -ip \"192.168.100.10\u002F24\"\n```\n\nBy default, host certificates will expire 1 second before the CA expires. Use the `-duration` flag to specify a shorter lifetime.\n\n#### 5. Configuration files for each host\n\nDownload a copy of the nebula [example configuration](https:\u002F\u002Fgithub.com\u002Fslackhq\u002Fnebula\u002Fblob\u002Fmaster\u002Fexamples\u002Fconfig.yml).\n\n* On the lighthouse node, you'll need to ensure `am_lighthouse: true` is set.\n\n* On the individual hosts, ensure the lighthouse is defined properly in the `static_host_map` section, and is added to the lighthouse `hosts` section.\n\n\n#### 6. Copy nebula credentials, configuration, and binaries to each host\n\nFor 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.\n\n**DO NOT COPY `ca.key` TO INDIVIDUAL NODES.**\n\n#### 7. Run nebula on each host\n\n```sh\n.\u002Fnebula -config \u002Fpath\u002Fto\u002Fconfig.yml\n```\n\nFor more detailed instructions, [find the full documentation here](https:\u002F\u002Fnebula.defined.net\u002Fdocs\u002F).\n\n## Building Nebula from source\n\nMake sure you have [go](https:\u002F\u002Fgo.dev\u002Fdoc\u002Finstall) installed and clone this repo. Change to the nebula directory.\n\nTo build nebula for all platforms:\n`make all`\n\nTo build nebula for a specific platform (ex, Windows):\n`make bin-windows`\n\nSee the [Makefile](Makefile) for more details on build targets\n\n## Curve P256 and BoringCrypto\n\nThe 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.\n\nIn addition, Nebula can be built using the [BoringCrypto GOEXPERIMENT](https:\u002F\u002Fgithub.com\u002Fgolang\u002Fgo\u002Fblob\u002Fgo1.20\u002Fsrc\u002Fcrypto\u002Finternal\u002Fboring\u002FREADME.md) by running either of the following make targets:\n\n```sh\nmake bin-boringcrypto\nmake release-boringcrypto\n```\n\nThis is not the recommended default deployment, but may be useful based on your compliance requirements.\n\n## Credits\n\nNebula was created at Slack Technologies, Inc by Nate Brown and Ryan Huber, with contributions from Oliver Fross, Alan Lam, Wade Simmons, and Lining Wang.\n\n","Nebula 是一个专注于性能、简洁性和安全性的可扩展覆盖网络工具。它通过使用Noise协议框架进行相互认证的点对点连接，支持跨平台运行（包括Linux, Windows, macOS等），并能跨越防火墙或NAT实现节点间的安全通信。Nebula利用证书来验证节点的身份及其所属用户定义组别，允许在不同云服务提供商、数据中心和个人设备之间无缝传输数据，同时提供基于用户自定义组的安全策略控制功能。适用于需要建立跨地域安全连接的企业环境，或是希望简化复杂网络架构管理的小团队和个人开发者。",2,"2026-06-11 03:00:51","top_language"]