connlib: unify packet routing between CIDR and DNS resources about firezone HOT 4 CLOSED

Conceptually yes, there are still different routing tables but that may not be worth unifying. What do you think @conectado?

I was thinking we could have an IpNetworkTable of ResourceIds and all resolved DNS IPs also get added to that and so would CIDR resources.

@thomaseizinger I'm changing the packet routing a lot for #4789 with the current model I'm working this will end up happening as part of that PR! And I'm planing to have it ready early this week. So let's wait until then.

But to give a quick overview of how that will work is: a routing table which is an IpNetworkTable and when adding any resource or when resolving a DNS resource the routing table would be updated, similarly to what's described in this PR. With the only difference that each entry on the table would point to a RangeMap that also points to a ResourceId. Will go into more details when I have the initial implementation done.

from firezone.

I think is done with the DNS refactor?

from firezone.

Conceptually yes, there are still different routing tables but that may not be worth unifying. What do you think @conectado?

I was thinking we could have an IpNetworkTable of ResourceIds and all resolved DNS IPs also get added to that and so would CIDR resources.

from firezone.

I think this is done?

from firezone.