MASQUE GA

Author: ranbel

src/content/changelogs/warp.yaml

@@ -5,6 +5,10 @@ productLink: "/cloudflare-one/connections/connect-devices/warp/"
 productArea: Cloudflare One
 productAreaLink: /cloudflare-one/changelog/
 entries:
+  - publish_date: "2024-11-15"
+    title: MASQUE GA
+    description: |-
+      MASQUE as a device tunnel protocol option is now generally available (GA). Refer to [Device tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol) for configuration details and minimum WARP client requirements.
   - publish_date: "2024-10-23"
     title: WARP client for macOS (version 2024.10.279.1)
     description: |-

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/index.mdx

@@ -63,7 +63,7 @@ The client will automatically reconnect after the [Auto connect period](#auto-co
 
 When `Enabled`, the WARP client will [automatically install](/cloudflare-one/connections/connect-devices/warp/user-side-certificates/automated-deployment/) your organization's root certificate on the device.
 
-### Override local interface IP <InlineBadge preset="beta" />
+### Override local interface IP
 
 <Details header="Feature availability">
 
@@ -120,9 +120,9 @@ When `Enabled`, users have the option to switch between [Gateway with WARP](/clo
 | Windows  | ✅           | 2024.6.415.0         |
 | macOS    | ✅           | 2024.6.416.0         |
 | Linux    | ✅           | 2024.6.497.0         |
-| iOS      | Coming soon  |                      |
-| Android  | Coming soon  |                      |
-| ChromeOS | Coming soon  |                      |
+| iOS      | ✅   			   | 1.7                  |
+| Android  | ✅   			   | 2.0                  |
+| ChromeOS | ✅ 				   | 2.0                  |
 
 </Details>
 
@@ -131,7 +131,7 @@ Configures the protocol used to route IP traffic from the device to Cloudflare G
 **Value**:
 
 - **WireGuard**: (default) Establishes a [WireGuard](https://www.wireguard.com/) connection to Cloudflare. The WARP client will encrypt traffic using a non-FIPs compliant cipher suite, `TLS_CHACHA20_POLY1305_SHA256`. When switching from MASQUE to WireGuard, users may lose Internet connectivity if their Wi-Fi network blocks the [ports and IPs](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip) required for WireGuard to function.
-- **MASQUE** <InlineBadge preset="beta" />: Establishes an HTTP/3 connection to Cloudflare. To use MASQUE, [Override local interface IP](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#override-local-interface-ip-) must be `Enabled`. The WARP client will encrypt traffic using TLS 1.3 and a [FIPS 140-2](https://csrc.nist.gov/pubs/fips/140-2/upd2/final) compliant cipher suite, `TLS_AES_256_GCM_SHA384`.
+- **MASQUE**: Establishes an HTTP/3 connection to Cloudflare. To use MASQUE, [Override local interface IP](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#override-local-interface-ip-) must be `Enabled`. The WARP client will encrypt traffic using TLS 1.3 and a [FIPS 140-2](https://csrc.nist.gov/pubs/fips/140-2/upd2/final) compliant cipher suite, `TLS_AES_256_GCM_SHA384`.
 
 For more details on WireGuard versus MASQUE, refer to our [blog post](https://blog.cloudflare.com/zero-trust-warp-with-a-masque).