new page: Networks access management

[nazarewk]

[nazarewk]

decided to include the original diagram sources so it's easier to adjust later on

[Blackclaws]

Related: netbirdio/netbird#4606

However I'd like to bring up the question whether the current behavior even makes sense if you need a whole page dedicated to explaining it.

It just took me an hour to debug that the input chain isn't populated because to me it was obvious that granting access to a subnet would also include the routing peer itself.

[nazarewk]

However I'd like to bring up the question whether the current behavior even makes sense if you need a whole page dedicated to explaining it.

@Blackclaws I understand the frustration (was there myself at least twice), but it's not as much about preserving the current behavior (it is what you get uniformly across all of the operating systems by default) as need to implement workarounds as fully fledged (and probably quite time-consuming) cross-platform feature that we don't have the manpower to properly design and implement in foreseeable future.

[Blackclaws]

However I'd like to bring up the question whether the current behavior even makes sense if you need a whole page dedicated to explaining it.

@Blackclaws I understand the frustration (was there myself at least twice), but it's not as much about preserving the current behavior (it is what you get uniformly across all of the operating systems by default) as need to implement workarounds as fully fledged (and probably quite time-consuming) cross-platform feature that we don't have the manpower to properly design and implement in foreseeable future.

Understood. Maybe adding a heads up to the networks page when you add resources that explains that routing peers by definition are not included in the scope whatever it may be, would alleviate that problem :)

I get that you need to be picky about what to implement and don't have unlimited resources. If this is something that gets implemented down the line that would be great however.

[nazarewk]

Understood. Maybe adding a heads up to the networks page when you add resources that explains that routing peers by definition are not included in the scope whatever it may be, would alleviate that problem :)

that's a good idea, thanks