Multihop networking

Does the rancher network agent support multi-hop routing? Meaning, if I have service A which can talk to service B and B can talk to C but A and C are isolated from each other can I still access C’s rancher managed IP from A? This would be similar to weave’s multi-hop routing.

I have containers running in my internal datacenter that I want to talk to from a public cloud but I don’t want to create a firewall rule for every one of my internal docker hosts. Wondering if I could just have one host running the network agent and then all other internal hosts hop in and out via that one.

DNS resolution will not work, but accessing the IP should work.