-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
Regarding Netbird Peer advertising routes, dont get new peers automatic #2864
Labels
Comments
for me helped to switch advertising route on peers off and on, and voila, its started working on new peer :) |
Where do you do that?
søn. 10. nov. 2024 kl. 21.30 skrev kratochvilales ***@***.***
…:
for me helped to switch advertising route on peers off and on, and voila,
its started working on new peer :)
—
Reply to this email directly, view it on GitHub
<#2864 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4JDMVJ7RN5LWW34T7QFVLZ7664RAVCNFSM6AAAAABRNJXP4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWHEYDMOJQGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi kratochvilales where is that feature located. Im using a self hosted installation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a selfhosted Netbird Installation. My Problem is that I have a connected peer that advertises routes and it works fine. But when a new client or peer joins, the netbird network, that peer that advertises routes does not get the new peer/client automatic and therefore cant communicate with the new client. I have to make a Netbird down and then Netbird up on the peer that advertises routes, then it finds the new peer client and can respond traffic.
So its the Peers count: 2/5 Connected that dont count up to for example 3/6 when a new client gets added. I have to restart the netbird.
Are there a command to call or why does it not find it itself?
OS: linux/amd64
Daemon version: 0.31.0
CLI version: 0.31.0
Management: Connected to https://netbirdvpn.domain.com:443
Signal: Connected to https://netbirdvpn.domain.com:443
Relays:
[stun:netbirdvpn.domain.com:3478] is Available
[turn:netbirdvpn.domain.com:3478?transport=udp] is Available
[rels://netbirdvpn.domain.com:443] is Available
Nameservers:
[172.16.20.4:53, 192.168.140.1:53] for [domain.com] is Available
FQDN: netbird01.netbird.selfhosted
NetBird IP: 100.86.156.178/16
Interface type: Kernel
Quantum resistance: false
Routes: 192.168.1.10/24, 192.168.1.12/24
Peers count: 2/5 Connected
The text was updated successfully, but these errors were encountered: