Repository navigation
lighthouse as relay for other lighthouse #1921
|
There are three lighthouses (all public IP and can see each other) the network is
pki:
ca: ca.crt
cert: host.crt
key: host.key
static_host_map:
"192.168.168.254": ["PUBLIC_IP:4242"]
"192.168.168.253": ["PUBLIC_IP:4242"]
"192.168.168.252": ["PUBLIC_IP:4242"]
lighthouse:
am_lighthouse: true
interval: 60
listen:
host: 0.0.0.0
port: 4242and each lighthouse relay setup to two others # 192.168.168.254
relay:
relays:
- 192.168.168.253
- 192.168.168.252
am_relay: true
use_relays: true
---
# 192.168.168.253
relay:
relays:
- 192.168.168.254
- 192.168.168.252
am_relay: true
use_relays: true
---
# 192.168.168.252
relay:
relays:
- 192.168.168.254
- 192.168.168.253
am_relay: true
use_relays: truethere are some clients behind NAT (all clients can see all three lighthouses)
there are some endpoint behind a firewall
pki:
ca: ca.crt
cert: host.crt
key: host.key
static_host_map:
"192.168.168.254": ["PUBLIC_IP:4242"]
"192.168.168.253": ["PUBLIC_IP:4242"]
"192.168.168.252": ["PUBLIC_IP:4242"]
lighthouse:
am_lighthouse: false
interval: 60
hosts:
- "192.168.168.254"
- "192.168.168.253"
- "192.168.168.252"
listen:
host: 0.0.0.0
port: 4242
punchy:
punch: true
respond: true
relay:
relays:
- 192.168.168.254
- 192.168.168.253
- 192.168.168.252
am_relay: false
use_relays: truethe architecture [clients] <====> | NAT | <====> [lighthouses] <====> | FW | <=====> [endpoints]clients should be able to reach endpoints as well as lighthouses be able to reach endpoints with this arch I wanted clients can reach to endpoints with high-availability (three lighthouses), but the issue is one of lighthouse (192.168.168.253) cannot see endpoints even when other lighthouses (192.168.168.254-252) are relay-enabled it seems like a lighthouse can ONLY be a relay for other nodes NOT another lighthouse? is this correct? Regards |
Replies: 1 comment 5 replies
|
if I make the second lighthouse (192.168.168.253) a host (lighthouse: false) then this machine can reach 192.168.168.100 via other two lighthouses (but I want to keep it as a lighthouse) |
Hi @shakibamoshiri -
If I'm following, you have three lighthouses on three different networks, plus an endpoint device. The endpoint device can reach two lighthouses, but not the third. The third lighthouse therefore cannot serve as a coordination server for NAT and IP discovery for that endpoint in either direction (expected.) It also can't send its own overlay traffic to the endpoint which your use case requires (problematic.)
If that's correct, then I think the cheapest option is to set
tun.disabled: trueon the problematic Lighthouse and run a second Nebula process on the same machine as a regular host that uses relays for overlay traffic (lighthouse.am_lighthouse: false, relay.am_rel…