# Pritunl route

**URL:** <https://forum.pritunl.com/t/pritunl-route/2106>\
**Category:** Pritunl VPN\
**Tags:** pritunl\
**Created:** [June 7, 2024, 1:46pm UTC](https://forum.pritunl.com/t/pritunl-route/2106 "2024-06-07T13:46:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![asthonis](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/a/59ef9b/32.png) [@asthonis](https://forum.pritunl.com/u/asthonis)\
**Post date:** [June 7, 2024, 1:46pm UTC](https://forum.pritunl.com/t/pritunl-route/2106/1 "2024-06-07T13:46:39Z")

</div>

Guys, I have a small problem and I can’t think of a solution for it. We have recently implemented the PRITUNL VPN for our team and encountered a small setback. I have a service running with the Cloudflare proxy active, and some people need to access this service from our PRITUNL VPN. However, to access this service, I would need to allow the entire IP range that Cloudflare uses for the proxy, but this is neither secure nor performant, considering that all internet services using Cloudflare would pass through my VPN. Is there any way I can get around this?

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [June 7, 2024, 2:08pm UTC](https://forum.pritunl.com/t/pritunl-route/2106/2 "2024-06-07T14:08:35Z")

</div>

There is no option to avoid this, routing those IPs will route significant portions of internet traffic over the VPN.