Mesh Networking: Difference between revisions

From Wizard Rants
Jump to navigation Jump to search
Created page with "Nebula as a mesh network choice potentially.<blockquote>Just a quick note, nebula doesn't inherently require being run as root, as long as you allow it to do network-things. T..."
 
linking to Nebula repo
 
Line 1: Line 1:
Nebula as a mesh network choice potentially.<blockquote>Just a quick note, nebula doesn't inherently require being run as root, as long as you allow it to do network-things. This is easily done with setcap with the CAP_NET_ADMIN capability, i.e. you can do:
[https://github.com/slackhq/nebula Nebula] as a mesh network choice potentially.<blockquote>Just a quick note, nebula doesn't inherently require being run as root, as long as you allow it to do network-things. This is easily done with setcap with the CAP_NET_ADMIN capability, i.e. you can do:


sudo setcap cap_net_admin+ep /usr/local/bin/nebula
sudo setcap cap_net_admin+ep /usr/local/bin/nebula


...and then you can run it as any user you like. Just make sure the nebula configuration and creds are readable by that user.</blockquote>
...and then you can run it as any user you like. Just make sure the nebula configuration and creds are readable by that user.</blockquote>

Latest revision as of 07:44, 22 February 2021

Nebula as a mesh network choice potentially.

Just a quick note, nebula doesn't inherently require being run as root, as long as you allow it to do network-things. This is easily done with setcap with the CAP_NET_ADMIN capability, i.e. you can do:

sudo setcap cap_net_admin+ep /usr/local/bin/nebula

...and then you can run it as any user you like. Just make sure the nebula configuration and creds are readable by that user.