You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a lighthouse that also works as a relay. I also have some hosts. One of the hosts is an oracle vps and the others are regular laptops behind a house network. With one of the regular laptops when i want to reach the vps on port 8000 it works perfectly. But if i try to reach port 8000 or 3000 on the other laptop that is behind another house network it doesnt work. I can ping it, but cant reach a specific port. SSH to all machines work using the nebula private ip.
To reach the other laptop I had to enable relays. To reach the vps I didn't need relays. I personally believe it could have something related to that, but im not sure why its not working.
Here are the config files for the lighthouse:
pki:
ca: /etc/nebula/ca.crt
cert: /etc/nebula/blue-lighthouse.crt
key: /etc/nebula/blue-lighthouse.key
# Port settings
listen:
#Default for this key is 0.0.0.0 which is v4-only
host: "[::]"
port: 4242
relay:
am_relay: true
use_relays: false
# No static hosts for lighthouses
static_host_map:
#Lighthouse settings
lighthouse:
am_lighthouse: true
# Enable serving DNS to anyone (Even our external IP)
serve_dns: true
dns:
#Default for this key is 0.0.0.0 which is v4-only
host: "[::]"
port: 5300
#Firewall settings
firewall:
outbound:
# Allow all outbound traffic from this node
- port: any
proto: any
host: any
inbound:
# Allow icmp between any nebula hosts
- port: any
proto: any
host: any
# Allow DNS incoming since we are serving DNS at this lighthouse
- port: 5300
proto: any
group: any
and here are the configs im using for the regular hosts:
pki:
ca: /etc/nebula/ca.crt
cert: /etc/nebula/host.crt
key: /etc/nebula/host.key
# Need a static host map, using the DNS name of the lighthouse
static_host_map:
#Put all of your lighthouses here
"192.168.100.1": ["<ip of the lighthouse>:4242"]
#This is completely undocumented
#static_map is how to interpret static_host_map
#It defaults to ip4, trying to connect to the lighthouse
#using only ipv4. This sorta-kinda makes sense since the node
#knows its own public v6 already but not its public v4 (Via NAT)
#so connecting to the lighthouse via v4 lets it learn that
#For ipv6-only hosts, change to `ip6` instead
static_map:
network: ip4
# Lighthouse config for clients
lighthouse:
hosts:
- "192.168.100.1"
relay:
relays:
- 192.168.100.1
am_relay: false
use_relays: true
#Listen
listen:
#Default for this key is 0.0.0.0 which is v4-only
host: "[::]"
#Port of 0 means randomly choose, usually good for clients
#Want to set to 4242 for relays and lighthouses
port: 0
#Firewall settings
firewall:
outbound:
# Allow all outbound traffic from this node
- port: any
proto: any
host: any
inbound:
# Allow icmp between any nebula hosts
- port: any
proto: any
host: any
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a lighthouse that also works as a relay. I also have some hosts. One of the hosts is an oracle vps and the others are regular laptops behind a house network. With one of the regular laptops when i want to reach the vps on port 8000 it works perfectly. But if i try to reach port 8000 or 3000 on the other laptop that is behind another house network it doesnt work. I can ping it, but cant reach a specific port. SSH to all machines work using the nebula private ip.
To reach the other laptop I had to enable relays. To reach the vps I didn't need relays. I personally believe it could have something related to that, but im not sure why its not working.
Here are the config files for the lighthouse:
and here are the configs im using for the regular hosts:
Beta Was this translation helpful? Give feedback.
All reactions