# OpenZiti Controller on Hetzner Cloud **URL:** \ **Category:** General Questions\ **Created:** [September 16, 2023, 1:33pm UTC](https://openziti.discourse.group/t/openziti-controller-on-hetzner-cloud/1636 "2023-09-16T13:33:59Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![dariuszSki](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/dariuszski/32/339_2.png) [@dariuszSki](https://openziti.discourse.group/u/dariuszSki)\ **Post date:** [September 16, 2023, 3:23pm UTC](https://openziti.discourse.group/t/openziti-controller-on-hetzner-cloud/1636/4 "2023-09-16T15:23:44Z")
As @TheLumberjack mentioned that 0.0.0.0/0 service should accomplish to divert all traffic to ziti tunnel. We also exclude fabric routes from that so the fabric tunnels don’t get sucked into the tunnel like vpn would. I did not test this service myself. But before we had this type of service, I configured all public prefixes to cover all internet to steer traffic into the ziti tunnel, which essentially equaled to 0.0.0.0/0. Additionally related to what Clint mentioned as well, if I wanted to watch a specific tv streaming service like sling tv I created a service with wildcard to capture traffic destined to sling ie \*.slingtv.com The trick is to find all urls this streaming service is trying to reach. --- _[View the full topic](https://openziti.discourse.group/t/openziti-controller-on-hetzner-cloud/1636)._