Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 BUG: use_relays false ignored #1025

Closed
chirayu-patel opened this issue Nov 26, 2023 · 2 comments
Closed

🐛 BUG: use_relays false ignored #1025

chirayu-patel opened this issue Nov 26, 2023 · 2 comments
Labels
WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@chirayu-patel
Copy link

chirayu-patel commented Nov 26, 2023

What version of nebula are you using?

1.6.0 and 1.7.2

What operating system are you using?

Linux

Describe the Bug

I have enabled relay feature on the lighthouse node which is having public ip.

The other nodes mostly are behind NAT.

By default, I have enabled relays to be true on all the nodes. So they try relaying through the lighthouse node.

Today, on one of the nodes I tried disabling relay using use_relay false, I also tried completely removing the relay config.

Still , its relaying through the lighthouse node. I even restarted the service as well rebooted the node completely.

I double checked by connecting to the ssh service, it continues relaying through the relay node. Not sure from where is it getting the info to relay

Logs from affected hosts

ray@nebula > print-relays
{"Relays":[{"NebulaIp":"192.168.100.1","RelayForIps":[{"Error":null,"Type":"terminal","State":"established","PeerIp":"192.168.100.49","LocalIndex":2817129221,"RemoteIndex":2268183854,"RelayedThrough":["192.168.100.1"]}]}]}

Config files from affected hosts

No response

@johnmaguire
Copy link
Collaborator

Hi @chirayu-patel - I apologize we let this issue languish for so long without a reply.

Can you please include the config file (with pki information removed) for the Lighthouse (192.168.100.1), the affected node, and the node it is communicating with (192.168.100.49)?

Additionally, can you confirm that the node has been restarted since you set relay.use_relays: false? This flag is not currently reloadable, and requires a full restart of Nebula to take effect.

@johnmaguire johnmaguire added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jan 17, 2024
@johnmaguire
Copy link
Collaborator

Closing for inactivity.

@johnmaguire johnmaguire closed this as not planned Won't fix, can't repro, duplicate, stale Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

2 participants