From ddd33e4c556a410e2e48f4bfbc84b5b5f1e45bfd Mon Sep 17 00:00:00 2001 From: Jake Howard Date: Sat, 6 Feb 2021 23:09:35 +0000 Subject: [PATCH] Remove stray header --- content/posts/nebula-unsafe-routes.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/posts/nebula-unsafe-routes.md b/content/posts/nebula-unsafe-routes.md index a948084..282ea36 100644 --- a/content/posts/nebula-unsafe-routes.md +++ b/content/posts/nebula-unsafe-routes.md @@ -6,8 +6,6 @@ subtitle: Routing traffic to devices outside Nebula 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. 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.