Relays/Exit nodes/Subnet routers #288

Open
opened 2025-11-20 05:09:09 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @alexlyee on GitHub (Mar 9, 2023).

The only feature that I see in Netmaker that I'm really missing out on here is the ability to advertise routes. I think this is essentially what #289 was getting at, but I'd like to be more specific because I think generalizing this problem hits a lot of birds (oughsorry!) with the same stone:

  • If a client/user advertises other addresses within the network (i.e. 100.0.0.0/8) to be routable from them, they have elected themselves to be a potential fallback path (fallback router?) for the network. This would be particularly desirable for me because I'm hosting mine on a little VPS and really would rather not have to worry about an unknowing family member or friend hitting my monthly data limit because NAT tunneling was unsuccessful between them and, say, the NAS.
  • If a client/user advertises their LAN network addresses, they may be called a local exit node.
  • If a client/user advertises any other addresses, this would make them an exit node. Without this feature, I've got to use a separate Wireguard tunnel on my PC to use netbird to access my things and exit through my home network the way I'd like. And without this feature, I don't think I could use the mobile app for my use case.

Maybe this differentiation would be useful for UI and for buttons for toggling the three on and off.

edit: this was also mentioned, upvoted, but not replied to, in this discussion.

Originally created by @alexlyee on GitHub (Mar 9, 2023). The only feature that I see [in Netmaker](https://github.com/gravitl/netmaker) that I'm really missing out on here is the ability to advertise routes. I think this is essentially what #289 was getting at, but I'd like to be more specific because I think generalizing this problem hits a lot of birds (oughsorry!) with the same stone: - If a client/user advertises other addresses within the network (i.e. 100.0.0.0/8) to be routable from them, they have **elected themselves to be a potential fallback path (fallback router?) for the network**. This would be particularly desirable for me because I'm hosting mine on a little VPS and really would rather not have to worry about an unknowing family member or friend hitting my monthly data limit because NAT tunneling was unsuccessful between them and, say, the NAS. - If a client/user advertises their LAN network addresses, they may be called a **local exit node.** - If a client/user advertises any other addresses, this would make them an **exit node.** Without this feature, I've got to use a separate Wireguard tunnel on my PC to use netbird to access my things and exit through my home network the way I'd like. And without this feature, I don't think I could use the mobile app for my use case. Maybe this differentiation would be useful for UI and for buttons for toggling the three on and off. edit: this was also mentioned, upvoted, but not replied to, in [this discussion](https://github.com/netbirdio/netbird/discussions/587).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#288