archive/theorangeone.net-legacy
1
Fork 0
Code Activity

Remove stray header

Browse source
This commit is contained in:
Jake Howard 2021-02-06 23:09:35 +00:00
parent 822198a7df
commit ddd33e4c55
Signed by: jake
GPG key ID: 57AFB45680EDD477
1 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/posts/nebula-unsafe-routes.md
View file

@ -6,8 +6,6 @@ subtitle: Routing traffic to devices outside Nebula
tags: [linux, security] tags: [linux, security]
--- ---
# Nebula unsafe routes
[Nebula](https://github.com/slackhq/nebula) is a great mesh network I [recently deployed]({{< relref "nebula-intro" >}}) into my stack. For connecting nodes spread between networks, it's great, much better than my previous [wireguard]({{< relref "wireguard-haproxy-gateway" >}}) installation. [Nebula](https://github.com/slackhq/nebula) is a great mesh network I [recently deployed]({{< relref "nebula-intro" >}}) into my stack. For connecting nodes spread between networks, it's great, much better than my previous [wireguard]({{< relref "wireguard-haproxy-gateway" >}}) installation.
An additional feature of nebula is `unsafe_routes`. Unsafe routes allow nodes which don't have Nebula installed to be accessible to other Nebula nodes. Traffic for those nodes is sent via an intermediary node which has access to the devices on its own network. This means you can use a node as a form of gateway to bride to another network, all through Nebula. An additional feature of nebula is `unsafe_routes`. Unsafe routes allow nodes which don't have Nebula installed to be accessible to other Nebula nodes. Traffic for those nodes is sent via an intermediary node which has access to the devices on its own network. This means you can use a node as a form of gateway to bride to another network, all through Nebula.