Proxy traffic through Gateway
With Cloudflare Gateway, you can log and filter DNS, network, and HTTP traffic from devices running the WARP client. This includes traffic to the public Internet and traffic directed to your private network. DNS filtering is enabled by default since the WARP client sends DNS queries to Cloudflare’s public DNS resolver, 1.1.1.1. To enable network and HTTP filtering, you will need to allow Cloudflare Gateway to proxy that traffic.
- Go to Settings > Network.
- Enable Proxy for TCP.
- (Recommended) To proxy traffic to internal DNS resolvers, select UDP.
- (Recommended) To proxy traffic for diagnostic tools such as
ping
andtraceroute
, select ICMP. You may also need to update your system to allow ICMP traffic throughcloudflared
:
Linux
-
Ensure that
ping_group_range
includes the Group ID (GID) of the user runningcloudflared
.- To get the Group ID of the user, run
id -g
. - To verify the Group IDs that are allowed to use ICMP:
- Either add the user to a group within that range, or update the range to encompass a group the user is already in. To update
ping_group_range
:
- To get the Group ID of the user, run
-
If you are running multiple network interfaces (for example,
eth0
andeth1
), configurecloudflared
to use the external Internet-facing interface:
Docker
In your environment, modify the ping_group_range
parameter to include the Group ID (GID) of the user running cloudflared
.
By default the cloudflared
Docker container ↗ executes as a user called nonroot
inside of the container. nonroot
is a specific user that exists in the base image ↗ we use, and its Group ID is hardcoded to 65532.
Cloudflare will now proxy traffic from enrolled devices, except for the traffic excluded in your split tunnel settings. For more information on how Gateway forwards traffic, refer to Gateway proxy.
Cloudflare will now proxy traffic from enrolled devices, except for the traffic excluded in your split tunnel settings. For more information on how Gateway forwards traffic, refer to Gateway proxy.