netbird
netbird copied to clipboard
netbirdio
self-define client IP address range
It seems that with the older version, client local ip address can be defined by --wgLocalAddr flag, yet it's no longer available in v0.3.
Also I couldn't find a field to set ip address range on server-side in management.json.
Is there any way to define client IP address range?
Just found that I can update the setting by touching store.json in management volume, while a more elegant should be preferable...
Hey @wellsgz and thank you for the question. We didn't plan to make it possible to update the address range. Might be something to plan for the future.
What is your use case? Why exactly do you want to manage this part?
Hey @wellsgz and thank you for the question. We didn't plan to make it possible to update the address range. Might be something to plan for the future.
What is your use case? Why exactly do you want to manage this part?
I happened to be testing wiretrustee and tailscale on the same machine, and tailscale automated iptables rules drop the wiretrustee traffic, so I was looking for a workaround.
Other than that, I don't have an actual use case now, yet I think it's not a bad idea to give advanced users freedom of choice, given hacking the store.json way seems to work seamlessly with my DIY management node.
We will think about it. Maybe on the first run, we could have this as a 1st configuration step.
Can't promise that we will implement it in the nearest future.
I too would like to be able to configure the subnet used for client IPs. In a controlled environment we can choose a network range that we know won't conflict with other ranges, but can still fit into our schema. I understand the reason for choosing the CGNAT range, it would be nice to be able to change it.
Yep, totally agreed, it would be great to have this feature implemented.
I too would like to be able to configure the subnet used for client IPs. In a controlled environment we can choose a network range that we know won't conflict with other ranges, but can still fit into our schema. I understand the reason for choosing the CGNAT range, it would be nice to be able to change it.
I am curious, could you tell why they chose CGNAT?
Is there any news or plan regarding this? I have the same situation where I want to implement this but it may collide with the network I can't manage. Thanks for your huge effort!
