To obtain access, contact your IT administrator.
+ +To obtain access, contact your IT administrator.
+ ``` diff --git a/src/content/partials/cloudflare-one/gateway/customize-block-page.mdx b/src/content/partials/cloudflare-one/gateway/customize-block-page.mdx index c0de73c31de4401..a9e74eec96a0bb4 100644 --- a/src/content/partials/cloudflare-one/gateway/customize-block-page.mdx +++ b/src/content/partials/cloudflare-one/gateway/customize-block-page.mdx @@ -1,6 +1,5 @@ --- {} - --- You can customize the block page by making global changes that will show up every time a user visits a block page, independently of the type of rule (DNS or HTTP) that is blocking the website. @@ -13,12 +12,12 @@ To apply customizations to your block page: 3. Select **Customize**. Available global customizations include: - * Adding your organization's name - * Adding a [logo](/cloudflare-one/policies/gateway/configuring-block-page/#add-a-logo-image) - * Adding a header text - * Adding a global block message, which will be displayed above the policy-specific block message - * Adding a [Mailto link](/cloudflare-one/policies/gateway/configuring-block-page/#allow-users-to-email-an-administrator) - * Choosing a background color + - Adding your organization's name + - Adding a [logo](/cloudflare-one/policies/gateway/block-page/#add-a-logo-image) + - Adding a header text + - Adding a global block message, which will be displayed above the policy-specific block message + - Adding a [Mailto link](/cloudflare-one/policies/gateway/block-page/#allow-users-to-email-an-administrator) + - Choosing a background color 4. Select **Save**. diff --git a/src/content/partials/cloudflare-one/gateway/policies/block-file-types.mdx b/src/content/partials/cloudflare-one/gateway/policies/block-file-types.mdx index 887bcc1d73c6720..fda7276c0940617 100644 --- a/src/content/partials/cloudflare-one/gateway/policies/block-file-types.mdx +++ b/src/content/partials/cloudflare-one/gateway/policies/block-file-types.mdx @@ -1,13 +1,12 @@ --- {} - --- ## Block file types Block the upload or download of files based on their type. -| Selector | Operator | Value | Logic | Action | -| ------------------ | -------- | ------------------------------------- | ----- | ------ | -| Upload File Type | in | Microsoft Office Word Document (docx) | And | Block | -| Download File Type | in | PDF (pdf) | | | +| Selector | Operator | Value | Logic | Action | +| ------------------ | -------- | --------------------------------------- | ----- | ------ | +| Upload File Type | in | _Microsoft Office Word Document (docx)_ | And | Block | +| Download File Type | in | _PDF (pdf)_ | | | diff --git a/src/content/partials/cloudflare-one/tunnel/warp-connector-alternate-gateway-flow.mdx b/src/content/partials/cloudflare-one/tunnel/warp-connector-alternate-gateway-flow.mdx new file mode 100644 index 000000000000000..e9d746288c52e16 --- /dev/null +++ b/src/content/partials/cloudflare-one/tunnel/warp-connector-alternate-gateway-flow.mdx @@ -0,0 +1,10 @@ +--- +{} +--- + +When a device on the subnet sends a request, the router will first redirect the traffic to the WARP Connector host. WARP Connector encrypts the traffic, changes its destination IP to the [WARP ingress IP](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip), and sends it back to the router. The router will now forward this encrypted traffic to Cloudflare. + +:::note + +Ensure that your routing rules do not forward the [WARP ingress IP](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip) back to the WARP Connector. +::: \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/tunnel/warp-connector-alternate-gateway.mdx b/src/content/partials/cloudflare-one/tunnel/warp-connector-alternate-gateway.mdx new file mode 100644 index 000000000000000..b85b3b959c9fb28 --- /dev/null +++ b/src/content/partials/cloudflare-one/tunnel/warp-connector-alternate-gateway.mdx @@ -0,0 +1,7 @@ +--- +{} +--- + +If you have access to the router but installed WARP Connector on another machine, you can configure the router to forward traffic to the WARP Connector. This typically involves adding a static route for the destination IPs that you want to connect to through Cloudflare. Refer to your router documentation for specific instructions on how to add an IP route. + +![Alternate gateway routing configuration](~/assets/images/cloudflare-one/connections/connect-apps/warp-connector/alternate-gateway.png) \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/tunnel/warp-connector-default-gateway.mdx b/src/content/partials/cloudflare-one/tunnel/warp-connector-default-gateway.mdx new file mode 100644 index 000000000000000..d86900345cd4301 --- /dev/null +++ b/src/content/partials/cloudflare-one/tunnel/warp-connector-default-gateway.mdx @@ -0,0 +1,7 @@ +--- +{} +--- + +If you installed WARP Connector on your router, no additional configuration is necessary. All traffic will use the router as the default gateway. + +![Default gateway routing configuration](~/assets/images/cloudflare-one/connections/connect-apps/warp-connector/default-gateway.png) \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/tunnel/warp-connector-device-profile.mdx b/src/content/partials/cloudflare-one/tunnel/warp-connector-device-profile.mdx new file mode 100644 index 000000000000000..2e18443ba38bdb3 --- /dev/null +++ b/src/content/partials/cloudflare-one/tunnel/warp-connector-device-profile.mdx @@ -0,0 +1,17 @@ +--- +{} +--- + +A dedicated [device profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/) allows you to manage the WARP Connector host machine separately from WARP client user devices. WARP Connector hosts are registered to your Zero Trust organization with the email address `warp_connector@