SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-14 19:31:51 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Force specific IP to node because infrastructure sometimes requires specific IP's to be forever. #150

New Issue
Open
opened 2025-11-20 05:07:05 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 05:07:05 -05:00
Owner
Copy Link

Originally created by @Leopere on GitHub (Jul 10, 2022).

Just recently due to to Canada getting "rogered" I had to rebuild some of my cluster and it turns out one of my nodes needed to be reinstalled during my RCA. Is there a way to guarantee that a node can start with a specific IP? Some infrastructure cannot have IPs shifting around.

Originally created by @Leopere on GitHub (Jul 10, 2022). Just recently due to to Canada getting "rogered" I had to rebuild some of my cluster and it turns out one of my nodes needed to be reinstalled during my RCA. Is there a way to guarantee that a node can start with a specific IP? Some infrastructure cannot have IPs shifting around.
saavagebueno added the feature-request label 2025-11-20 05:07:05 -05:00
saavagebueno commented 2025-11-20 05:07:06 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 10, 2022):

Hi @Leopere the node IP will be the same as long as his wireguard key doesn't change. You can keep a backup of the /etc/netbird/config.json file to avoid IP changes in the future

@mlsmaycon commented on GitHub (Jul 10, 2022): Hi @Leopere the node IP will be the same as long as his wireguard key doesn't change. You can keep a backup of the /etc/netbird/config.json file to avoid IP changes in the future
saavagebueno commented 2025-11-20 05:07:06 -05:00
Author
Owner
Copy Link

@Leopere commented on GitHub (Jul 11, 2022):

Correct however that's not always possible for example during the Rogering Canada received it was massively disruptive and a number of things broke and during an RCA it was necessary to upgrade from the old Wiretrustee namespace to Netbird in this scenario the IP was forced to roll over. It would be massively inconvenient for let's say an Active Directory Domain Controller is bound to the Netbird IP among others and to have to meddle with keys in a secure way.

Also perhaps the config is somehow compromised on the machine which would mean that you would have to continue to use the old key. Is it technologically difficult to allow me to determine the IP of a Netbird node through the panel?

@Leopere commented on GitHub (Jul 11, 2022): Correct however that's not always possible for example during the Rogering Canada received it was massively disruptive and a number of things broke and during an RCA it was necessary to upgrade from the old `Wiretrustee` namespace to `Netbird` in this scenario the IP was forced to roll over. It would be massively inconvenient for let's say an Active Directory Domain Controller is bound to the Netbird IP among others and to have to meddle with keys in a secure way. Also perhaps the config is somehow compromised on the machine which would mean that you would have to continue to use the old key. Is it technologically difficult to allow me to determine the IP of a Netbird node through the panel?
saavagebueno commented 2025-11-20 05:07:06 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 11, 2022):

Ok, I see your point.

It is possible to allow such an option via the panel or API, we will discuss and prioritize that.

Regarding issues with the name change, we would like to get more information as the client was prepared to migrate files between /etc/wiretrustee to /etc/netbird and it may be a major bug if you faced issues.

@mlsmaycon commented on GitHub (Jul 11, 2022): Ok, I see your point. It is possible to allow such an option via the panel or API, we will discuss and prioritize that. Regarding issues with the name change, we would like to get more information as the client was prepared to migrate files between /etc/wiretrustee to /etc/netbird and it may be a major bug if you faced issues.
saavagebueno commented 2025-11-20 05:07:06 -05:00
Author
Owner
Copy Link

@Leopere commented on GitHub (Jul 11, 2022):

For now I'll follow your advice but just hoping that it makes it at some point might be a good feature!

@Leopere commented on GitHub (Jul 11, 2022): For now I'll follow your advice but just hoping that it makes it at some point might be a good feature!
saavagebueno commented 2025-11-20 05:07:07 -05:00
Author
Owner
Copy Link

@Leopere commented on GitHub (Jul 13, 2022):

Ok, I see your point.

It is possible to allow such an option via the panel or API, we will discuss and prioritize that.

Regarding issues with the name change, we would like to get more information as the client was prepared to migrate files between /etc/wiretrustee to /etc/netbird and it may be a major bug if you faced issues.

My problem was caused by the Rogering* that Canada received and I wouldn't really know how to reproduce a country losing internet to really reproduce. All of my other 25 various style nodes recovered fine.

@Leopere commented on GitHub (Jul 13, 2022): > Ok, I see your point. > > It is possible to allow such an option via the panel or API, we will discuss and prioritize that. > > Regarding issues with the name change, we would like to get more information as the client was prepared to migrate files between /etc/wiretrustee to /etc/netbird and it may be a major bug if you faced issues. My problem was caused by the Rogering* that Canada received and I wouldn't really know how to reproduce a country losing internet to really reproduce. All of my other 25 various style nodes recovered fine.
saavagebueno commented 2025-11-20 05:07:07 -05:00
Author
Owner
Copy Link

@Leopere commented on GitHub (Jun 20, 2023):

Thanks!

@Leopere commented on GitHub (Jun 20, 2023): Thanks!
saavagebueno commented 2025-11-20 05:07:07 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 20, 2023):

Hi, @Leopere, I intended to send you a message instead of closing the issue. My apologies.

The initial issue seems to have been resolved, but I wanted to ask you if with the DNS feature you still have the need for forcing the IP address, if so, could you explain a bit your use case so we can properly take into consideration?

@mlsmaycon commented on GitHub (Jun 20, 2023): Hi, @Leopere, I intended to send you a message instead of closing the issue. My apologies. The initial issue seems to have been resolved, but I wanted to ask you if with the DNS feature you still have the need for forcing the IP address, if so, could you explain a bit your use case so we can properly take into consideration?
saavagebueno commented 2025-11-20 05:07:07 -05:00
Author
Owner
Copy Link

@Leopere commented on GitHub (Jun 21, 2023):

it was mostly that sometimes a node dies and occassionally I don't have backups to specific nodes /etc/ directories as its typically okay if we just blow away a node and start fresh on it. However the way Netbird was working was you would have to keep the private key of the machine if you wanted to continue using it's IP address and it would be critical in some cases such as active directory servers for example that the IP addresses used never change. In some cases using Gluster FS is also a trick with changing locations and IP's of nodes in a cluster. I will often use the wireguard/netbird mesh to avoid having to trust gluster's encryption/security layer.

@Leopere commented on GitHub (Jun 21, 2023): it was mostly that sometimes a node dies and occassionally I don't have backups to specific nodes /etc/ directories as its typically okay if we just blow away a node and start fresh on it. However the way Netbird was working was you would have to keep the private key of the machine if you wanted to continue using it's IP address and it would be critical in some cases such as active directory servers for example that the IP addresses used never change. In some cases using Gluster FS is also a trick with changing locations and IP's of nodes in a cluster. I will often use the wireguard/netbird mesh to avoid having to trust gluster's encryption/security layer.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label feature-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#150
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?