4 ms·
"By routing all an enterprise's traffic from devices anywhere on the planet through WARP." The one massively annoying thing is their split tunnel config does n
by slownews45 5y ago
"By routing all an enterprise's traffic from devices anywhere on the planet through WARP."
The one massively annoying thing is their split tunnel config does not let you ONLY route your enterprise IP ranges through cloudflare for teams. Ie, you want users to have access to 10.15.XXX.XXX but the rest of their traffic is unmolested.
You can only EXCLUDE some items from the routing, not just route some ranges. Weird isn't it?
Most users at home want netflix, local printing etc to continue to work as it did before their employer has them stick cloudflare on machine. Routing all their private traffic through cloudflare seems like a big miss.
- jaywalk 5y agoThat seems like something a company as technically-sophisticated as Cloudflare wouldn't screw up. Are you sure that's how it works? Even the crappy VPN software my employer uses does proper split tunneling.
- slownews45 5y agoI know! I was all excited to push everyone over to WARP - but it's a no go - people don't want all their traffic being proxied through corp side (we reserve right to do what we need / want with corp traffice). Info here: https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/exclude-traffic/split-tunnels https://developers.cloudflare.com/cloudflare-one/connections... And yes, the junky folks have this solved - you drop the endpoint on client, set a split tunnel and just pick up your enterprise route. A basic split tunnel (normal style) or one that picked up accessible ranges based on the individual user permissions both would work fine. So if you had a single app on 10.15.54.120 and user had access to that app, split tunnel would put that into route. Key is to leave everything else out - so your computer can see your phone can see your lights etc etc on local network and netflix and friends work normally.