Replies: 3 comments
-
Hi @enzopsc - have you given this a read through? https://nebula.defined.net/docs/guides/unsafe_routes/ You'll need to make sure your routing nodes have the subnets defined in their certificate, IP forwarding must be enabled on the host, you need routing rules configured outside Nebula (e.g. using iptables), as well as creating Nebula firewall rules to allow this traffic. |
Beta Was this translation helpful? Give feedback.
-
Hi @johnmaguire
#server1
#server2:
I've already followed that guide https://nebula.defined.net/docs/guides/unsafe_routes/ for :
and it works. Server1 can reach Server2 and viceversa but if lighthouse tries to reach Server2 (172.16.50.3) and is not online it doesn't switch to Server1 (172.16.50.2). |
Beta Was this translation helpful? Give feedback.
-
I ended up doing a script that pings nebula hosts and switch configuration based on that. |
Beta Was this translation helpful? Give feedback.
-
I've a big network with 3 public IPs.
They're all located in different places and with different providers.
I've set 1 lighthouse and 3 nodes from 3 different public IP.
Below I'm showing only 2 of them because I was still testing nebula.
Behind these I've a single big network on 192.168.0.0/16
I was supposing to use unsafe_routes:
192.168.0.0/16 on both but when I tried to configure lighthouse that way to test reachability of them it wasn't working.
When node 172.16.50.4 goes down, it wasn't able to reach machines through 172.16.50.2
Basically it should give me ability to reach my clients from any public IP I've to grant me 100% uptime from outside my private network.
How I should configure it, is it possible?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions