How to set AllowedIPs? #66

Closed
opened 2025-11-20 05:05:44 -05:00 by saavagebueno · 4 comments
Owner

Originally created by @yangchuansheng on GitHub (Sep 13, 2021).

I want to customize AllowedIPs, how do I do that?

Originally created by @yangchuansheng on GitHub (Sep 13, 2021). I want to customize AllowedIPs, how do I do that?
Author
Owner

@braginini commented on GitHub (Sep 13, 2021):

Hey @yangchuansheng
This is not possible.
For each allowed peer we set IP/32

Could you tell us more about your use case? Maybe we could do something about it.

@braginini commented on GitHub (Sep 13, 2021): Hey @yangchuansheng This is not possible. For each allowed peer we set IP/32 Could you tell us more about your use case? Maybe we could do something about it.
Author
Owner

@yangchuansheng commented on GitHub (Sep 13, 2021):

Suppose I want to connect to Peer's private address, how to do?

Carson Yang
@.***
+86 15316909456
QingCloud Technologies Corp.
fuckcloudnative.io
Zhejiang Hangzhou
KubeSphere is the Kubernetes platform tailored for hybrid multicloud More>>
在 2021年9月13日 +0800 PM11:36,Mikhail Bragin @.***>,写道:

@.*** is not possible.
For each allowed peer we set IP/32
Could you tell us more about your use case? Maybe we could do something about it.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

@yangchuansheng commented on GitHub (Sep 13, 2021): Suppose I want to connect to Peer's private address, how to do? Carson Yang ***@***.*** +86 15316909456 QingCloud Technologies Corp. fuckcloudnative.io Zhejiang Hangzhou KubeSphere is the Kubernetes platform tailored for hybrid multicloud More>> 在 2021年9月13日 +0800 PM11:36,Mikhail Bragin ***@***.***>,写道: > ***@***.*** is not possible. > For each allowed peer we set IP/32 > Could you tell us more about your use case? Maybe we could do something about it. > —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
Author
Owner

@mlsmaycon commented on GitHub (Sep 13, 2021):

Hello @yangchuansheng this feature is not implemented yet, but we plan to add it as part of the Router nodes described in our Public roadmap, you can have a look at https://github.com/wiretrustee/wiretrustee/projects/2#card-62348783, right now, the initial estimative is that we will be working on it on Q1/2022 but that can be moved to Q4/2021 depending on our review.

Please follow up on the roadmap updates.

@mlsmaycon commented on GitHub (Sep 13, 2021): Hello @yangchuansheng this feature is not implemented yet, but we plan to add it as part of the **Router nodes** described in our Public roadmap, you can have a look at https://github.com/wiretrustee/wiretrustee/projects/2#card-62348783, right now, the initial estimative is that we will be working on it on Q1/2022 but that can be moved to Q4/2021 depending on our review. Please follow up on the roadmap updates.
Author
Owner

@mlsmaycon commented on GitHub (Oct 29, 2022):

Closing this as network routes and routing peers are in the latest releases since v0.9.0

@mlsmaycon commented on GitHub (Oct 29, 2022): Closing this as network routes and routing peers are in the latest releases since [v0.9.0](https://github.com/netbirdio/netbird/releases/tag/v0.9.0)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#66