Basically a copy-paste of Tailscale's feature; the wireguard protocol allows clients to specify which IPs are being forwarded for, and so specifying that some clients can act as exit nodes (0.0.0.0/8 routing) and some can act as subnet routers (for their local subnets) is able to be easily integrated.
This would add some core complexity.
Additionally, one feature I'm missing from Tailscale is the ability to specify which subnets are being routed, and where. Sometimes they overlap, this is almost inevitable with home networks, and so I'd like an option for granular control (for those clients which want them) to enable/disable routing for particular subnets.
Segments
Description
Basically a copy-paste of Tailscale's feature; the wireguard protocol allows clients to specify which IPs are being forwarded for, and so specifying that some clients can act as exit nodes (0.0.0.0/8 routing) and some can act as subnet routers (for their local subnets) is able to be easily integrated.
This would add some core complexity.
Additionally, one feature I'm missing from Tailscale is the ability to specify which subnets are being routed, and where. Sometimes they overlap, this is almost inevitable with home networks, and so I'd like an option for granular control (for those clients which want them) to enable/disable routing for particular subnets.